Graham Williams wrote:
Hi David,
Thank you for the bug report. Could you give me an example that
illustrates what you observe.
# just list linux-image-2.6.16-alsa-agp
rc linux-image-2.6.16-alsa-agp
6 Linux kernel binary image for version 2.6.16
# just purge linux-image-2.6.16-alsa-agp
Reading package lists... Done
Building dependency tree... Done
Package linux-image-2.6.16-alsa-agp is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
# just list linux-image-2.6.16-alsa-agp
rc linux-image-2.6.16-alsa-agp
6 Linux kernel binary image for version 2.6.16
What I would like this do to is to remove the package so it doesn't show
in list (it's not just deinstalled but purged). In /var/lib/dpkg/status,
I would like to see something like this:
Package: libpostproccvs51-dev
Status: purge ok not-installed
Priority: optional
Section: libdevel
Bugs: mailto:[EMAIL PROTECTED]
Architecture: amd64
That's what a purged package should look like. If I do a list here, I
see nothing -- not even a blank line:
[EMAIL PROTECTED]:~# just list libpostproccvs51-dev
[EMAIL PROTECTED]:~#
But purge isn't working, so /var/lib/dpkg/status shows the whole thing,
as below. It clutters my lists badly. As an installation grows in age,
it accretes increasing quantities of useless information that distracts
from the task at hand.
David
Package: linux-image-2.6.16-alsa-agp
Status: deinstall ok config-files
Priority: optional
Section: base
Installed-Size: 11400
Maintainer: John Doe <[EMAIL PROTECTED]>
Architecture: amd64
Source: linux-source-2.6.16-alsa-agp
Version: 6
Config-Version: 6
Provides: linux-image, linux-image-2.6
Depends: coreutils | fileutils (>= 4.0)
Pre-Depends: debconf (>= 0.2.17) | debconf-2.0
Suggests: lilo (>= 19.1) | grub, fdutils, linux-doc-2.6.16-alsa-agp |
linux-source-2.6.16$
Description: Linux kernel binary image for version 2.6.16-alsa-agp
This package contains the Linux kernel image for version
2.6.16-alsa-agp.
.
It also contains the corresponding System.map file, and the modules
built by the packager. It also contains scripts that try to ensure
that the system is not left in a unbootable state after an update.
.
Kernel image packages are generally produced using kernel-package,
and it is suggested that you install that package if you wish to
create a custom kernel from the sources. Please look at kernel-img.conf(5),
and /usr/share/doc/kernel-package/README.gz from the package
kernel-package
for details on how to tailor the installation of this or any other kernel
image package
Thanks,
Graham
Received Sat 15 Apr 2006 3:38am +1000 from David Liontooth:
Package: wajig
Version: 2.0.31
Severity: minor
wajig purge <package> no longer changes the status of that package from deinstall
to purged. Perhaps this is a dpkg feature?
It would also be very useful to have a command that removes purged packages from
/var/lib/dpkg/status, so they don't clutter queries.
David
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages wajig depends on:
ii apt 0.6.43.1 Advanced front-end for dpkg
ii python 2.3.5-4 An interactive high-level object-o
ii python-apt 0.6.16 Python interface to libapt-pkg
wajig recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
