Re: fc40 beta kernel update to 6.8.5-301 produces errors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 2024-04-14 at 23:32 +0000, J C wrote:
> Hi all, used Fedora a while, but my first thing to report so apologies if I don't get process right here.  Trying to give the feedback to help make a better Fedora for all of us...
> 
> Updated the subject fedora workstation today and got some errors.  Copying the terminal contents here for reference.  
> 
> Seems some missing file and library errors in addition to some things for gnome-remote-desktop and systemctrl.
> 
> `~$ sudo dnf check-update
> ...
> Last metadata expiration check: 0:06:30 ago on Sun 14 Apr 2024 04:52:10 PM MDT.
> 
> kernel.x86_64                                                           6.8.5-301.fc40                                              fedora
> kernel-core.x86_64                                                      6.8.5-301.fc40                                              fedora
> kernel-modules.x86_64                                                   6.8.5-301.fc40                                              fedora
> kernel-modules-core.x86_64                                              6.8.5-301.fc40                                              fedora
> kernel-modules-extra.x86_64                                             6.8.5-301.fc40                                              fedora
> ~$ sudo dnf distro-sync -y

So, the problem likely isn't anything to do with the kernel, it's
because you did a distro-sync, after upgrading from the fedora-repos
that has updates-testing enabled (which is how we want things through
most of the pre-release cycle) to the fedora-repos that has updates-
testing disabled (which is how we want things for release and after).
This means you wind up with a lot of downgrades, because you have
packages from updates-testing installed, but now it's disabled. It's an
unfortunate recurring issue, but I can't see an obvious way to resolve
it.

Downgrades aren't generally as tested or reliable as upgrades, so yeah,
this can cause problems. The usual ways to avoid the problem are: re-
enable updates-testing after the fedora-repos update that disables it
(if you're fine with continuing to help test updates), or wait for the
final release freeze to lift shortly before release (whereupon most of
the updates that are currently stuck behind the freeze will go stable
and you mostly won't get any downgrades when doing distro-sync any
more). And, of course, you can just use `dnf update` or `dnf upgrade`
instead of `distro-sync` while we're in this state.

Sorry for the trouble!
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@xxxxxxxxxxxxx
https://www.happyassassin.net



--
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/test@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux