Bug#432266: wajig: details doesn't work on installed but unavailable packages

2009-04-08 Thread 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

Bug#432266: wajig: details doesn't work on installed but unavailable packages

2009-04-07 Thread Graham Williams
Hi Reuben, I'm looking to close out some long outstanding wajig bugs. I'm thinking to close this one - perhaps its a wishlist? Or would you have some suggested code to update? Thanks, Graham Received Mon 09 Jul 2007 9:13am +1000 from Reuben Thomas: Package: wajig Version: 2.0.36 Severity:

Bug#432266: wajig: details doesn't work on installed but unavailable packages

2009-04-07 Thread Reuben Thomas
On Tue, 7 Apr 2009, Graham Williams wrote: I'm looking to close out some long outstanding wajig bugs. I'm thinking to close this one - perhaps its a wishlist? Or would you have some suggested code to update? As far as I can see it's a bug: wajig detail's documentation in wajig listcommands

Bug#432266: wajig: details doesn't work on installed but unavailable packages

2007-07-08 Thread Reuben Thomas
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: