Your message dated Fri, 1 May 2009 12:51:30 +1000
with message-id <[email protected]>
and subject line Re: Bug#432266: wajig: details doesn't work on installed but
unavailable packages
has caused the Debian Bug report #432266,
regarding wajig: details doesn't work on installed but unavailable packages
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.)
--
432266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432266
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wajig
Version: 2.0.36
Severity: normal
wajig details doesn't work on packages that are not installable, but
are installed. This is not a big surprise, as -t reveals that it uses
apt-cache avail. I guess that if this fails, it should try "dpkg -S".
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-4-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.3 Advanced front-end for dpkg
ii dselect 1.14.4 user tool to manage Debian package
ii python 2.4.4-6 An interactive high-level object-o
ii python-apt 0.7.2 Python interface to libapt-pkg
wajig recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Reuben,
I've been testing this. It does not work properly, in that it does not
work in the context of the describe and new commands, for example,
where only a single line is generated (verbose==0).
I think the right solution lays somewhere in the get_available
function in commands.py instead. That is where dumpavail is being
used. I'm now augmenting dumpavali with the /var/lib/dpkg/status file
so that it also handles installed but no longer available
packages.
Testing indicates it works in multiple scenarios.
It will be in 2.0.44.
I'll close this bug report now.
Regards,
Graham
Received Thu 09 Apr 2009 8:25am +1000 from Reuben Thomas:
> Updated patch attached. Two changes:
>
> 1. Use grep-status instead of dpkg. This means needing dctrl-tools for
> describe. Is that a big deal? It has the desired behaviour with respect
> to exit codes, i.e. 0 for an installed package, 1 otherwise (dpkg
> --status exits with 0 for an available or installed package, 1
> otherwise).
>
> 2. I removed the lines of "=====" from wajig detail's output when it uses
> a dpkg command, as its apt-cache-using output doesn't put these lines in.
> --- commands.py.bak 2008-12-01 10:21:56.000000000 +0000
> +++ commands.py 2009-04-08 22:59:18.000000000 +0100
> @@ -219,8 +219,12 @@
> if package_files:
> for f in package_files:
> perform.execute("dpkg-deb --info %s" % f)
> - print "="*72
> sys.stdout.flush()
> + l = package_names[:]
> + for p in l:
> + if perform.execute("grep-status -PX %s" % p) == 0:
> + sys.stdout.flush()
> + package_names.remove(p)
> if package_names:
> packages = package_names
> else:
--- End Message ---
