Miroslav Suchý venit, vidit, dixit 2025-10-03 16:22:40: > Do you want to make Fedora 43 better? Please spend 1 minute of your time and > try to run: > > dnf --releasever=43 --enablerepo=updates-testing --assumeno --best distro-sync > > This command does not replace `dnf system-upgrade`, but it will reveal > potential problems. > > You may also run `dnf upgrade` before running this command. > > > The `--assumeno` will just test the transaction, but does not make the actual > upgrade. > >
The `--enablerepo=updates-testing` will test against builds from `updates-testing` which is currently frozen (not being pushed to stable). Is this really where `dnf system-upgrade` will be pulling from? I don't think so. We're in a somewhat sore state right now where some updates in `updates-testing` are needed (python3-matplotlib-data-fonts in my case) whereas other updates from updates-testing are blocking at least rpmfusion (I know, 3rd party, but ...) because rpmfusion cannot build against `updates-testing`. I wrote on discourse: If we want people to test drive beta in real world scenarios during this phase we need something like `updates-testing-stable` where those updates from `updates-testing` are pushed to which would be pushed to stable if it weren't for the freeze. Otherwise, things are either completely broken for many users (and not fixable until release day stable pushes + wait time in testing), or if not then early adopters have to decide between missing out on important updates (without `updates-testing`) or pulling in testing packages early. Cheers Michael -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
