dc24dd3105
The new API to find pending and rollback deployments do so relative to
the booted deployment. This caused an interesting behaviour: the first
time a user uses "rpm-ostree rollback", it would (as expected) move the
previous deployment first. but the second call to "rpm-ostree rollback"
would fail since there were now no more rollback deployments.
We fine tune the logic here to allow this, as well as the more general
case of putting the booted deployment back on top.
This fixes a subtle regression from
|
||
---|---|---|
.. | ||
fetch-journal.sh | ||
multitest.py | ||
overlay.sh | ||
sync.sh | ||
test-basic.sh | ||
test-initramfs.sh | ||
test-layering-basic.sh | ||
test-layering-gpg.sh | ||
test-layering-local.sh | ||
test-layering-non-root-caps.sh | ||
test-layering-relayer.sh | ||
test-layering-rpmdb.sh | ||
test-layering-scripts.sh | ||
test-layering-unified.sh | ||
test-livefs.sh | ||
test-override-local-replace.sh | ||
test-override-remove.sh | ||
test.sh |