Closed noahdotpy closed 2 weeks ago
Couldn't you use the existing 40
and 41
tags in your build and then update those accordingly?
How could we differentiate between stable and latest if we only use fedora version tags?
I am confused as what you're trying to do, you mentioned that you want to use a specific fedora version until "I feel I am ready to update". When you feel you are ready to update you would increment the version. Am I misunderstanding?
I am trying to add the following tags:
Right now it is impossible to specify which fedora version to use and which channel to use (stable/latest). It is impossible to specify which channel you want to use when all you have is either the fedora version tags (40, 41) or channel tags (stable, latest, gts) since latest and stable are on the same fedora version.
I am proposing to add these tags so that we can differentiate between the channels on the same fedora version but still allow the end user of the image to specifically stay on the version they want without automatically updating.
When you feel you are ready to update you would increment the version. Am I misunderstanding?
Yes, I would increment the version in the tag (ex: 39 -> 40)
Basically what I would want is a tag that differentiates between the channels and specifies which version to use:
Stable explicitly isn't tied to a fedora version. It is matching the rolling model of CoreOS stable channel.
If you want to stay on a lower version use GTS or use an explicit Fedora version like 40.
Describe the bug
Currently, when wanting to specify a specific fedora version it is impossible to specify also which update channel that you want. This is because stable and latest will usually use the same version and gts is currently the same version as stable is.
What did you expect to happen?
I expect these tags to exist:
with the following structure being used:
Output of
rpm-ostree status
No response
Output of
groups
No response
Extra information or context
No response