这是indexloc提供的服务,不要输入任何密码

Debian Bug report logs - #376123
a way for a prerm to postpone package removal

version graph

Package: dpkg; Maintainer for dpkg is Dpkg Developers <debian-dpkg@lists.debian.org>; Source for dpkg is src:dpkg (PTS, buildd, popcon).

Reported by: Simon Richter <sjr@debian.org>

Date: Fri, 30 Jun 2006 11:33:15 UTC

Severity: wishlist

Found in version dpkg/1.13.21

Reply or subscribe to this bug.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, sjr@debian.org, Dpkg Developers <team@dpkg.org>:
Bug#376123; Package dpkg. (full text, mbox, link).


Acknowledgement sent to Simon Richter <sjr@debian.org>:
New Bug report received and forwarded. Copy sent to sjr@debian.org, Dpkg Developers <team@dpkg.org>. (full text, mbox, link).


Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Simon Richter <sjr@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: a way for a prerm to postpone package removal
Date: Fri, 30 Jun 2006 13:26:08 +0200
Package: dpkg
Version: 1.13.21
Severity: wishlist

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I thought it would be nice if there were a way for a prerm to indicate
that it would like to abort package removal but not flag an error.

Rationale: When I have the metapackage for "current kernel" installed, I
get a new kernel-image package every so often, and at the same time the
old kernel goes unused in the eyes of aptitude, so it wants to remove
it. The kernel's prerm then asks the user whether to uninstall the
running kernel (bad) or abort the removal. If the user chooses to abort
the removal, dpkg bails out as it could not perform the requested
action, thus making the entire installation fail. If it were possible to
say "not yet" and have dpkg ignore the removal request and return a
special exit code ("not entirely successful"), then aptitude could
reconsider that the removal is not required at this time (because it's
just an unused package being removed) and leave the package in "to be
removed" state. Eventually, the user will boot the new kernel, at which
time the removal of the old kernel will succeed.

The only way to "emulate" such a feature for aptitude would be to retry
removals package-by-package in order to find out what failed (the user
would be prompted again here), which takes a lot more time than just
rereading the status and deciding on a further course of action (fail if
the removal was needed, ignore otherwise).

   Simon

- -- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-amd64-k8
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)

Versions of packages dpkg depends on:
ii  coreutils                     5.96-3     The GNU core utilities
ii  libc6                         2.3.6-15   GNU C Library: Shared libraries

dpkg recommends no packages.

- -- debconf-show failed



Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Sun Jul 27 22:38:30 2025; Machine Name: berlioz

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU General Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.