stages/ostree.encapsulate: use new entrypoint on rpm-ostree >=2023.2
rpm-ostree 2023.2 dropped the `rpm-ostree container-encapsulate` entrypoint. Instead, we have to use `rpm-ostree compose container-encapsulate`. Adjust the code that it selects the correct entrypoint based on the rpm-ostree version. Since the new stage now requires python-yaml, add it to the buildroot and regenerate all manifests.
This commit is contained in:
parent
09fa9e9def
commit
6e254c95af
69 changed files with 158 additions and 5 deletions
|
|
@ -236,6 +236,7 @@
|
|||
"sha256:4c0a98cd79110fc394123f6b13e1967d9f5719d1045595818eda0ff9b31e8f29": {},
|
||||
"sha256:bdf429e9e79cbaaf49a37d53ba96a4e3197a3410080968ac2d0e2bd5560521e2": {},
|
||||
"sha256:66e1fea6d0e73a0631f2926cc835e589eb9bb01791c0dea5bbe89b7d48e1bf29": {},
|
||||
"sha256:6d809624847cf620e3060938474120a473572b0ffa3785013069c63c964b8b4b": {},
|
||||
"sha256:0ac49fd1615cbbcd5dc87bfb8220a3953e23a309cdd1e791c6bd30babb7805d3": {},
|
||||
"sha256:57c012e31a9903c3bdc70cc636f016bf998dbacdd0918fc53dd21a154f491391": {},
|
||||
"sha256:fa61f497c2f94b4bbe9022f2e7a1bb4138aa02db1b5f60706a0056cccf2eb7ac": {},
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue