Jonathan Kamens writes:
> Again, I hate to do this, but until we've figured this out, can the two
> of you please do me a favor? Before you run each apt upgrade, please
> save a backup copy of /var/lib/apt/listchanges, then if the problem
> happens during the upgrade, please send me the backup
Again, I hate to do this, but until we've figured this out, can the two
of you please do me a favor? Before you run each apt upgrade, please
save a backup copy of /var/lib/apt/listchanges, then if the problem
happens during the upgrade, please send me the backup copy of the file
as well as the
I'm afraid it really does happen with 4.1:
niko@niko-desktop:~$ cat /var/log/dpkg.log | grep apt-listchanges | tail -3
2023-10-10 11:28:51 status unpacked apt-listchanges:all 4.1
2023-10-10 11:28:51 status half-configured apt-listchanges:all 4.1
2023-10-10 11:28:52 status installed
I really hate to do this, but I have spent hours constructing test cases
and poring over the code and I can't reproduce this or figure out how it
happened, so I need to ask... can you both please check your
/var/log/dpkg.log and make 100% certain that you had apt-listchanges 4.1
(not 4.0)
I see similar issues with apt-listchanges 4.1 while updating several
other packages:
For the curl update from 8.3.0-2 to 8.3.0-3 apt-listchanges shows all
changes starting from curl 7.65.1-1.
For the debianutils update from 5.13 to 5.14 apt-listchanges shows all
changes starting from
Package: apt-listchanges
Version: 4.1
Severity: normal
X-Debbugs-Cc: r...@debian.org
Looks like some variation of this bug still exists in 4.1, although I'm
not sure if it's the same bug. But the following upgrades:
Unpacking golang-1.21-doc (1.21.3-1) over (1.21.2-1) ...
Unpacking
6 matches
Mail list logo
