Your message dated Thu, 28 Sep 2006 01:56:19 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line not a bug
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.57
If i redirect the output of apt-listchanges to a file, this file gets
lots of lines with "Reading changelogs... 0%^MReading changelogs...
0%^M".
$ cd /var/cache/apt/archives
$ apt-listchanges *deb > /tmp/listchanges
$ less /tmp/listchanges
Reading changelogs... 0%^MReading changelogs... 0%^MReading
changelogs... 1%^MReading changelogs... 1%^MReading changelogs... 1%
Reading changelogs... 2%^MReading changelogs... 2%^MReading
changelogs... 2%^MReading changelogs... 3%^MReading changelogs... 3%
Reading changelogs... 3%^MReading changelogs... 4%
...
....
This works OK, though:
$ head /tmp/listchanges
Reading changelogs... Done
cyrus-sasl2 (2.1.19-1.5) unstable; urgency=emergency
...
...
I don't know if this is the intended behaviour, or what could be done.
I suppose sending it to stderr wouldn't be a good solution either.
--- End Message ---
--- Begin Message ---
--- End Message ---
