Closed Ghoelian closed 3 months ago
Here's my /etc/os-release, if that's useful to you at all:
NAME="Fedora Linux" VERSION="40.20240426.0 (Sway Atomic)" ID=fedora VERSION_ID=40 VERSION_CODENAME="" PLATFORM_ID="platform:f40" PRETTY_NAME="Fedora Linux 40.20240426.0 (Sway Atomic)" ANSI_COLOR="0;38;2;60;110;180" LOGO=fedora-logo-icon CPE_NAME="cpe:/o:fedoraproject:fedora:40" DEFAULT_HOSTNAME="fedora" HOME_URL="https://fedoraproject.org/atomic-desktops/sway/" DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora-sericea/" SUPPORT_URL="https://ask.fedoraproject.org/" BUG_REPORT_URL="https://gitlab.com/fedora/sigs/sway/SIG/-/issues" REDHAT_BUGZILLA_PRODUCT="Fedora" REDHAT_BUGZILLA_PRODUCT_VERSION=40 REDHAT_SUPPORT_PRODUCT="Fedora" REDHAT_SUPPORT_PRODUCT_VERSION=40 SUPPORT_END=2025-05-13 VARIANT="Sway Atomic" VARIANT_ID=sway-atomic OSTREE_VERSION='40.20240426.0'
Erroneous Behavior
After rebasing to Fedora sway atomic 40, topgrade tries to update system packages using
yum upgrade
. This fails because yum is not installed on the host system.Expected Behavior
Topgrade should detect it's running on an atomic distro, and run
rpm-ostree update
instead.Steps to reproduce
Rebase Fedora Sericea 39 to Fedora Sway Atomic 40, and run topgrade.
Possible Cause (Optional)
I think this is because the Fedora atomic spins have been renamed, in my case from Fedora Sericea to Fedora Sway Atomic.
Problem persists without calling from topgrade
Did you run topgrade through
Remote Execution
Configuration file (Optional)
Additional Details
Operation System/Version Fedora Sway Atomic 40.20240426.0
Installation Crates.io
Topgrade version (
topgrade -V
) 14.0.1Verbose Output (
topgrade -v
)