Hi,
For about one month ago, I upgraded my F41 to F42 while still in beta,
I just wanted to ask if I need to disable the testing repo now. I haven’t update this system for the past 10 days or so if that is relevant.
Hi,
For about one month ago, I upgraded my F41 to F42 while still in beta,
I just wanted to ask if I need to disable the testing repo now. I haven’t update this system for the past 10 days or so if that is relevant.
I guess it is. Have a look into hostnamectl
if it states as prerelease first thing i would do is update the system and recheck hostnamectl
. The per-release part should have been gone now.
You can also verifier with sudo dnf repolist
if testing is deactivated after update your system first.
Operating System: Fedora Linux 42 (Workstation Edition)
$ dnf repolist
repo id repo name
copr:copr.fedorainfracloud.org:phracek:PyCharm Copr repo for PyCharm owned by phracek
fedora Fedora 42 - x86_64
fedora-cisco-openh264 Fedora 42 openh264 (From Cisco) - x86_64
updates Fedora 42 - x86_64 - Updates
Seems to be alright, doesn’t it?
There’s a update to the fedora-repos package that goes out just before release that disables updates-testing. It appears you have that update, so all should be fine.
Note that there is sometimes a very corner case where you have something installed from updates-testing that needs something else from updates-testing and you get a mismatch error trying to install it. In those cases you can just re-enable updates-testing or do a ‘distro-sync’ to sync up to only updates packages.
Thanks for the heads up @kevin ! I’ll keep an eye on the updates. Hopefully it’ll be fine. If I run into the issue you have mentioned, I’ll proceed as per your suggestion.