Just get rid of the sid name
Just get rid of the sid name
Posted Aug 11, 2024 12:08 UTC (Sun) by bluca (subscriber, #118303)In reply to: Just get rid of the sid name by zblaxell
Parent article: Distinguishing Debian testing from unstable
> Yeah I read that. The example with the images is why I thought you were trying to solve either a dependency analysis problem or a content identification problem, and copying CODENAME to an image is insufficient for either of those use cases on not-stable Debian. That's why I proposed a solution that leverages existing metadata to try to solve those problems.
Your solution might solve some other problems, although I don't know what they may be - but it doesn't solve ours
> Why would we not simply push the other half of the apt configuration into mkosi?
Because it would break the tests, and be incredibly wrong. What we need is the codename, as we then match several conditional configuration on distro+release+arch triplet. I have no idea what the full apt configuration might contain, as it changes between testbeds and even between backends on the same testbeds (cloud autopkgtest vs debci and lxd vs lxc vs qemu vs podman vs ...) and if it is even going to be compatible with mkosi, so it must absolutely not be blindly copied over. This must work reliably across distributions, releases, branches, testbeds, infrastructures. Have you ever actually used mkosi? Have you ever actually had to work and maintain on this specific CI setup?
> There's another example (obs-build) that is similar, which is similar to the systemd test cases, in the sense that it builds a product with a short usable lifespan. This is more obvious in the systemd case because it creates a system image that's used only once, but in the obs-build case the package isn't labelled with sufficient dependency information so it's inevitably going to become unusable.
Not really? This is a throw-away VM guest with fixed locally downloaded content, that is used offline and never changed once created. It's entirely appropriate to identify it in such a way (if it worked reliably, of course). Have you ever actually used OBS?
> These are excellent concrete examples of when it is inappropriate to use os-release and VERSION_CODENAME.
I'm afraid that, while making grand statements like these in a comment in a thread is easy, actually working in the real world out there is much harder. What you are saying leads me to believe you never actually worked _with_ any of these systems, let alone _on_ them. There is nothing wrong with this of course, nobody can work on everything all the time. Please correct me if I am wrong.
> > You seem to be thinking that this is exclusively useful for dependencies purposes.
> Can you blame me?
I did not intend to assign blame, merely to try and explain the situation.
> > There are tons of use cases, some that we'll never know about.
> This is noise.
It's really not. The number of ways a universally present implementation of a generic specification is used is essentially endless. Searching on Github alone for the 'os-release' keyword yields 434 _thousands_ results. I am not going to read them all, sorry!
> > Fundamentally, os-release is about the OS vendor tree self-identifying in a distro-agnostic way that can be relied to just be there and be usable and accurate for what it provides
> This needs more definition to be useful.
Not really. I think the confusion stems from the notion that this is about some precise and exact and pin-pointed combination of content. It's obviously not: you can have a package that is bit-by-bit identical from oldoldstable all the way to unstable, literally the same identical one. This happens many times. bullseye is still bullseye, bookworm is still bookworm, etc. Also most of the packages are optional, and most are never installed in most installations. Two different bookworm images with different sets of packages are both still bookworm, etc. Bookworm at 12.0 had different content with respect to bookworm does now at 12.6, in dramatic ways in some cases (eg: kernel), but it's still bookworm. The identify of an image doesn't change because some of its content does. What you find under https://ftp.debian.org/debian/dists/bookworm/ is bookworm, even if it gets updates and changes at some point, and even if other archives have very similar contents. Same for everything else, including sid and trixie. Hope this helps clarify a bit?
> > without requiring special binaries or scripts or other hacks
> This needs definition too. What's a special script in the context of 640+ lines of highly Debian-specific code that is only run on Debian? Why is it better to remove a hack on top of os-release than to remove the dependency on os-release?
Sorry, what script?
> > There are many uses that one might derive from such a system, and not all of them have to be useful to everyone for it to exist.
> Forget everyone, and forget the other cases--at this point I'm trying to identify _anyone_ who might find a distinction between only the two options of testing and unstable useful for a reason that is not "misunderstanding the problem they're trying to solve" or "inventing a problem that os-release can be involved in solving."
As already mentioned, there are 430k hits for 'os-release' on Github alone. If you want to say that this is completely useless and serves no point, of course you can, but you'll need _a lot_ of evidence to back it up against that.
The LWN site is currently under high scraper load, so comment display has been suppressed for anonymous users. If you are a human, you may read the comments by clicking the button below:
Note: you can avoid this step in the future by logging into your LWN account.
