Re: DNF Needs Restarting Repository Update

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

 



On Thu, Nov 7, 2024 at 4:57 PM Stephen Morris <steve.morris.au@xxxxxxxxx> wrote:
>
> On 7/11/24 19:30, Barry wrote:
>
> On 6 Nov 2024, at 22:11, Stephen Morris <steve.morris.au@xxxxxxxxx> wrote:
>
>     I ran a sudo dnf update which updated and loaded the two F41 Updates repositories and then put on the updates. Immediately after the update finished I ran a dnf needs-restarting which said there was no reboot required, but before it said that it updated and loaded all the existing repositories including the F41 Updates repository, why was that updated again, surely that repository was flagged as up to date by the prior dnf update?
>
> There are two things going on.
> 1. The update repo is being continuously updated.
> 2. The time when you download the repo meta data.
>
> I always use `dnf update --refresh` to ensure that the meta data is up to date.
> But if you run the command again new packages may have been released.
>
> Having said this though a subsequent dnf needs-restarting -s didn't update any of the repositories
>
> It is not it’s job to update repositories. It’s job is tell you if services are using out of date code.
>
> but did list a whole host of services that needed restarting, which included sddm and akmods, which I didn't understand because as far as I could see there was nothing updated by dnf that was related to sddm nor was there anything related to akmods or nvidia drivers.
>
> The services maybe using a library that is common, for example glibc.
>
> Thanks Barry, that might explain it. I did notice with one of the packages installed there was a glibc scriptlet run, which interestingly didn't display the deprecated spawning warning.

The noisy glibc trigger-post-uninstall scriptlet was fixed recently;
see <https://bugzilla.redhat.com/show_bug.cgi?id=2291869>.

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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux