Open orbitalmartian8 opened 1 year ago
I had the same problem on a Fedora 37 beta instance. It seems like topgrade
defaults to upgrade using rpm-ostree
. Anyways, to remediate I did the following:
access the config:
topgrade --edit-config
In config under [linux] I changed the rpm_ostree
line to false
(You need to do this even though the line is #
out by default)
[linux]
# Arch Package Manager to use. Allowed values: autodetect, trizen, paru, yay, p>
#arch_package_manager = "pacman"
# Arguments to pass yay (or paru) when updating packages
#yay_arguments = "--nodevel"
#show_arch_news = true
#trizen_arguments = "--devel"
#pikaur_arguments = ""
#enable_tlmgr = true
#emerge_sync_flags = "-q"
#emerge_update_flags = "-uDNa --with-bdeps=y world"
#redhat_distro_sync = true
rpm_ostree = false
If you run topgrade
agian, but this time with the -v
flag you should see that dnf update
being used instead.
Hope this helps!
Br
STian
Got solved with this PR to a new fork: https://github.com/topgrade-rs/topgrade/pull/4#issue-1405138261
What did you expect to happen?
Update with DNF.
What actually happened?
Additional Details