Package: wajig Version: 2.0.22 Severity: minor
Something appears to have gone wrong with the new package count in recent versions of wajig -- not sure where it started. Consider this snippet: Replacing available packages info, using /var/cache/apt/available. Information about 16400 package(s) was updated. This is the same as the previous count with 9795 new packages. There are 11 new upgrades [EMAIL PROTECTED]:~# wajig new No new packages It may be the very latest version, 22. I had the same behavior yesterday. The response to the command wajig new is correct and not affected. Cheers, Dave -- System Information: Debian Release: sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-ac8 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages wajig depends on: ii apt 0.5.28.1 Advanced front-end for dpkg ii python 2.3.5-1 An interactive high-level object-o ii python-apt 0.5.10 Python interface to libapt-pkg -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
