#1085722 apt-listchanges: displays all old entries for some packages

Package:
apt-listchanges
Source:
apt-listchanges
Submitter:
Raphaël Halimi
Date:
2026-01-19 00:35:01 UTC
Severity:
normal
#1085722#5
Date:
2024-10-22 09:57:40 UTC
From:
To:
Dear developer,

The new version of TLP displays (or sends, for e-mails) all older
entries for some packages.

To date, it happened to me three times (I wanted to be sure before
filing a bug report) with two packages : linux (going back all the way
to 4.19.37-6) and gcc-defaults (going back all the way to 0.2).

It seems these entries come from the online changelogs (the local ones
don't go back so far).

I keep all my e-mails so I can send them to you privately if you wish.

Regards,
#1085722#10
Date:
2024-10-22 14:19:16 UTC
From:
To:
I don't understand that "TLP" means in this context ("The new version of
TLP displays..."). The only "TLP" I'm aware of is the laptop battery
optimization package which doesn't make sense here.

It would be helpful for me to see your apt-listchanges configuration,
but you didn't include it here even though `reportbug apt-listchanges`
would include it automatically. Can you please run that command and then
copy and paste the automatically generated information in the template
that reportbug generates into a reply to this ticket so I can see your
configuration?

There is no Debian package with the exact name "linux" so I need more
specifics about exactly what package you're referring to there.

I also don't understand what package you're referring to when you
mention "gcc-defaults". `apt search gcc-defaults` doesn't yield any
results. I have gcc installed on my system and I do not have a package
called "gcc-defaults".

Are you using a distribution other than stock Debian? If so, what
distribution?
#1085722#15
Date:
2024-10-22 18:27:59 UTC
From:
To:
Le 22/10/2024 à 16:19, Jonathan Kamens a écrit :

Hi,

Sorry for the confusion. I rally don't know why I wrote "TLP" (I'm the
maintainer of this package), I of course meant apt-listchanges.

Sorry, of course. The required information is included at the end.

It seems those are the source packages names. They are in the changelog
files. I can send you apt-listchanges' e-mails privately if you want.

No, I'm using plain Debian unstable (with a couple of other repositories
but not many packages).

reportbug information :
#1085722#20
Date:
2024-11-11 09:18:44 UTC
From:
To:
Hi,

Tired of receiving 2.5 MB e-mails every time the kernel was upgraded, in
an attempt to work around the problem, I changed apt-listchanges'
configuration to disable the download of changelogs from the network
(since the one in the package is truncated, I told myself that I may get
a bunch of already seen entries, but a lot less).

Today, the kernel was upgraded in Sid, and for the first time since the
major overhaul, apt-listchanges behaved correctly, displaying only the
latest changelog entry, instead of going back to the bottom of the
changelog file, which means it correctly identified the entries I've
already seen, and eliminated them.

Why are local changelogs (extracted from packages) and remote ones
(downloaded from Internet) treated differently ? Are they processed by
two different algorithms ?

Regards,
#1085722#25
Date:
2024-11-11 21:21:41 UTC
From:
To:
Hi,

My apologies for the delay getting back to you about this.

If you can, please do the following to help me debug this further:

 1. Undo the configuration change described in your email.
 2. Add `capture_snapshots=yes` to /etc/apt/listchanges.conf in the
    `[apt]` section.
 3. Add `snapshot_dir=/var/lib/apt/listchanges-snapshots` to
    /etc/apt/listchanges.conf in the `[apt]` section.
 4. Wait until the next time the problem happens.
 5. Right after it happens, send me (preferably by uploading it
    somewhere temporarily and sending me a link privately, rather than
    by attaching it to the ticket) the newest snapshot file in
    /var/lib/apt/listchanges-snapshots.
 6. Then you can either remove the settings you added to
    `listchanges.conf` or change `capture_snapshots` to `auto` which
    will disable snapshots until/unless you later install an
    experimental version of apt-listchanges.

I hope the snapshot of the run which has this problem will give me the
information I need to be able to figure out what's going wrong and how
to fix it.

If you want to read more about the snapshot functionality see the
comment at the top of this file
<https://salsa.debian.org/debian/apt-listchanges/-/blob/debian/unstable/apt_listchanges/snapshot.py>.

Thanks,

jik
#1085722#30
Date:
2024-11-19 08:47:16 UTC
From:
To:
Le 11/11/2024 à 22:21, Jonathan Kamens a écrit :

Done.

Regards,
#1085722#35
Date:
2025-02-10 11:41:34 UTC
From:
To:
I've also been seeing old entries for some packages, for instance,
concerning packages of gcc-mingw-w64 source today.

The currently installed version of one of these packages:

cventin:~> dpkg -s gcc-mingw-w64-i686
Package: gcc-mingw-w64-i686
Status: install ok installed
Priority: optional
Section: devel
Installed-Size: 256
Maintainer: Stephen Kitt <skitt@debian.org>
Architecture: all
Source: gcc-mingw-w64 (26.7)
Version: 13.3.0-12+26.7
[...]

/usr/share/doc/gcc-mingw-w64-i686/changelog.Debian.gz starts with

gcc-mingw-w64 (26.7) unstable; urgency=medium
[...]
 -- Stephen Kitt <skitt@debian.org>  Sat, 18 Jan 2025 18:54:00 +0100

gcc-mingw-w64 (26.6) unstable; urgency=medium
[...]
 -- Stephen Kitt <skitt@debian.org>  Wed, 04 Dec 2024 07:36:40 +0100

gcc-mingw-w64 (26.5) unstable; urgency=medium
[...]
 -- Stephen Kitt <skitt@debian.org>  Wed, 23 Oct 2024 13:20:10 +0200

and so on.

When upgrading to 26.8, "/usr/bin/apt-listchanges --apt" shows

gcc-mingw-w64 (26.8) unstable; urgency=medium
[...]
 -- Stephen Kitt <skitt@debian.org>  Fri, 07 Feb 2025 07:51:32 +0100

gcc-mingw-w64 (26.7) unstable; urgency=medium
[...]
 -- Stephen Kitt <skitt@debian.org>  Sat, 18 Jan 2025 18:54:00 +0100

gcc-mingw-w64 (26.6) unstable; urgency=medium
[...]
 -- Stephen Kitt <skitt@debian.org>  Wed, 04 Dec 2024 07:36:40 +0100

down to the initial release

gcc-mingw-w64 (0.1) unstable; urgency=low
[...]
 -- Stephen Kitt <steve@sk2.org>  Tue, 16 Nov 2010 12:52:08 +0100

My /etc/apt/listchanges.conf file:

[apt]
frontend=pager
email_address=none
confirm=1
save_seen=/var/lib/apt/listchanges
which=both
no_network=false
headers=false
reverse=false

Just in case, "apt-listchanges --dump-seen --profile=apt" gives
information only for packages upgraded earlier today:

packages:
  apt 1739185510 (2025-02-10)
  apt-doc 1739185510 (2025-02-10)
  apt-utils 1739185510 (2025-02-10)
  libapt-pkg6.0t64 1739185510 (2025-02-10)
  linux-compiler-gcc-12-x86 1739185412 (2025-02-10)
  linux-doc-6.1 1739185413 (2025-02-10)
  linux-kbuild-6.1 1739185414 (2025-02-10)
exact checksums:
[...] (all for 2025-02-10)
#1085722#40
Date:
2025-02-10 12:06:06 UTC
From:
To:
[...]
[...]

BTW, like Raphaël, I think I also saw the same issue on the linux and
gcc-defaults source packages (but not always).

There is something in common for these 3 cases: the version of the
binary packages does not match the version of the corresponding source
package. I'm wondering whether this may confuse apt-listchanges.
#1085722#45
Date:
2025-03-02 19:55:29 UTC
From:
To:
On Mon, 10 Feb 2025 13:06:06 +0100 Vincent Lefevre <vincent@vinc17.net>  wrote:
 > BTW, like Raphaël, I think I also saw the same issue on the linux and
 > gcc-defaults source packages (but not always).

Hi, just for information and ready to provide some more if needed,
(I have a apt-listchanges-snapshots_2025-03-02T18:21:06.tar.xz)
I am reproducing the issue systematically when upgrading kernel,
'linux-headers-amd64' in my case;
but not having the issue with 'linux-libc-dev'
..and from my memory starting around linux 6.6 (during bisecting for
#1061521)

Example today for 6.12.16-1 → 6.12.17-1:
(after purging first-install db and re-launching:
'python3 -m apt_listchanges.populate_database --profile apt')
The repeated scheme is always the same:
- it doesn't re-display previous unstable viewed ones
   (today: 6.12.{11,13,15,16}-1)
- always re-display starting from the last from experimental one
   (today: 6.12~rc6-1~exp1),
- until 4.19.37-6

Pkgs:
-----
libc-bin                  2.41-2                     2.41-3
libc-dev-bin              2.41-2                     2.41-3
libc-l10n                 2.41-2                     2.41-3
libc6                     2.41-2                     2.41-3
libc6-dbg                 2.41-2                     2.41-3
libc6-dev                 2.41-2                     2.41-3
locales                   2.41-2                     2.41-3
linux-headers-amd64       6.12.16-1                  6.12.17-1
linux-image-amd64         6.12.16-1                  6.12.17-1
linux-libc-dev            6.12.16-1                  6.12.17-1

Hereafter edited [...] generated listchanges
/tmp/apt-listchanges-kernel.log:

...hope it could be of any help, thank you - cheers
Antoine



apt-listchanges: Changelogs
---------------------------

--- Changes for linux-headers-amd64 ---

linux-signed-amd64 (6.12.17+1) unstable; urgency=medium

   * Sign kernel from linux 6.12.17-1

   * New upstream stable update:
     https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
[...]

  -- Salvatore Bonaccorso <carnil@debian.org>  Sat, 01 Mar 2025 17:57:27
+0100

linux (6.12~rc6-1~exp1) experimental; urgency=medium
[...]
linux (6.11.6-1) unstable; urgency=medium
linux (6.11.5-1) unstable; urgency=medium
linux (6.11.4-1) unstable; urgency=medium
linux (6.11.2-1) unstable; urgency=medium
linux (6.11-1~exp1) experimental; urgency=medium
linux (6.11~rc5-1~exp1) experimental; urgency=medium
linux (6.11~rc4-1~exp1) experimental; urgency=medium
linux (6.10.12-1) unstable; urgency=medium
linux (6.10.11-1) unstable; urgency=medium
linux (6.10.9-1) unstable; urgency=medium
linux (6.10.7-1) unstable; urgency=medium
linux (6.10.6-1) unstable; urgency=medium
linux (6.10.4-1) unstable; urgency=medium
linux (6.10.3-1) unstable; urgency=medium
linux (6.10.1-1~exp1) experimental; urgency=medium
linux (6.10-1~exp1) experimental; urgency=medium
linux (6.9.12-1) unstable; urgency=medium
linux (6.9.11-1) unstable; urgency=medium
linux (6.9.10-1) unstable; urgency=medium
linux (6.9.9-1) unstable; urgency=medium
linux (6.9.8-1) unstable; urgency=medium
linux (6.9.7-1) unstable; urgency=medium
linux (6.9.2-1~exp1) experimental; urgency=medium
linux (6.8.12-1) unstable; urgency=medium
linux (6.8.11-1) unstable; urgency=medium
linux (6.8.9-1) unstable; urgency=medium
linux (6.7.12-1) unstable; urgency=medium
linux (6.7.9-2) unstable; urgency=high
linux (6.7.9-1) unstable; urgency=medium
linux (6.7.7-1) unstable; urgency=medium
linux (6.7.4-1~exp1) experimental; urgency=medium
linux (6.7.1-1~exp1) experimental; urgency=medium
linux (6.7-1~exp1) experimental; urgency=medium
linux (6.6.15-2) unstable; urgency=medium
linux (6.6.15-1) unstable; urgency=medium
linux (6.6.13-1) unstable; urgency=medium
linux (6.6.11-1) unstable; urgency=medium
linux (6.6.9-1) unstable; urgency=medium
linux (6.6.8-1) unstable; urgency=medium
linux (6.6.7-1~exp1) experimental; urgency=medium
linux (6.6.4-1~exp1) experimental; urgency=medium
linux (6.6.3-1~exp1) experimental; urgency=medium
linux (6.5.13-1) unstable; urgency=medium
linux (6.5.10-1) unstable; urgency=medium
linux (6.5.8-1) unstable; urgency=medium
linux (6.5.6-1) unstable; urgency=medium
linux (6.5.3-1) unstable; urgency=medium
linux (6.5.1-1~exp1) experimental; urgency=medium
linux (6.5~rc7-1~exp1) experimental; urgency=medium
linux (6.5~rc6-1~exp1) experimental; urgency=medium
linux (6.5~rc4-1~exp1) experimental; urgency=medium
linux (6.4.13-1) unstable; urgency=medium
linux (6.4.11-1) unstable; urgency=medium
linux (6.4.4-3) unstable; urgency=high
linux (6.4.4-2) unstable; urgency=high
linux (6.4.4-1) unstable; urgency=medium
linux (6.4.1-1~exp1) experimental; urgency=medium
linux (6.4~rc7-1~exp1) experimental; urgency=medium
linux (6.4~rc6-1~exp1) experimental; urgency=medium
linux (6.3.11-1) unstable; urgency=medium
linux (6.3.7-1) unstable; urgency=medium
linux (6.3.5-1~exp1) experimental; urgency=medium
linux (6.3.4-1~exp1) experimental; urgency=medium
linux (6.3.2-1~exp1) experimental; urgency=medium
linux (6.3.1-1~exp1) experimental; urgency=medium
linux (6.1.27-1) unstable; urgency=medium
linux (6.1.25-1) unstable; urgency=medium
linux (6.1.20-2) unstable; urgency=medium
linux (6.1.20-1) unstable; urgency=medium
linux (6.1.15-1) unstable; urgency=medium
linux (6.1.12-1) unstable; urgency=medium
linux (6.1.11-1) unstable; urgency=medium
linux (6.1.8-1) unstable; urgency=medium
linux (6.1.7-1) unstable; urgency=medium
linux (6.1.4-1) unstable; urgency=medium
linux (6.1.2-1~exp1) experimental; urgency=medium
linux (6.1.1-1~exp2) experimental; urgency=medium
linux (6.1.1-1~exp1) experimental; urgency=medium
linux (6.1~rc8-1~exp1) experimental; urgency=medium
linux (6.1~rc7-1~exp1) experimental; urgency=medium
linux (6.1~rc6-1~exp1) experimental; urgency=medium
linux (6.1~rc5-1~exp1) experimental; urgency=medium
linux (6.1~rc3-1~exp1) experimental; urgency=medium
linux (6.0.12-1) unstable; urgency=medium
linux (6.0.10-2) unstable; urgency=medium
linux (6.0.10-1) unstable; urgency=medium
linux (6.0.8-1) unstable; urgency=medium
linux (6.0.7-1) unstable; urgency=medium
linux (6.0.6-2) unstable; urgency=medium
linux (6.0.6-1) unstable; urgency=medium
linux (6.0.5-1) unstable; urgency=medium
linux (6.0.3-1) unstable; urgency=medium
linux (6.0.2-1) unstable; urgency=high
linux (6.0-1~exp1) experimental; urgency=medium
linux (6.0~rc7-1~exp1) experimental; urgency=medium
linux (5.19.11-1) unstable; urgency=medium
linux (5.19.6-1) unstable; urgency=medium
linux (5.19-1~exp1) experimental; urgency=medium
linux (5.19~rc6-1~exp1) experimental; urgency=medium
linux (5.19~rc4-1~exp1) experimental; urgency=medium
linux (5.18.16-1) unstable; urgency=medium
linux (5.18.14-1) unstable; urgency=medium
linux (5.18.5-1) unstable; urgency=medium
linux (5.18.2-1) unstable; urgency=medium
linux (5.18-1~exp1) experimental; urgency=medium
linux (5.17.11-1) unstable; urgency=medium
linux (5.17.6-1) unstable; urgency=medium
linux (5.17.3-1) unstable; urgency=medium
linux (5.17.1-1~exp1) experimental; urgency=medium
linux (5.17~rc8-1~exp1) experimental; urgency=medium
linux (5.17~rc7-1~exp1) experimental; urgency=medium
linux (5.17~rc6-1~exp1) experimental; urgency=medium
linux (5.17~rc5-1~exp1) experimental; urgency=medium
linux (5.17~rc4-1~exp1) experimental; urgency=medium
linux (5.17~rc3-1~exp1) experimental; urgency=medium
linux (5.16.18-1) unstable; urgency=medium
linux (5.16.14-1) unstable; urgency=medium
linux (5.16.12-1) unstable; urgency=high
linux (5.16.11-1) unstable; urgency=medium
linux (5.16.10-1) unstable; urgency=medium
linux (5.16.7-2) unstable; urgency=medium
linux (5.16.7-1) unstable; urgency=medium
linux (5.16.4-1~exp1) experimental; urgency=medium
linux (5.16.3-1~exp1) experimental; urgency=medium
linux (5.16~rc8-1~exp1) experimental; urgency=medium
linux (5.16~rc7-1~exp1) experimental; urgency=medium
linux (5.16~rc6-1~exp1) experimental; urgency=medium
linux (5.16~rc5-1~exp1) experimental; urgency=medium
linux (5.16~rc4-1~exp1) experimental; urgency=medium
linux (5.16~rc3-1~exp1) experimental; urgency=medium
linux (5.16~rc1-1~exp1) experimental; urgency=medium
linux (5.15.15-2) unstable; urgency=high
linux (5.15.15-1) unstable; urgency=high
linux (5.15.5-2) unstable; urgency=medium
linux (5.15.5-1) unstable; urgency=medium
linux (5.15.3-1) unstable; urgency=medium
linux (5.15.2-1~exp1) experimental; urgency=medium
linux (5.15.1-1~exp1) experimental; urgency=medium
linux (5.15-1~exp1) experimental; urgency=medium
linux (5.14.16-1) unstable; urgency=medium
linux (5.14.12-1) unstable; urgency=medium
linux (5.14.9-2) unstable; urgency=medium
linux (5.14.9-1) unstable; urgency=medium
linux (5.14.6-3) unstable; urgency=medium
linux (5.14.6-2) unstable; urgency=medium
linux (5.14.6-1) unstable; urgency=medium
linux (5.14.3-1~exp1) experimental; urgency=medium
linux (5.14.2-1~exp1) experimental; urgency=medium
linux (5.14.1-1~exp1) experimental; urgency=medium
linux (5.14-1~exp2) experimental; urgency=medium
linux (5.14-1~exp1) experimental; urgency=medium
linux (5.13.12-1~exp1) experimental; urgency=medium
linux (5.13.9-1~exp2) experimental; urgency=medium
linux (5.13.9-1~exp1) experimental; urgency=medium
linux (5.10.46-4) unstable; urgency=medium
linux (5.10.46-3) unstable; urgency=medium
linux (5.10.46-2) unstable; urgency=medium
linux (5.10.46-1) unstable; urgency=medium
linux (5.10.40-1) unstable; urgency=medium
linux (5.10.38-1) unstable; urgency=medium
linux (5.10.28-1) unstable; urgency=medium
linux (5.10.26-1) unstable; urgency=medium
linux (5.10.24-1) unstable; urgency=medium
linux (5.10.19-1) unstable; urgency=medium
linux (5.10.13-1) unstable; urgency=medium
linux (5.10.12-1) unstable; urgency=medium
linux (5.10.9-1) unstable; urgency=medium
linux (5.10.5-1) unstable; urgency=medium
linux (5.10.4-1) unstable; urgency=medium
linux (5.10.2-1~exp1) experimental; urgency=medium
linux (5.10.1-1~exp1) experimental; urgency=medium
linux (5.10~rc7-1~exp1) experimental; urgency=medium
linux (5.10~rc6-1~exp1) experimental; urgency=medium
linux (5.10~rc4-1~exp1) experimental; urgency=medium
linux (5.9.15-1) unstable; urgency=medium
linux (5.9.11-1) unstable; urgency=medium
linux (5.9.9-1) unstable; urgency=medium
linux (5.9.6-1) unstable; urgency=medium
linux (5.9.1-1) unstable; urgency=medium
linux (5.9~rc8-1~exp1) experimental; urgency=medium
linux (5.9~rc6-1~exp1) experimental; urgency=medium
linux (5.9~rc4-1~exp1) experimental; urgency=medium
linux (5.8.14-1) unstable; urgency=medium
linux (5.8.10-1) unstable; urgency=medium
linux (5.8.7-1) unstable; urgency=medium
linux (5.8.3-1~exp1) experimental; urgency=medium
linux (5.7.17-1) unstable; urgency=medium
linux (5.7.10-1) unstable; urgency=medium
linux (5.7.6-1) unstable; urgency=medium
linux (5.7~rc5-1~exp1) experimental; urgency=medium
linux (5.6.14-2) unstable; urgency=medium
linux (5.6.14-1) unstable; urgency=medium
linux (5.6.7-1) unstable; urgency=medium
linux (5.6.4-1~exp1) experimental; urgency=medium
linux (5.5.17-1) unstable; urgency=medium
linux (5.5.13-2) unstable; urgency=medium
linux (5.5.13-1) unstable; urgency=medium
linux (5.5~rc5-1~exp1) experimental; urgency=medium
linux (5.4.19-1) unstable; urgency=medium
linux (5.4.13-1) unstable; urgency=medium
linux (5.4.8-1) unstable; urgency=medium
linux (5.4.6-1) unstable; urgency=medium
linux (5.4.2-1~exp1) experimental; urgency=medium
linux (5.4-1~exp1) experimental; urgency=medium
linux (5.3.15-1) unstable; urgency=medium
linux (5.3.9-3) unstable; urgency=medium
linux (5.3.9-2) unstable; urgency=medium
linux (5.3.9-1) unstable; urgency=medium
linux (5.3.7-1) unstable; urgency=medium
linux (5.3.2-1~exp1) experimental; urgency=medium
linux (5.3~rc5-1~exp2) experimental; urgency=medium
linux (5.3~rc5-1~exp1) experimental; urgency=medium
linux (5.2.17-1) unstable; urgency=medium
linux (5.2.9-2) unstable; urgency=medium
linux (5.2.9-1) unstable; urgency=medium
linux (5.2.7-1) unstable; urgency=medium
linux (5.2.6-1) unstable; urgency=medium
linux (5.0.2-1~exp1) experimental; urgency=medium
linux (5.0.1-1~exp1) experimental; urgency=medium
linux (4.20-1~exp1) experimental; urgency=medium
linux (4.19.37-6) unstable; urgency=high
[...]



--- Changes for libc6 ---

glibc (2.41-3) unstable; urgency=medium

   [ Aurelien Jarno ]
   * debhelper.in/libc{,-dev}.lintian-overrides: drop libm related lintian
     overrides, as lintian does not provide a multiarch compatible way to
     provide overrides.  Closes: #1099166, #1099167.
   * debian/salsa-ci.yml: add unpack-message-for-deb-data to
     SALSA_CI_LINTIAN_SUPPRESS_TAGS due to the above.

  -- Aurelien Jarno <aurel32@debian.org>  Sat, 01 Mar 2025 15:24:08 +0100



--- Changes for linux-libc-dev ---

linux (6.12.17-1) unstable; urgency=medium

   * New upstream stable update:
     https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
[...]

  -- Salvatore Bonaccorso <carnil@debian.org>  Sat, 01 Mar 2025 17:57:27
+0100
#1085722#50
Date:
2025-03-02 22:45:33 UTC
From:
To:
Note that in my case, I always upgrade all the packages of the same
source at the same time.

linux-libc-dev can be upgraded alone (well, without the kernel
upgrade), while upgrading linux-headers-amd64 generally installs
a new package, which might confuse apt-listchanges (though there
may be another explanation, see below).

For instance...

linux-headers-amd64 6.12.16-1 depends on linux-headers-6.12.16-amd64
while linux-headers-amd64 6.12.17-1 depends on
linux-headers-6.12.17-amd64. So the new package
linux-headers-6.12.17-amd64 has been installed.

But a more probable cause would actually be linux-image-amd64,
possibly due to the linux-signed-amd64 source.
#1085722#55
Date:
2025-05-01 05:54:08 UTC
From:
To:
this happens to me as well, in my case it is always firefox-esr which
causes apt-listchanges to display the following over and over, years
after the fact:


apt-listchanges: Notizie
------------------------

firefox-esr (60.0esr-1) unstable; urgency=medium

  * The use of `lockPref` in preferences under /etc/firefox-esr is
deprecated.
    Please use `pref("name", value, locked)` instead. `lockPref` will still
    be supported for compatibility purpose until version 67.
#1085722#60
Date:
2026-01-19 00:33:56 UTC
From:
To:
When I run

  apt changelog firefox-esr | grep '^[^ ]'

I get:

firefox-esr (140.7.0esr-1) unstable; urgency=medium
firefox-esr (140.6.0esr-1) unstable; urgency=medium
firefox-esr (140.5.0esr-1) unstable; urgency=medium
firefox-esr (140.4.0esr-1) unstable; urgency=medium
firefox-esr (140.3.1esr-2) unstable; urgency=medium
firefox-esr (140.3.1esr-1) unstable; urgency=medium
firefox-esr (140.3.0esr-2) unstable; urgency=medium
firefox-esr (140.3.0esr-1) unstable; urgency=medium
firefox (140.0.4-1) unstable; urgency=medium
firefox (140.0.1-1) unstable; urgency=medium
firefox (140.0-1) unstable; urgency=medium
firefox (139.0.4-1) unstable; urgency=medium
[...]
firefox (46.0.1-1) unstable; urgency=medium
firefox (46.0-1) unstable; urgency=medium
firefox (45.0.2-1) unstable; urgency=medium
firefox (45.0.1-1) unstable; urgency=medium
firefox (45.0-1) unstable; urgency=medium
firefox-esr (45.0esr-1) unstable; urgency=medium
iceweasel (44.0.2-1) unstable; urgency=medium
iceweasel (44.0-1) unstable; urgency=medium

so there had been a rename from firefox-esr to firefox, then to
firefox-esr again. I suppose that this may confuse apt-listchanges.
But I cannot see firefox-esr 60.0esr-1 in my list!