Your message dated Sun, 4 Nov 2007 11:45:12 +1100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#445713: wajig: bash completion doesn't offer "autoremove"
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: wajig
Version: 2.0.37
Severity: minor
There may be others; probably worth checking.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (700, 'testing'), (600, 'experimental'), (600, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-2-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/dash
Versions of packages wajig depends on:
ii apt 0.7.6 Advanced front-end for dpkg
ii dselect 1.14.6 user tool to manage Debian package
ii python 2.4.4-6 An interactive high-level object-o
ii python-apt 0.7.3.1 Python interface to libapt-pkg
ii python-central 0.5.15 register and build utility for Pyt
wajig recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Received Mon 08 Oct 2007 8:18am +1000 from Reuben Thomas:
> Package: wajig
> Version: 2.0.37
> Severity: minor
>
> There may be others; probably worth checking.
>
[...]
Thanks Reuben. The oversight has been fixed. Problem as that the
command was not listed in the list of commands that "wajig commands"
reports. Now fixed in 2.0.38 which should be in the Debian archives in
a day or two.
Regards,
Graham
--- End Message ---
