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
See also:
http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&version=all&exact=1&keywords=fetchmail-ssl
> > If you have any suggestions how to debug this, please tell me.
> >
> > and today again:
> > Die folgenden Pakete werden aktualisiert:
> > printconf python-foomatic
> > 2 aktualisiert, 0 neu installiert, 0 zu entfernen und 1 nicht aktualisiert.
> > Es müssen 34,4kB Archive geholt werden.
> > Nach dem Auspacken werden 4096B Plattenplatz zusätzlich benutzt.
> > Möchten Sie fortfahren [J/n]?
> > Hole:1 http://127.0.0.1 etch/main python-foomatic 0.7.7 [18,8kB]
> > Hole:2 http://127.0.0.1 etch/main printconf 0.7.7 [15,6kB]
> > Es wurden 34,4kB in 0s geholt (88,8kB/s)
> > Lese Changelogs... Fertig
> > foomatic-gui (0.7.7) unstable; urgency=low
> >
> > * Non-maintainer upload to fix pending l10n issues
> > * Debconf translation:
> > - German. Closes: #397870
> > - Danish. Closes: #400787
> > - Spanish. Closes: #402237
> > - Galician. Closes: #405392
> > - Portuguese. Closes: #408178
> >
> > -- Christian Perrier <[EMAIL PROTECTED]> Thu, 1 Feb 2007 21:28:40 +0100
> >
> > apt-listchanges: Wollen Sie fortsetzen? [J/n]?
> > Vorkonfiguration der Pakete ...
> >
> > no changelog for printconf ...
>
> [madcoder hades] apt-cache showsrc printconf
> Package: foomatic-gui
> Binary: printconf, foomatic-gui, python-foomatic
> [...]
>
> I need better proofs :)
Ok, I see, sorry, missed this one.
> 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).
Greetings
Helge
--
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
