Your message dated Mon, 25 Sep 2023 09:05:43 -0400 with message-id <8b18cd22-e48a-4d0d-a36a-621132fb4faf@kamens.us> and subject line Re: tag moreinfo 926175 has caused the Debian Bug report #926175, regarding apt-listchanges: only a single changelog is shown when multiple packages are updated 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 926175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926175 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: apt-listchanges: only a single changelog is shown when multiple packages are updated
- From: Nicholas Joll <najoll@posteo.net>
- Date: Mon, 1 Apr 2019 15:25:00 +0100
- Message-id: <2e670cfb-20e1-b83a-e072-c7a8957f2cd5@posteo.net>
Package: apt-listchanges
Version: 3.16
Kernel: 5.0.5-050005-generic
libc-2.27.so
Linux Mint 19.1 x64 Cinnamon
When I update >1 package at once, and whether using Mint's 'Mint Update tool' or apt, apt-list changes only displays a changelog for *one* of the packages.
My listchanges.conf file:
[apt]
frontend=gtk
which=both
email_address=none
email_format=text
confirm=true
headers=false
reverse=false
save_seen=/var/lib/apt/listchanges.db
no_network=false
--- End Message ---
--- Begin Message ---
- To: 926175-done@bugs.debian.org
- Subject: Re: tag moreinfo 926175
- From: Jonathan Kamens <jik@kamens.us>
- Date: Mon, 25 Sep 2023 09:05:43 -0400
- Message-id: <8b18cd22-e48a-4d0d-a36a-621132fb4faf@kamens.us>
- In-reply-to: <YNlifqPPhdR863ix@brians-debian>
- References: <YNlifqPPhdR863ix@brians-debian> <YNlifqPPhdR863ix@brians-debian>
I'm going to close this bug because it's not reproducible and we haven't heard back from the reporter in a couple of years.
Also, this may be the same as bug #383803, which I have a fix for that I hope to release shortly.
--- End Message ---