Re: DNF not Installing all Updates?

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

 



On 27/6/21 22:23, Ed Greshko wrote:
On 27/06/2021 20:00, Patrick O'Callaghan wrote:
On Sun, 2021-06-27 at 18:31 +1000, Stephen Morris wrote:
Hi,
      I have just done a sudo dnf upgrade on F34 which I think
upgraded
1311 packages. After the update finished I rebooted F34 and then ran
discovery and it was still telling me there was 628 MB of F34
Platform
updates to put on, which I did put on. Why is dnf not installing all
done to alleviate this that is not done in an "out of the box"
install,
should be using Discovery instead?
I think plasma-discover uses PackageKit. As has been noted several
times here, mixing dnf and PK often leads to confusion. Better pick one
and stick with it.

Personally, I erased PK and don't use plasma-discover, and I don't see
these kinds of problem.

I probably misunderstood the OP.  I haven't (yet) banished packageKit from my system.

I have not had a situation where an update was performed and immediately followed by a need
for another update.  I do my updates with "dnf --refresh update".

The only thing I've seen is when packageKit is telling me there are updates but when dnf runs it says no updates are available.  I attribute that to packageKit using different mirrors than
dnf.
I hadn't realised Discover was using Packagekit. If it is using different mirrors to dnf and they indicate they have updates over and above what dnf has applied, does that mean dnf will catch up, or are they updates that dnf will never put on because it never sees them? While we are on the topic of updates with dnf, I have noticed that when dnf goes to a mirror to find an update, if it can't find the package it produces a 404 error, and keeps producing that error when it goes to the next mirror, etc. Is there any way to get dnf to only produce the 404 error if the required package can't be found in any mirror?

regards,
Steve

_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure



[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