Closed karuboniru closed 1 month ago
I believe this is due to https://github.com/coreos/rpm-ostree/pull/4697, it seems that the building process should populate files in /usr/lib/rpm-ostree
while this hasn't done in this case cusing updating to fail.
Will check if the same is true for latest testing compose, if so maybe I should downvote the update to stop the package from landing to stable
Downvoted, at least we won't need to worry about breaking stable and things gets less urgent :)
Wow, thanks for testing this out.
Should be fixed by https://github.com/coreos/rpm-ostree/pull/4727 - we should make a new release soon.
Should be fixed by coreos/rpm-ostree#4727 - we should make a new release soon.
Check 4727 is included in 2023.12-1, maybe also need https://github.com/coreos/rpm-ostree/pull/4746
Should be fixed with https://github.com/coreos/rpm-ostree/releases/tag/v2024.1 when it lands in Fedora.
Upgrade to rpm-ostree-2024.1-4.fc39.x86_64
, can remove package successfully.
[root@cosa-devsh ~]# rpm -q rpm-ostree
rpm-ostree-2023.11-1.fc39.x86_64
[root@cosa-devsh ~]# rpm-ostree override replace https://bodhi.fedoraproject.org/updates/FEDORA-2024-2a4f3dce00
[root@cosa-devsh ~]# reboot
[core@cosa-devsh ~]$ rpm -q rpm-ostree
rpm-ostree-2024.1-4.fc39.x86_64
[core@cosa-devsh ~]$ ls /usr/lib/rpm-ostree
ls: cannot access '/usr/lib/rpm-ostree': No such file or directory
[core@cosa-devsh ~]$ sudo rpm-ostree override remove chrony
Checking out tree 621d18a... done
Resolving dependencies... done
Applying 3 overrides
Processing packages... done
Running pre scripts... done
Running post scripts... done
Running posttrans scripts... done
Writing rpmdb... done
Writing OSTree commit... done
Staging deployment... done
Pruned images: 0 (layers: 51)
Freed: 2.2 MB (pkgcache branches: 0)
Removed:
chrony-4.5-1.fc39.x86_64
Use "rpm-ostree override reset" to undo overrides
Run "systemctl reboot" to start a reboot
This may be a different issue, but this one is now blocked by https://bugzilla.redhat.com/show_bug.cgi?id=2252000, at least until we complete the investigation.
Testing https://bodhi.fedoraproject.org/updates/FEDORA-2024-2a4f3dce00 resolves this issue would be nice.
This should have been fixed now.
Describe the bug
rpm-ostree update
will fail if executed from 39.20231224.0 of fedora/39/x86_64/testing/silverblue.To Reproduce Please describe the steps needed to reproduce the bug:
rpm-ostree update
没有那个文件或目录
should be translation ofno such file or directory
Expected behavior It should bring me newer release
Screenshots If applicable, add screenshots to help explain your problem.
OS version:
Additional context