Can I upgrade already to Fedora42 following these instructions?

[neotux (Neo)]

Upgrading Fedora Linux Using DNF System Plugin

I have done this once upgrading from 40 to 41. I just wanted to make sure if I can already go ahead and upgrade to F42 Beta? Anything to have in mind? Preparation, etc.?
My personal data is all on different subvolumes so there is not much to backup from my home directory.

[augenauf (Flo)]

You can use these instructions to upgrade.

Be aware of the bugs reported against F42 release candidates: Fedora 42 Final Blocker Bugs

Always make sure you have a working backup. A separate volume/ dataset is not a backup.

[mjg (Michael J Gruber)]

In addition, be aware of the enabled repos: currently “-testing” repos are enabled because that’s where packages were sitting to be pushed to stable. Most of them will actually be, and at some point an update will disable “-testing” repos before the release. You may have some packages from “-testing” which never make it to release, or have to wait for updates which come to F41 earlier than to F42 (after “-testing” is disabled", before release).
Usually, none of this is a problem. It’s part of “beta”.

[wkmaurom (Mauro DeAngelis)]

Hi. I have Fedora in bare metal and vm virtualbox. About 1 month ago I cloned a Fedora 41 mate vm and attempted to upgrade to vers. 42. I had only one issue with the Proton VPN package.
Once that was resolved I found the upgrade very smooth.

[neotux (Neo)]

@augenauf

You can use these instructions to upgrade.

Be aware of the bugs reported against F42 beta: Fedora 42 Final Blocker Bugs

Always make sure you have a working backup. A separate volume/ dataset is not a backup.

Thanks @augenauf for the info!
I’ve got my data or most of it backed up on external drives as well. I’ll make sure to backup properly before attempting the upgrade. I guess I’ll be waiting until the weekend to have a bit more time and not rush through things.

[neotux (Neo)]

@mjg

In addition, be aware of the enabled repos: currently “-testing” repos are enabled because that’s where packages were sitting to be pushed to stable. Most of them will actually be, and at some point an update will disable “-testing” repos before the release.

That’s good to know. So I don’t have to disable the testing repo myself. It is handled by an update before the final release of 42.

@mjg

You may have some packages from “-testing” which never make it to release, or have to wait for updates which come to F41 earlier than to F42 (after “-testing” is disabled", before release).
Usually, none of this is a problem. It’s part of “beta”.

Do I need to do some “sanity check” after the stable release of 42 for not having any leftover packages of the sort?

[mjg (Michael J Gruber)]

Usually there’s no need for a sanity check - sooner or later, regular updates will update everything you have, be it from testing or regular updates.

If you really want to you can do a dnf distro-sync. Do it well after release day when all “zero day updates” had a chance to land.

[neotux (Neo)]

Good to know!

@mjg

If you really want to you can do a dnf distro-sync. Do it well after release day when all “zero day updates” had a chance to land.

I’ll keep that in mind. Thanks a lot for your input @mjg!