Background: https://github.com/projectatomic/rpm-ostree/issues/1081
Now that the first PR has landed in git master and will shortly be in the next release: https://github.com/projectatomic/rpm-ostree/pull/1103
I'd like to schedule a discussion about rpm-ostree jigdo (official emoji tag: ♲📦, i.e. recycle package).
Making use of this will require changes in the "ostree" (really rpm-ostree) phase in pungi, as well as anaconda, our kickstarts and also the special magic to embed the ostree data in the ISOs.
But a major part of the idea of this is to reduce releng burden, so hopefully we can accomplish the goal!
Notable topics:
- Do OIRPMs appear in the Everything repo? (I hope so but it's not required) - How hard would it be to change pungi for this given things become somewhat more circular? (i.e. it's createrepo_c, rpm-ostree compose jigdo, createrepo_c) - Would anything I'm not aware of break at having RPMs without corresponding .src.rpms or do we "fake out" SRPMs for this? - Anything else you want to discuss!
On Mon, Dec 4, 2017, at 03:22 PM, Colin Walters wrote:
- Do OIRPMs appear in the Everything repo? (I hope so but it's not required)
Actually I forgot to mention the sub-thread from https://github.com/projectatomic/rpm-ostree/issues/1081#issuecomment-3419807... and my reply: https://github.com/projectatomic/rpm-ostree/issues/1081#issuecomment-3420039...
Basically to really preserve the experience we need to keep older RPMs around in a "reliable" way - at least the last release, and my preference would be 2-3 or more. This might be something where we e.g. pass
"fedora-atomic-host-27.8"
as the "$releasever" variable to
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=...
and mirrormanager DTRT? Maybe it'd be more reliable though to pass a distinct variable though.
Also, from this comment: https://github.com/projectatomic/rpm-ostree/issues/1081#issuecomment-3485406...
Given how very prominent the repo IDs will be, I'd like to consider renaming `[fedora]` to `[fedora-major-release]` or something, and then `[updates]` to `[fedora-updates]`? Or possibly just `[fedora]`?
(Using [] around the name to clarify these are rpm-md repo IDs for things that appear in /etc/yum.repos.d)
If we don't do this we can probably hack around it with some metadata to tell rpm-ostree to present [updates] as [fedora-updates]` or so).
rel-eng@lists.fedoraproject.org
-
Colin Walters