Your message dated Thu, 30 Apr 2009 10:43:56 +1000 with message-id <[email protected]> and subject line Re: Bug#477921: wajig: Fixed script has caused the Debian Bug report #477921, regarding wajig: Please add purge-removed to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 477921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477921 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: wajig Version: 2.0.38 Severity: wishlist I often go through my packages and purge configuration files of removed packages. It'd be nice to do at least one of two things: 1. Have wajig purge prompt. I often want to know whether a purge is likely to cause problems, so I run wajig remove to see if any problems will be caused, then wajig purge to remove the packages. This is to avoid the situation where packages are purged but still installed because of dependency problems, as wajig purge doesn't prompt, but just goes ahead and tries to purge the packages you ask to be purged without first checking dependencies. 2. Add wajig purge-removed to purge packages that have already been removed but have configuration files still in the system. This is useful in its own right e.g. after a system upgrade. I use the following script for this at the moment: dpkg-query -W --showformat='${Package}\t${Status}\n' | grep "deinstall ok config-files" | cut -f 1 | xargs wajig purge The only obvious problem is that it gives an ugly error message if no such packages are in the system, but there may be other subtleties I'm unaware of. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (700, 'testing'), (601, 'unstable'), (600, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages wajig depends on: ii apt 0.7.11 Advanced front-end for dpkg ii dselect 1.14.16.6 user tool to manage Debian package ii python 2.4.4-6 An interactive high-level object-o ii python-apt 0.7.5 Python interface to libapt-pkg ii python-central 0.6.5 register and build utility for Pyt wajig recommends no packages. -- no debconf information
--- End Message ---
--- Begin Message ---I've updated the purge-removed command (has been there since 2 Jun 2008) to use dpkg purge rather than apt-get. Seems to work better but could not see any documented reason why I used apt=get originally rather than dpkg. dpkg is what wajig purge uses. So in 2.0.42 wajig purge-removed should be more in line with purge. This close this bug report again? Please reopen if needed. I'm not sure why it was not closewd with wajig 2.0.39. Regards, Graham Received Thu 30 Apr 2009 2:12am +1000 from Reuben Thomas: > Package: wajig > Version: 2.0.38 > Followup-For: Bug #477921 > > Sorry, the last version was wrong. This one is actually correct and tested. > > -- System Information: > Debian Release: 5.0.1 > APT prefers stable > APT policy: (500, 'stable') > Architecture: i386 (i686) > > Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages wajig depends on: > ii apt 0.7.20.2+lenny1 Advanced front-end for dpkg > ii dselect 1.14.25 Debian package management > front-en > ii python 2.5.2-3 An interactive high-level > object-o > ii python-apt 0.7.7.1+nmu1 Python interface to libapt-pkg > ii python-central 0.6.8 register and build utility for > Pyt > > wajig recommends no packages. > > Versions of packages wajig suggests: > pn alien <none> (no description available) > pn apt-listbugs <none> (no description available) > pn apt-move <none> (no description available) > ii apt-show-versions 0.15 lists available package versions > w > ii debconf 1.5.24 Debian configuration management > sy > ii deborphan 1.7.27 program that can find unused > packa > pn dpkg-repack <none> (no description available) > ii fakeroot 1.11 Gives a fake root environment > ii fping 2.4b2-to-ipv6-15 sends ICMP ECHO_REQUEST packets > to > pn gkdebconf <none> (no description available) > pn gnome-tasksel <none> (no description available) > pn gnome-terminal <none> (no description available) > ii locales 2.7-18 GNU C Library: National Language > ( > pn lynx <none> (no description available) > pn python-glade2 <none> (no description available) > pn python-gnome2 <none> (no description available) > pn python-gtk2 <none> (no description available) > ii reportbug 3.48 reports bugs in the Debian > distrib > ii sudo 1.6.9p17-2 Provide limited super user > privile > pn vrms <none> (no description available) > ii wget 1.11.4-2 retrieves files from the web > > -- no debconf information > #! /bin/sh > # Purge removed packages > packages=`dpkg-query -W --showformat='${Package}\t${Status}\n' | grep > "deinstall ok config-files" | cut -f 1` > if [ "x$packages" != x ]; then > wajig purge $packages > fi
--- End Message ---
