Bug#1053696: Upgrading Python packages showed numerous ancient changelog entries

2023-10-09 Thread Russ Allbery
Jonathan Kamens writes: > TLDR this will be fixed in 4.1 and it's a significant enough fix that I > should probably release 4.1 to experimental Great, thank you! Let me know when that's ready to go. > So, this was one of the edge cases mentioned in the design documentation > for the revamped

Bug#1053696: Upgrading Python packages showed numerous ancient changelog entries

2023-10-09 Thread Jonathan Kamens
TLDR this will be fixed in 4.1 and it's a significant enough fix that I should probably release 4.1 to experimental So, this was one of the edge cases mentioned in the design documentation for the revamped changelog filtering logic: when the persistent database is not being used in a

Bug#1053696: Upgrading Python packages showed numerous ancient changelog entries

2023-10-08 Thread Jonathan Kamens
You don't have to look into it anymore, I know what's happening. ;-) Been working on it for a couple of hours. Will have an update in the morning, no time to write it up now. Thanks for the report! jik On 10/8/23 22:23, Russ Allbery wrote: Package: apt-listchanges Version: 4.0

Bug#1053696: Upgrading Python packages showed numerous ancient changelog entries

2023-10-08 Thread Russ Allbery
Package: apt-listchanges Version: 4.0 Followup-For: Bug #1053696 X-Debbugs-Cc: r...@debian.org Same thing happened with the following upgrades: Unpacking gcc-12 (12.3.0-10) over (12.3.0-9) ... Unpacking libgcc-12-dev:amd64 (12.3.0-10) over (12.3.0-9) ... Unpacking cpp-12 (12.3.0-10) over

Bug#1053696: Upgrading Python packages showed numerous ancient changelog entries

2023-10-08 Thread Russ Allbery
Package: apt-listchanges Version: 4.0 Severity: normal X-Debbugs-Cc: r...@debian.org An apt run that included the following upgrades: Unpacking python3.11-dev (3.11.6-3) over (3.11.6-2) ... Unpacking libpython3.11-dev:amd64 (3.11.6-3) over (3.11.6-2) ... Unpacking libpython3.11:amd64 (3.11.6-3)