New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fedora 38 - Incorrect use of rpm-ostree vs dnf #402
Comments
Forgot to mention that the rest of the log looks normal. |
Could you try out #393 and see if this patch works? |
I just ran topgrade and saw it upgrade to version 10.3.3, which still has the issue. How do I apply the patch? I am not a developer. |
The latest released version has that patch included, you can try it now.
You can grab the pre-built binary here: https://github.com/topgrade-rs/topgrade/releases/tag/v11.0.2 |
It is working correctly for me now. Thanks.
…On Thu, May 4, 2023 at 6:37 AM SteveLauC ***@***.***> wrote:
I just ran topgrade and saw it upgrade to version 10.3.3, which still has
the issue. How do I apply the patch? I am not a developer.
The latest version 11.0.0 (released in crates.io) has that patch
included, you can try it now.
—
Reply to this email directly, view it on GitHub
<#402 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZCOXVA4XA3DUSKJV632MUTXEOWJRANCNFSM6AAAAAAWSD7PUM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Then we can close this issue:) |
My computer is running Fedora 38 Workstation beta (not Silverblue).
── 20:28:29 - System update ────────────────────────────────────────────────────
error: This system was not booted via libostree.
Currently, most rpm-ostree commands only work on ostree-based host systems.
System update failed:
0: Command failed:
/usr/bin/rpm-ostree upgrade
1:
/usr/bin/rpm-ostree
failed: exit status: 1Location:
src/steps/os/linux.rs:176
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
The text was updated successfully, but these errors were encountered: