Closed cgwalters closed 3 years ago
Let's close this one because ultimately it's a problem solved at the distro/releng level, not something that rpm-ostree can do a whole lot about.
And anyway, we're mostly talking about Fedora here which will have this fixed very soon. See: https://github.com/coreos/fedora-coreos-tracker/issues/400 https://src.fedoraproject.org/rpms/fedora-repos/pull-request/79 https://github.com/coreos/fedora-coreos-config/pull/673
(That last PR is Fedora CoreOS specific, but similar ones should follow for the other OSTree-based editions.)
Let's close this one because ultimately it's a problem solved at the distro/releng level, not something that rpm-ostree can do a whole lot about.
Well, https://github.com/coreos/rpm-ostree/pull/2125 did help a lot!
In wstree right now
krb5-libs
is a dependency of various things in the base OS.krb5-workstation
is an app that uses it - however, it's version locked.This introduces a problem with package layering, since if the compose server picks up a newer version from package mirror A, but the client only has an older version from mirror B, upgrades break. (Or if it's not installed, it can't be).
There are obviously a few solutions to this...likely krb5-workstation should be more flexible, and only introduce a hard requirement on the
-libs
package version if it needs it. Second, we may need to consider a way to retrieve rpm-md data from the same place as the ostree commit, or vice versa. Basically having unified metadata/data management.--
EDIT (2019-09-08): rojig is a much bigger hammer attempting to solve this problem.