On 27/6/21 22:43, Ed Greshko wrote:
On 27/06/2021 20:34, Stephen Morris wrote:
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?
Oh, dnf will "catch up" as more mirrors are synced. You'll never have a case where an update is available via PK but never becomes available when using dnf.
Thanks Ed, I thought that was the case but I was just checking.
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?
It gets the 404 error since it uses curl to download.
I see no way to avoid what you've seen. It happens only occasionally so I never thought about it.
I thought that might be the case. Because I was updating a large number of packages I was seeing this message around a dozen times on various packages. I am assuming that if dnf gets to the situation where it can't find the package in any mirror, that it will suspend that update and any associated updates but continue on with the rest of the updates that are available and check again with the next update to see if it can then find the "missing" package?
regards, Steve