[Reportbug-maint] Bug#517989: how does one use reportbug to follow up on packages marked for removal?
arthur.marsh at internode.on.net
Tue Mar 3 12:03:38 UTC 2009
Hi, I was about to report a bug on package grip when I found in
reportbug that it had been marked for removal.
What neither reportbug nor the emails indicating the packages removal
made clear was how to post a follow-up message in reportbug.
Could I have just done a follow-up in reportbug on one of the grip
Is there a way in reportbug to get browse the packages recently marked
for removal from Debian?
Is there a way in that reportbug could make clear how to post a
follow-up to a package marked for removal from Debian?
-- Package-specific info:
** Environment settings:
realname "Arthur Marsh"
email "arthur.marsh at internode.on.net"
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.28 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages reportbug depends on:
ii apt 0.7.20.2 Advanced front-end for dpkg
ii python 2.5.4-2 An interactive high-level object-o
ii python-central 0.6.11 register and build utility for Pyt
reportbug recommends no packages.
Versions of packages reportbug suggests:
ii debconf-utils 1.5.25 debconf utilities
ii debsums 2.0.41 verification of installed package
ii dlocate 0.96.1 fast alternative to dpkg -L and dp
ii exim4 4.69-9 metapackage to ease Exim MTA (v4)
ii exim4-daemon-light [mail-tran 4.69-9 lightweight Exim MTA (v4) daemon
ii file 4.26-2 Determines file type using "magic"
ii gnupg 1.4.9-4 GNU privacy guard - a free PGP rep
pn python-urwid <none> (no description available)
-- debconf-show failed
More information about the Reportbug-maint