- Package:
- apt-listchanges
- Source:
- apt-listchanges
- Submitter:
- Vincent Lefevre
- Date:
- 2026-02-24 03:23:01 UTC
- Severity:
- normal
I currently have kmod and libkmod2 34.2-2;
kmod and libkmod2 34.2-2+b1 are available.
When I want to upgrade kmod (and libkmod2 as a consequence),
apt-listchanges displays:
apt-listchanges: Changelogs
---------------------------
kmod (34.2-2) unstable; urgency=medium
* kmod.initramfs-hook: if compressed modules have been copied to the
initramfs and CONFIG_MODULE_DECOMPRESS=n (which is not the default
in Debian kernels) then also copy the compression libraries needed
by kmod to load them. (Closes: #1099801)
--- Binary NMU of: kmod (34.2-2+b1)
* Binary-only non-maintainer upload for amd64; no source changes.
* Rebuild to enable GCS on arm64
The "kmod (34.2-2+b1)" entry is expected, but not the "kmod (34.2-2)"
one as kmod 34.2-2 is already installed.
This looks different from bug 1085722 as
• apt-listchanges displays a single old entry;
• the version of the binary packages is the same as the version of
the source package;
• the source package kmod hasn't been renamed (in case this matters).
Note that other upgrades that just consist of a "Binary NMU" +b1
(e.g. dbus) do not have this issue, which seems specific to kmod.
Actually there are other packages with the same issue, e.g.
firebird4.0 (4.0.6.3221.ds6-2) unstable; urgency=medium
* -examples: replace firebird4.0-dev recommendation with firebird-dev.
Thanks to Carles Pina i Estany (Closes: #1113833)
* convert debian/watch to version 5
Control: retitle -1 apt-listchanges displays an old entry for some packages with just Binary NMU
[...]
And other ones:
klibc (2.0.14-1) unstable; urgency=medium
* New upstream version:
- parisc: Fix build with Linux 6.10+ (Closes: #1075820)
When running "apt dist-upgrade" today on a system tracking Unstable I got the
below old entries. On that system I have not had inappropriate display of
news entries before and I only got it from the following 3 packages. I have
included my configuration at the bottom which is all the default AFAIK.
tor (0.2.0.26-rc-1) experimental; urgency=critical
* weak cryptographic keys
It has been discovered that the random number generator in Debian's
openssl package is predictable. This is caused by an incorrect
Debian-specific change to the openssl package (CVE-2008-0166). As a
result, cryptographic key material may be guessable.
See Debian Security Advisory number 1571 (DSA-1571) for more information:
http://lists.debian.org/debian-security-announce/2008/msg00152.html
If you run a Tor server using this package please see
/var/lib/tor/keys/moved-away-by-tor-package/README.REALLY