Commit 7782349
committed
feat(just): use uupd for system upgrades
We have a bit of an unideal situation currently as we are rather poorly
re-implementing what uupd already handles in regards to
rpm-ostree/bootc.
What we want is to use bootc for upgrades when it is possible to use it.
We currently don't do this as we just check for the `LockLayering` value
in `rpm-ostreed.conf`. Users don't change this so this will always call
to `rpm-ostree`. This recipe used to be shared with bluefin-lts which
sets `LockLayering=True` because it doesn't support package layering.
This also matches what automatic background updates are doing in this
regard. Which might prevent bugs/confusion in the future.
Bootc upgrade is slightly faster than rpm-ostree and more importantly
does not mess with any RPMs or calls to any repos, which are all steps
that might fail. There have also been bugs in the past in `rpm-ostree`
that broke image updates [1]. Bootc is simpler and the likelihood seems to
be lower for `upgrade` to straight up be broken.
UUPD sadly doens't have "human output" as it wasn't really designed for
this usecase so we need to do a little trickery there.
1 coreos/rpm-ostree#55671 parent 28529d0 commit 7782349
1 file changed
Lines changed: 10 additions & 6 deletions
File tree
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
14 | 14 | | |
15 | 15 | | |
16 | 16 | | |
17 | | - | |
18 | | - | |
19 | | - | |
20 | | - | |
21 | | - | |
22 | | - | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
23 | 27 | | |
24 | 28 | | |
25 | 29 | | |
| |||
0 commit comments