On 2021-06-27 7:59 p.m., Stephen Morris wrote:
On 28/6/21 10:12, Samuel Sieb wrote:
On 2021-06-27 4:12 p.m., Stephen Morris wrote:
On 27/6/21 22:43, Ed Greshko wrote:
On 27/06/2021 20:34, Stephen Morris wrote:
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?
If dnf can't find a package on any mirror, it will immediately abort the entire transaction. Otherwise, it would have go through the whole dependency resolution process again.
So does that then mean that we have to keep issuing the dnf upgrade statement until the issue is resolved, which may or may not be a quick fix depending on what the issue is?
A 404 means that a sync is ongoing and not completed yet. It's extremely unlikely that a file will be missing on all mirrors unless you're very unlucky. :-) In any case, you shouldn't have to wait very long.