The use of distribution-gpg-keys for these repo files is
ancient; the first occurrence is 342e8813 ("Switch to f29, add
fedora-release-coreos") which doesn't have a rationale for it.
However, in practice today FCOS is currently built only by Fedora-based
tools, like cosa and the bootc-base-imagectl in fedora-bootc. So we
could just use the `/etc/pki/rpm-gpg` paths there.
This allows us to avoid having to install `distribution-gpg-keys` before
doing a compose. Note that `fedora-rawhide.repo` was already using the
`/etc` path so we know this works.
In Fedora 39 modularity is going away [1]. Let's drop the repos for F39+
and also drop the test that we have. We do still want to test installing
crio works so let's add crio to the ext.config.extensions.package test.
We also drop the repos as input to the build here. They were never used
for actual RPM content anyway.
[1] https://fedoraproject.org/wiki/Changes/RetireModularity
This isn't supported by `dnf`. `libdnf` will parse it but it's not
actually hooked up to anything. Recent repo files no longer use this
key. So just nuke it.
See: https://bugzilla.redhat.com/show_bug.cgi?id=1653831
This is take two on #109. What's different this time is that we just
include *both* the primary and secondary `dl.fp.o` baseurls. The stack
knows how to handle this and just tries one before going to the next.
The baseurl doesn't apply equally across all basearchs, so let's go back
to using metalink for now. I think we could get what we want using
custom mirrorlists, though want to explore this space a bit more first.
This is prep for having `testing-devel` be the source of truth for all
the files other than the lockfile and manifest (see [1]). We just have
one `fedora.repo` file which contains all the repos we care about, but
only actually enable the appropriate ones for each stream independently.
In this case, once packages are tagged, `testing-devel` will just use
the `coreos-pool` repo.
[1] https://github.com/coreos/fedora-coreos-tracker/issues/204
Otherwise, we can hit different mirrors on each run. This is an issue in
our pipeline since it breaks our change detection. See:
https://github.com/coreos/fedora-coreos-pipeline/issues/85
There could be nicer ways to do this in the future. This will fix things
for now at least.
