Your message dated Mon, 07 Oct 2024 12:19:41 +0000
with message-id <e1sxmid-00gkft...@fasolo.debian.org>
and subject line Bug#1083066: fixed in apt-listchanges 4.8
has caused the Debian Bug report #1083066,
regarding apt-listchanges: crazy CPU use since v4.6
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 ow...@bugs.debian.org
immediately.)
--
1083066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-listchanges
Version: 4.7
Severity: important
Dear Maintainer,
since v4.6 entered testing I noticed extremely high CPU temperatures on my
laptop (97°C while writing down this bug report); apt-listchanges hogs one CPU
thread, which stays at 100% with the command
apt-get -qq changelog [packagename]=[version]
I currently have 5835 packages installed on my laptop and each command requires
more than 9 seconds; if that command needs to be run for each installed
package, it means that at least 14.5 hours with a CPU at 90+°C are required to
completely populate the database and this, frankly speaking, doesn't seem
acceptable to me.
v3.x version of apt-listchanges didn't have such issues.
Thanks
-- Package-specific info:
==> /etc/apt/listchanges.conf <==
[apt]
frontend=pager
which=news
email_address=root
email_format=text
confirm=false
headers=false
reverse=false
save_seen=/var/lib/apt/listchanges
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-security'), (500,
'proposed-updates'), (500, 'oldstable-security'), (500, 'oldoldstable'), (500,
'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to it_IT.UTF-8), LANGUAGE=it
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages apt-listchanges depends on:
ii apt 2.9.8
ii debconf [debconf-2.0] 1.5.87
ii python3 3.12.6-1
ii python3-apt 2.9.0+b1
ii python3-debconf 1.5.87
ii sensible-utils 0.0.24
ii ucf 3.0043+nmu1
apt-listchanges recommends no packages.
Versions of packages apt-listchanges suggests:
ii chromium [www-browser] 129.0.6668.70-1
ii exim4-daemon-light [mail-transport-agent] 4.98-1
ii falkon [www-browser] 24.08.1-1
ii firefox [www-browser] 130.0.1-1
ii gnome-terminal [x-terminal-emulator] 3.54.0-1
ii konqueror [www-browser] 4:22.12.3-2+b3
ii konsole [x-terminal-emulator] 4:23.08.1-1+b1
ii lynx [www-browser] 2.9.2-1
ii python3-gi 3.48.2-1+b1
ii w3m [www-browser] 0.5.3+git20230121-2+b3
ii xterm [x-terminal-emulator] 394-1
-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: apt-listchanges
Source-Version: 4.8
Done: Jonathan Kamens <j...@kamens.us>
We believe that the bug you reported is fixed in the latest version of
apt-listchanges, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1083...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonathan Kamens <j...@kamens.us> (supplier of updated apt-listchanges package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 06 Oct 2024 14:56:36 -0400
Source: apt-listchanges
Built-For-Profiles: noudeb
Architecture: source
Version: 4.8
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Kamens <j...@kamens.us>
Changed-By: Jonathan Kamens <j...@kamens.us>
Closes: 1083066 1083245
Changes:
apt-listchanges (4.8) unstable; urgency=medium
.
* When a package has both regular changelog entries and binnmu changelog
entries, we need to display both of them, not just the binnmu entries.
(Closes: #1083066)
* When we are trying to read changelog entries from an installed package
and we find binnmu entries but no regular changelog entries, treat
that as a successful read. Previously, this would be interpreted as
there being no locally installed changelog files so the program would
attempt to fetch changelog entries over the network unnecessarily.
* German program translation update courtesy of Helge Kreutzmann.
(Closes: #1083245)
* Galician debconf translation update courtesy of Pablo.
Checksums-Sha1:
46b2215a68b9637e8d61bfebc919337513412407 1967 apt-listchanges_4.8.dsc
fcb0d80d26c824e0b87b7429a3d92ed8c617d8d4 484364 apt-listchanges_4.8.tar.xz
50aa87410ec2b30de37ef2679286b3de8b251abf 14832
apt-listchanges_4.8_source.buildinfo
Checksums-Sha256:
9f3fbff6763518daca763c3630da47f6749ff148572fe438e27d5b40829eaf15 1967
apt-listchanges_4.8.dsc
8508b6fd2a3e2f18f55956038713a093eb3c4ceba71ff259dd9d3b38659e8517 484364
apt-listchanges_4.8.tar.xz
ff4ac83eacf0fdfe2653bbf61dcc8cac262c30e38324bfa5d3f0420aeab416b0 14832
apt-listchanges_4.8_source.buildinfo
Files:
bd854654b3a5286b0f97b215ef53bbe4 1967 utils standard apt-listchanges_4.8.dsc
3cd745ad0a8ebefc3a4268cd7fa4ee37 484364 utils standard
apt-listchanges_4.8.tar.xz
31890b989c2acd13e2c0c6d3951d29f7 14832 utils standard
apt-listchanges_4.8_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEd8lhnEnWos3N8v+qQoMEoXSNzHoFAmcDldwACgkQQoMEoXSN
zHrYUg/5AYYf95i13uMha2W2Sv9RxuBhHt9p3YA3DoZLiJQOxvPjZeVddSfwe7K0
zeAxqwcsR6bR0OBdynImNMm6dLXLI+KIXi+uH+JCjOuXuB7M7XnL9hSMYgfDqeGv
0YbxrBmlMkTsHUlmx6a4m63n39f+bnMOaIaYkP7ronLLsjrie1CyqZL2IFBlhJsz
y3iwfUQmaNocsqMU4a3XJ+/xT/5l7saoK0khScNMfznUkvJ9URQSChd2Y0VbgC2V
DZ0xwrft3ZNgvpEM6niZV7jmDodlA56HWm96y/qNdOiRjOM7S2lrKf0blxZ6RLhM
zJqjfQdHGafVb1fC6YNtiwSqnYxZ+RkCu0a484Z9FkvsipLVngcdy6dLTW12GWl8
F6nNTXdpUvLQ0mjPfWBQXI7QZ8PphOcKg2FpyXqCzdIp3YHS+PAGkVlPhdNQ1jel
MCw3k705j+0/05y0DbBdaLfL1i1yD3wGvsqyZlNhL9P7btYK22lclXdJ7pIL3ZZK
cWAPSR9oaDqxdsmgZ9QL1DZaZV6L0CDOLtkFBD7NBtCVFEgWLkdF9+G1bIdIIUF6
EamKc6FSnK/DuSaN7GonSgYrcgwBOlgTEN3IGU6/CyWwTIl3ELQIGZma7eDCrWOg
DJvLk1jYR23cLLc8Bwbmu25vwTkX/d5zjK6XgHTrBYHK2gk078g=
=YKG3
-----END PGP SIGNATURE-----
pgp5fUiDYngaF.pgp
Description: PGP signature
--- End Message ---
