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).
* While buster debian-security patches are in dist/buster/update
subdirectory, bullseye patches are in dist/bullseye-security directly
while ALSO having an updates subdirectory with apparently the same
content that is in its parent. The updates folder behaves like a link
to its parent, recursively showing all the same content and a new
updates folder at the new (lower) level.
* If I point to this bullseye-security folder will apt do something
dysfunctional due to the recursive folder?
* Bookworm and Trixie have the same structure as bullseye, including the
recursive folder.
Ultimately I want to develop sources.list and mirror.list files that
will work correctly so that I can efficiently install repetitively for
tests.
Thank you for your insights and advise!
--Ray
Buster organization (As expected, no issues)
archive.debian.org
debian
dists
buster
buster-updates
buster-proposed-updates
buster-backports
Each of the above categories having some of all of:
main
contrib
non-free
non-free-firmware
debian-security
dists
buster
updates
main
contrib
non-free
non-free-firmware
Each of the above categories having some of all of:
main
contrib
non-free
non-free-firmware
Bullseye organization (Questions embedded below with *)
archive.debian.org
debian
dists
Bullseye
Bullseye-updates
Bullseye-proposed-updates
Bullseye-backports
Each of the above categories having some of all of:
main
contrib
non-free
non-free-firmware
deb.debian.org
debian
dists
Bullseye
Bullseye-updates
Bullseye-proposed-updates
Each of the above categories having some of all of:
main
contrib
non-free
non-free-firmware
* Bullseye appears under both archive.debian.org and
deb.debian.org.
Not being the current release, I expected it all to
be in archive.
* If this is a duplicate of what is in archive, why is
Bullseye-backports missing?
* If this is not a duplicate, what is it?
* Which is correct? Which should I use? archive, deb,
or list both?
archive.debian.org
debian-security
dists
There is no subdirectory for Bullseye, OK.
deb.debian.org
debian-security (This is a link to
security.debian.org/debian-security)
dists
Bullseye-security
contrib
main
non-free
non-free-firmware
updates
* "updates" is a subdirectory containing everything
in its parent directory, including an updates
folder that appears to be recursive, like a link
to its containing folder (parent) would behave.
* Comparing this to the Buster structure, the updates
folder would exist and have the
contrib/main/non-free/
non-free-firmware and other (InRelease, Release,
Release.gpg) content in it. It would not contain
another "updates" folder (or link).
Bookworm-security and Trixie-security follow the same structure as Bullseye,
with the recursive "update" folder. The same issues with the location
of the
content vs. an update folder, and the recursive nature of the update folder
exist with bookworm and trixie also.
Bookworm and Trixie do not appear under archive.debian.org/debian/dists and
so do not / cannot have a redundant copy of the non-security categories
in those places.
