Closed travier closed 1 year ago
We've had rpm-ostree bugs and changes that prevented that from working. The update from bdb to sqlite for example required latest rpm-ostree to be able to update to the next version. In general, we don't test it at all and we don't update Fedora N-1 versions of rpm-ostree that much.
The update from bdb to sqlite for example required latest rpm-ostree to be able to update to the next version. In general, we don't test it at all and we don't update Fedora N-1 versions of rpm-ostree that much.
Ah, right...that is a good example. Thanks for the reminder/context!
What's the reasoning behind this change/warning?
It should be technically possible to rebase from N to N+2, but I could understand why it might not be a good idea in practice. Are we just trying to avoid extra bugs/issues filed on the tracker?