On Fri, Feb 16, 2007 at 06:39:13PM +0100, Helge Kreutzmann wrote: > On Thu, Feb 15, 2007 at 10:18:16PM +0100, Pierre Habouzit wrote: > > > As you can see (sorry for the German text) "fetchmail-ssl" was downloaded > > > and installed, but *no* changelog was shown, even though "Reading > > > Changelogs" was displayed. > > > > fetchmail-ssl is not in the archive ... So I cannot say, I don't where > > it comes from ... > > fetchmail-ssl: > Installiert:6.2.5-12sarge5 > Mögliche Pakete:6.2.5-12sarge5 > Versions-Tabelle: > *** 6.2.5-12sarge5 0 > 500 http://127.0.0.1 sarge/updates/main Packages > 100 /var/lib/dpkg/status > > This is an apt-proxy for http://security.debian.org
okay, are you _sure_ you _never_ installed fetchmail-ssl ? also consider that no changelog is shown upon first install. > > Closing except if you have more consistent things to show. > > Could you first provide me with an URL of bugs handling? > As I understood and practiced the BTS so far, the maintainer tries to > reproduce the bug first. If there are problems in the bug report or > missing information, he first asks the submitter to clarify, giving > him hints what to check. While this investigation is in progress, the > bug is marked "unreproducible". Once it becomes clear (if possible for > both sides) that there is no bug, the non-bug gets closed, or tagged > "wontfix" if the submitter still believes a bug to be there. Since I > did not know how to reproduce the problem until I saw the first > example, I asked you for advice. Maybe I am always wrong, as clearly > shown by you in the second "example". But I did not even get a chance > to reply or clarify. > > I still think that something is not working right. Instead of playing > bug ping-pong I'd rather ask you how your bugs are supposed to be > handled (URL is fine). I could have done that, but this bit of the apt-listchanges code is _very_ old (like in very well toroughly tested) and I don't really think there is a bug. You can e.g. use db_dump (in dbX.Y-util) on /var/lib/apt/listchanges.db you will have a succession of hex lines, they are alternatively a package name, and a version. Though, after an upgrade that file would have changed and there is no way to know if anything changed afaict. The sole solution is to store that db before apt-get update, do the upgrade, find the diff, and be sure it showed you the diff. -- ·O· Pierre Habouzit ··O [EMAIL PROTECTED] OOO http://www.madism.org
pgp5KMBijDbUE.pgp
Description: PGP signature
