Now that rpm-ostree and cosa support it, move to just using a
`manifest-lock.overrides.yaml` which uses `evr` instead of `evra` so
that we can avoid all the duplication.
The previous filenames are still supported in case we do have
arch-specific overrides (e.g. grub) in the future.
Previously we pinned clevis to v15 in order to work around
https://github.com/latchset/clevis/pull/295.
But overrides are not set up in the tagger for mechanical streams, so we
can't easily pin in `branched` and `rawhide`. Let's just unpin and
temporarily ship `seq` ourselves to work around this. Put that temporary
hack in `40ignition-ostree` since that's the closest module conceptually
to clevis.
systemd in f34 learned to read the default hostname from a
`DEFAULT_HOSTNAME` key in `/etc/os-release`.
Use that to set the hostname back to `localhost` on f34 so that once we
move over we can unpin the systemd build which had this same effect at
compilation time.
Ideally, this would be part of `fedora-release`, but I'm trying to aim
for a better fix where the compiled-in default hostname in Fedora is
back to `localhost` and only on the variants where we really want
`fedora` would we set `DEFAULT_HOSTNAME=fedora` in `fedora-release`.
So for now, let's just do this here.
Closes: #649
The dracut module from the latest Clevis v16 release has an undeclared
dependency on `seq`. There's a patch to fix that upstream:
https://github.com/latchset/clevis/pull/295
But for now, let's just pin to the previous release. This will unblock
lockfile bumps.
This one is complicated, we need to revert the systemd change
in f33 that makes it fallback to `fedora` rather than `localhost`
for the hostname and we also need to essentially render systemd-resolved
ineffective because it's internal fallbacks for reverse DNS make
it really hard to set the hostname via reverse DNS, which is
something we don't want to break and needs upstream work to
get more appropriate fixes in.
More context in https://github.com/coreos/fedora-coreos-tracker/issues/649#issuecomment-736104003
This is the culmination of a lot of work to make package layering
more reliable. This archive repo provides all packages that have
ever been in the updates repository, which means there should always
be a solution that will depsolve given the existing set of base layer
packages.
Pairing this along with https://github.com/coreos/rpm-ostree/pull/2125
means that we should finally see less of the split base layer vs update
repo problem and see less `Forbidden base package replacements` errors.
Fixes: https://github.com/coreos/fedora-coreos-tracker/issues/400