On Sun, 28 Dec 2025, Tim Woodall wrote:
On Sun, 28 Dec 2025, Ray and Sandie Clark for Biz wrote:
I think this amounts to what might be called bugs or mistakes in the
structuring of the archive.debian.org and deb.debian.org repositories for
bullseye, bookworm, and trixie, but I am thinking that I should start here
to get some feedback.
The detailed structure and what I see as wrong is below (Questions embedded
in the detail are marked with an *), but at a high level :
* Bullseye appears under both archive.debian.org and deb.debian.org, and
the deb version is missing bullseye-backports. I do not have the
capability to compare them, and I don't know which I should use or if I
should list both! Bullseye security information is only in deb, whereas
buster is only in archive (Which seems appropriate for an old release,
which bullseye is also).
This might be down to which architectures have lts.
Recently, things seem to be being moved to archive.debian.org more
aggressively than they used to be.
I have this currently:
bullseye_sources()
{
cat <<CATEOF
Types: deb
URIs: http://archive.debian.org/debian
Suites: bullseye
Components: main
Types: deb
URIs: http://deb.debian.org/debian-security
Suites: bullseye-security
Components: main
CATEOF
}
I've not checked the data, but packages.xz has the same aug 2024
timestamp for the amd64 arch in both archive and deb.debian.org.
