Your message dated Sat, 24 Oct 2026 08:42:56 +0100
with message-id
<352f86f18879e1def62b91a84480b64fa9556c53.ca...@adam-barratt.org.uk>
and subject line Re: Bug#1151865: apt changelog returns 404 error
has caused the Debian Bug report #1151865,
regarding apt changelog returns 404 error
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 [email protected]
immediately.)
--
1151865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1151865
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: apt
Version: 3.0.3
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
When trying to view changelogs for some packages using the apt changelog
interface it returns a 404 error. An example:
apt changelog bind9-host
Err:1 https://metadata.ftp-master.debian.org bind9 1:9.20.30-1~deb13u1 Changelog
Changelog unavailable for bind9=1:9.20.30-1~deb13u1 (404 Not Found [IP:
151.101.138.132 443])
Error: Failed to fetch
https://metadata.ftp-master.debian.org/changelogs/main/b/bind9/bind9_9.20.30-1%7edeb13u1_changelog
Changelog unavailable for bind9=1:9.20.30-1~deb13u1 (404 Not Found [IP:
151.101.138.132 443])
After manually trying to look up the changelogs online it looks like the error
is due to a discrepancy in the url for the package changelogs on the
metadata.ftp-master.debian.org site.
For example, the bind9-host package above looks for a package changelog name
bind9_9.20.30-1~deb13u1_changelog, while the changelog on the
metadata.ftp-master.debian.org site is named bind9_9.20.30-1_changelog, which
has had the debian release version (~deb13u1) omitted from the file name for
some reason.
It should be noted that the changelog link for packages on
https://packages.debian.org/ also returns a 404 error due to this discrepancy
in changelog names.
Thank you for your attention
-- Package-specific info:
-- (no /etc/apt/preferences present) --
-- (no /etc/apt/preferences.d/* present) --
-- (no /etc/apt/sources.list present) --
-- /etc/apt/sources.list.d/debian.sources --
# Modernized from /etc/apt/sources.list
Types: deb deb-src
URIs: http://deb.debian.org/debian/
Suites: trixie
Components: main non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
# Modernized from /etc/apt/sources.list
Types: deb deb-src
URIs: http://security.debian.org/debian-security/
Suites: trixie-security
Components: main non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
# Modernized from /etc/apt/sources.list
Types: deb deb-src
URIs: http://deb.debian.org/debian/
Suites: trixie-updates
Components: main non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
-- System Information:
Debian Release: 13.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.113+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages apt depends on:
ii adduser 3.152
ii base-passwd 3.6.7
ii debian-archive-keyring 2025.1
ii libapt-pkg7.0 3.0.3
ii libc6 2.41-12+deb13u4
ii libgcc-s1 14.2.0-19
ii libseccomp2 2.6.0-2
ii libssl3t64 3.5.7-1~deb13u3
ii libstdc++6 14.2.0-19
ii libsystemd0 257.13-1~deb13u1
ii sqv 1.3.0-3+b2
Versions of packages apt recommends:
ii ca-certificates 20250419+deb13u1
Versions of packages apt suggests:
pn apt-doc <none>
pn aptitude | synaptic | wajig <none>
pn dpkg-dev <none>
ii gnupg 2.4.7-21+deb13u1
ii powermgmt-base 1.38
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 2026-10-23 at 20:35 -0400, ned wrote:
> When trying to view changelogs for some packages using the apt
> changelog interface it returns a 404 error. An example:
>
> apt changelog bind9-host
> Err:1 https://metadata.ftp-master.debian.org bind9 1:9.20.30-
> 1~deb13u1 Changelog
> Changelog unavailable for bind9=1:9.20.30-1~deb13u1 (404 Not Found
> [IP: 151.101.138.132 443])
> Error: Failed to fetch
> https://metadata.ftp-master.debian.org/changelogs/main/b/bind9/bind9_9.20.30-1%7edeb13u1_changelog
> Changelog unavailable for bind9=1:9.20.30-1~deb13u1 (404 Not Found
> [IP: 151.101.138.132 443])
>
> After manually trying to look up the changelogs online it looks like
> the error is due to a discrepancy in the url for the package
> changelogs on the metadata.ftp-master.debian.org site.
>
> For example, the bind9-host package above looks for a package
> changelog name bind9_9.20.30-1~deb13u1_changelog, while the changelog
> on the metadata.ftp-master.debian.org site is named bind9_9.20.30-
> 1_changelog, which has had the debian release version (~deb13u1)
> omitted from the file name for some reason.
The suffix isn't being omitted, those are different package versions
and the filenames - and their contents - are accordingly different.
This is not a bug in APT, nor anything APT can do anything about.
Rather it is due to the fact that uploads to the security archive do
not result in the publication of changelogs on metadata.ftp-master,
with that only occurring when the package reaches an (old)stable suite
in the main archive (at least, the relevant proposed-updates suite
beforehand).
That's tracked in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490848
Regards,
Adam
--- End Message ---
