On 27/06/2021 20:45, Ed Greshko wrote:
On 27/06/2021 20: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.
>
>>
>> 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.
>
Hit send before I completed my thought.
I think it "wise" to do as poc has done. Get rid of packageKit and
plasma-discover. Running 2 update utilities can
lead to confusion.
Again with the fast finger.
I always install dnfdragora-updater and use that for notifications of when package updates
are available. But, I use dnf
from the command line to do the actual update as I have an alias to do the update via dnf
and that is
easier than clicking on things and I like to see what is going on.
--
Remind me to ignore comments which aren't germane to the thread.