-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Debian stable is more or less an alias #237
Comments
BTW: I guess it would not matter so much if not the rootfs has different checksums. Only minor reasons for that: $ diff -q -r 91b542912d126a7516f2371a25a8b1f865f327cd8bd079f23d057d9945f7d02d 5e240deb53858e76136796ec3f24a521450bfc40dfa525e96380a5134ed09df9
Files 9../etc/apt/sources.list.d/debian.sources and
5../etc/apt/sources.list.d/debian.sources differ
Files 9../etc/shadow and
5../etc/shadow differ The later one looks like a reproducibility problem (date of last password change could be unified to fixed value): --- 5e240deb53858e76136796ec3f24a521450bfc40dfa525e96380a5134ed09df9/etc/shadow 2025-01-13 01:00:00.000000000 +0100
+++ 91b542912d126a7516f2371a25a8b1f865f327cd8bd079f23d057d9945f7d02d/etc/shadow 2025-02-03 01:00:00.000000000 +0100
@@ -1,18 +1,18 @@
-root:*:20101:0:99999:7:::
+root:*:20122:0:99999:7:::
... The first one is caused by the different "entry" alias name, but since all other files are the same, its doubtful this is wanted/helpful? (i dont really can imagine someone wants to have a stable tag which can switch to a new major distribution inside a container anyway): --- 5e240deb53858e76136796ec3f24a521450bfc40dfa525e96380a5134ed09df9/etc/apt/sources.list.d/debian.sources 2025-01-13 01:00:00.000000000 +0100
+++ 91b542912d126a7516f2371a25a8b1f865f327cd8bd079f23d057d9945f7d02d/etc/apt/sources.list.d/debian.sources 2025-02-03 01:00:00.000000000 +0100
@@ -1,13 +1,13 @@
Types: deb
-# http://snapshot.debian.org/archive/debian/20250113T000000Z
+# http://snapshot.debian.org/archive/debian/20250203T000000Z
URIs: http://deb.debian.org/debian
-Suites: stable stable-updates
+Suites: bookworm bookworm-updates
Components: main
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
Types: deb
-# http://snapshot.debian.org/archive/debian-security/20250113T000000Z
+# http://snapshot.debian.org/archive/debian-security/20250203T000000Z
URIs: http://deb.debian.org/debian-security
-Suites: stable-security
+Suites: bookworm-security
Components: main
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg I might have forgotten to pull=alwas the stable tag, but nothing much has changed (besides the shadow timestamp and the snapshot date)
BTW: unrelated but i noticed it while comparing the root images:
|
Comparing the InRelease files for :stable and :bookworm its pretty clear that they are the same file (at the moment). It would probably be a good idea to treat stable as a alias for bookworm, because:
a) one image less to build
b) less confusion why @sha256 of bookwork and stable is different
c) no problem with people comparing timestamps and wondering which is more recent
d) its obvious from the tag list where stable points to
Instead of treating it hardcoded, its probably best to just resolve the alias url and check the codename in the InRelease file.
The text was updated successfully, but these errors were encountered: