Your message dated Mon, 12 Mar 2007 23:57:49 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#414616: apt-listchanges: Please explain how to report bugs 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: apt-listchanges Version: 2.72.5 Severity: wishlist Hello, a while ago I reported a bug in apt-listchanges (#411075). You closed it without giving me a chance to explain/answer your questions. I provided more information, but you (unfortunately) did not respond. As I see the bug over and over again (I just saved a log of it again) I would like to report it so it can get tracked down and fixed. I know how to work with the Debian BTS, its tags and severities. Since you obviously have a different mode of operation of the BTS, I want to know how to report bugs in apt-listchanges. I looked in /usr/share/doc/apt-listchanges but could not find any special instructions, unfortunately. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19.2-grsec-cz01 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages apt-listchanges depends on: ii apt 0.6.46.4-0.1 Advanced front-end for dpkg ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii debianutils 2.17 Miscellaneous utilities specific t ii python 2.4.4-2 An interactive high-level object-o ii python-apt 0.6.19 Python interface to libapt-pkg ii python-support 0.5.6 automated rebuilding support for p ii ucf 2.0020 Update Configuration File: preserv Versions of packages apt-listchanges recommends: ii exim4 4.63-17 metapackage to ease exim MTA (v4) ii exim4-daemon-light [mail-tran 4.63-17 lightweight exim MTA (v4) daemon -- debconf information: * apt-listchanges/confirm: true * apt-listchanges/email-address: * apt-listchanges/which: both * apt-listchanges/frontend: pager * apt-listchanges/save-seen: true -- Dr. Helge Kreutzmann [EMAIL PROTECTED] Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---On Mon, Mar 12, 2007 at 09:44:35PM +0100, Helge Kreutzmann wrote: > Package: apt-listchanges > Version: 2.72.5 > Severity: wishlist > > Hello, > a while ago I reported a bug in apt-listchanges (#411075). You closed > it without giving me a chance to explain/answer your questions. I > provided more information, but you (unfortunately) did not respond. As > I see the bug over and over again (I just saved a log of it again) I > would like to report it so it can get tracked down and fixed. I closed it because you gave no proof that the bug existed (your examples were not problems I showed that to you) and that: 1/ the package has no known bugs with respect to that feature for _years_ and it's its centra feature. 2/ I never touched any bit of the code that deals with the database so I'm pretty sure I never introduced bugs in it. that weren't there before. Hence I closed it, because I'm confident the bug is not there, and that you did not exhibit a problem I could reproduce. When there is a doubt I do not close bugs like that. Moreover I did answered to you, many times, please read [0]: your damn mail server drops my mail, whereas I do nothing wrong. Fix it, or live with the fact that you won't receive my answers and that you have to poll the BTS to see them. [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411075;msg=25;att=0 > I know how to work with the Debian BTS, its tags and severities. Since > you obviously have a different mode of operation of the BTS, I want to I don't, I treated that bug quickly because I'm sure it does not exists. You can reopen whichever time you want with a way to reproduce it, sending a mail To: [EMAIL PROTECTED], Cc: [EMAIL PROTECTED] starting with: reopen nnnnnn thanks and with the example of the problem in it (old database, package that caused the problem, and new database). I see nothing to fix here, so I'll close that bug. please try to contact me directly for "social" issues like that, rather than through the BTS. I'm quite easy to find on IRC too if you use it. Else contacting me on my debian address is fine too. For software bugs, the BTS is obviously better though :) Cheers, -- ·O· Pierre Habouzit ··O [EMAIL PROTECTED] OOO http://www.madism.org
Description: PGP signature
--- End Message ---
