Your message dated Mon, 2 Oct 2023 18:16:46 -0400
with message-id <8981438c-2e75-4565-bb07-479119bc6...@kamens.us>
and subject line I don't think this was an apt-listchanges bug
has caused the Debian Bug report #1026376,
regarding apt-listchanges: Should not emit "WARNING: Unknown distro but dpkg
found, assuming Debian" on Debian (Unstable)
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.)
--
1026376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-listchanges
Version: 3.24
Severity: normal
Hi,
when apt-listchanges is run on my Debian Sid running laptop, it's
emitting this irritating warning:
WARNING: Unknown distro but dpkg found, assuming Debian
Might be related to the changes to /etc/os-release which has changed its
values a bit a few months ago.
-- Package-specific info:
==> /etc/apt/listchanges.conf <==
[apt]
frontend=pager
which=news
email_address=root
email_format=text
confirm=true
headers=true
reverse=false
save_seen=/var/lib/apt/listchanges.db
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'),
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'),
(105, 'experimental-debug')
merged-usr: no
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages apt-listchanges depends on:
ii apt 2.5.4
ii debconf [debconf-2.0] 1.5.80
ii python3 3.10.6-3
ii python3-apt 2.5.0
ii python3-debconf 1.5.80
ii sensible-utils 0.0.17
ii ucf 3.0043
apt-listchanges recommends no packages.
Versions of packages apt-listchanges suggests:
ih chromium [www-browser] 108.0.5359.94-1
ii cool-retro-term [x-terminal-emulator] 1.2.0+ds2-1+b1
ii dillo [www-browser] 3.0.5-7+b1
ii edbrowse [www-browser] 3.7.7-4+b1
ii elinks [www-browser] 0.13.2-1+b4
ii falkon [www-browser] 3.2.0+dfsg1-2
ii firefox [www-browser] 107.0.1-1
ii firefox-esr [www-browser] 102.5.0esr-1
ii kitty [x-terminal-emulator] 0.21.2-2
ii links [www-browser] 2.28-1
ii links2 [www-browser] 2.28-1
ii luakit [www-browser] 1:2.3.3-1
ii lxterminal [x-terminal-emulator] 0.4.0-2
ii lynx [www-browser] 2.9.0dev.10-1+b1
ii netrik [www-browser] 1.16.1-2+b2
ii netsurf [www-browser] 3.6-3.2
ii netsurf-fb [www-browser] 3.10-1+b3
ii netsurf-gtk [www-browser] 3.10-1+b3
ii postfix [mail-transport-agent] 3.7.3-2+b1
ii python3-gi 3.42.2-3
ii qterminal [x-terminal-emulator] 1.2.0-2
ii qutebrowser [www-browser] 2.5.2-2
ii rxvt-unicode [x-terminal-emulator] 9.30-2+b3
ii stterm [x-terminal-emulator] 0.9-1
ii surf [www-browser] 2.1+git20221016-2
ii termit [x-terminal-emulator] 3.1-2
ii w3m [www-browser] 0.5.3+git20220429-1+b1
ii xfce4-terminal [x-terminal-emulator] 1.0.4-1
ii xterm [x-terminal-emulator] 377-1
ii zutty [x-terminal-emulator] 0.13.2.20221029.103432+dfsg1-1
-- debconf information:
apt-listchanges/no-network: false
* apt-listchanges/headers: true
* apt-listchanges/email-format: text
* apt-listchanges/which: news
* apt-listchanges/frontend: pager
* apt-listchanges/reverse: false
* apt-listchanges/save-seen: true
* apt-listchanges/email-address: root
* apt-listchanges/confirm: true
--- End Message ---
--- Begin Message ---
That message doesn't occur anywhere in the apt-listchanges source tree
and never has.
As far as I can tell it comes from `whatmaps`. Also as far as I can
tell, apt-listchanges has never depended on `whatmaps` directly, though
perhaps at some point in the past it depended on something that depended
on `whatmaps`.
Right now you can have a working apt-listchanges on your system without
even having `whatmaps` installed.
As such I'm not sure this was ever an apt-listchanges bug and in any
case I don't think it is anymore, so I'm closing it.
If you are able to reproduce it, please open a new ticket with
additional details and I suppose we will have to try to get to the
bottom of what apt-listchanges is invoking that's invoking whatmaps.
--- End Message ---
