reopen 411075
thanks

Hello Pierre,
first of all, sorry if there a e-mail problems. I can receive e-mails
via the BTS (and almost all recipients I know of) quite fine, so can
you please provide me with the detailed error, I'll forward that to my
admin to get this problem fixes ASAP. Thanks!
For the moment, best to use [EMAIL PROTECTED]

Secondly for this bug.
a) Even old code can have bugs, this is IMHO not a too strong argument. Usually
   I updated lots of packages at a time, so *I* would not notice if
   one or two changelog entries would be missing, but now with the
   freeze in effect, I do catch missing ones (two examples confirmed
   already). I might, of course, also "catch" non-issues, like the one
   you pointed out in the original report.

b) As I understood the BTS so far, bugs are closed if either a
   resolution is found (i.e. a patch, a working version, ...) or both
   parties agree. If I get a bug for my package which I cannot
   reproduce, I tag them "unreproducible" or "help" if I miss the
   (hardware, knowledge, ...) to solve it. I only close it if I am
   confident that the bug is understood and solved or the submitter
   agrees that there is no bug. This topic, btw., is also an article
   in the current DWN. 

c) Yes, I updated fetchmail-ssl (no first install). From dpkg.log:
2007-02-14 21:56:24 upgrade fetchmail-ssl 6.2.5-12sarge4 6.2.5-12sarge5
2007-02-14 21:56:24 status half-configured fetchmail-ssl 6.2.5-12sarge4
2007-02-14 21:56:24 status unpacked fetchmail-ssl 6.2.5-12sarge4
2007-02-14 21:56:24 status half-installed fetchmail-ssl 6.2.5-12sarge4
2007-02-14 21:56:24 status half-installed fetchmail-ssl 6.2.5-12sarge4
2007-02-14 21:56:24 status unpacked fetchmail-ssl 6.2.5-12sarge5
2007-02-14 21:56:24 status unpacked fetchmail-ssl 6.2.5-12sarge5
2007-02-14 21:56:24 status unpacked fetchmail-ssl 6.2.5-12sarge5
2007-02-14 21:56:24 status half-configured fetchmail-ssl 6.2.5-12sarge5
2007-02-14 21:56:24 status installed fetchmail-ssl 6.2.5-12sarge5

d) Today only two packages were upgraded: foomatic-filters and
   libnautilus-burn3 but I only saw the changelog for the former:
Abhängigkeitsbaum wird aufgebaut... Fertig
Berechne Upgrade...Fertig
Die folgenden Pakete sind zurückgehalten worden:
  wmaker
Die folgenden Pakete werden aktualisiert:
  foomatic-filters libnautilus-burn3
2 aktualisiert, 0 neu installiert, 0 zu entfernen und 1 nicht aktualisiert.
Es müssen 224kB Archive geholt werden.
Nach dem Auspacken werden 36,9kB Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren [J/n]?
Hole:1 http://127.0.0.1 etch/main foomatic-filters 3.0.2-20061031-1.2 [139kB]
Hole:2 http://127.0.0.1 etch/main libnautilus-burn3 2.14.3-8+b1 [85,0kB]
Es wurden 224kB in 0s geholt (273kB/s)
Lese Changelogs... Fertig
foomatic-filters (3.0.2-20061031-1.2) unstable; urgency=low

  * Non-maintainer upload to fix pending l10n issues.
  * Debconf translations:
    - Translation files converted to UTF-8
    - Czech. Closes: #408722
    - Portuguese. Closes: #409210

 -- Christian Perrier <[EMAIL PROTECTED]>  Fri,  2 Mar 2007 07:39:27 +0100

Again citing dpkg.log:
2007-03-13 18:06:45 upgrade libnautilus-burn3 2.14.3-8 2.14.3-8+b1
2007-03-13 18:06:45 status half-configured libnautilus-burn3 2.14.3-8
2007-03-13 18:06:45 status unpacked libnautilus-burn3 2.14.3-8
2007-03-13 18:06:45 status half-installed libnautilus-burn3 2.14.3-8
2007-03-13 18:06:46 status half-installed libnautilus-burn3 2.14.3-8
2007-03-13 18:06:46 status unpacked libnautilus-burn3 2.14.3-8+b1
2007-03-13 18:06:46 status unpacked libnautilus-burn3 2.14.3-8+b1
2007-03-13 18:06:47 status unpacked foomatic-filters 3.0.2-20061031-1.2
2007-03-13 18:06:47 status half-configured foomatic-filters 3.0.2-20061031-1.2
2007-03-13 18:06:49 status installed foomatic-filters 3.0.2-20061031-1.2
2007-03-13 18:06:49 status unpacked libnautilus-burn3 2.14.3-8+b1
2007-03-13 18:06:49 status half-configured libnautilus-burn3 2.14.3-8+b1
2007-03-13 18:07:10 status installed libnautilus-burn3 2.14.3-8+b1


e) So, if I understood you correct, I should run the following sequence:
db4.2_dump /var/lib/apt/listchanges.db > /tmp/listbefore
script apt-get /tmp/distupgrade
db4.2_dump /var/lib/apt/listchanges.db > /tmp/listafter

   and if I notice a problem, send you the diff of before and after,
   correct?

   I added that in a script, and will try to use it every time I
   update and send you the result (i.e. the diff) once I caught one.
   In the next weeks I will probably updated infrequently, so please be
   patient.

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/

Attachment: signature.asc
Description: Digital signature

Reply via email to