I use dnf to manage updates on two machines. On one, the recent 200+
list of packages was successfully completed. On this machine, dnf
continually returns "Nothing to do" despite the mgaapplet showing that
updates are available.
The list of enabled repos is the same, and the contents of dnf.conf are
#dnf install dnf had no effect.
This is a recent development, because dnf ran last successfully on this machine on 21 March with 4 updates.
Anyone with an idea where else to look?
--
Grimble
Machine 'Haydn' running Plasma 5.27.10 on 6.6.18-desktop-1.mga9 kernel.
Mageia release 9 (Official) for x86_64

--- MBSE BBS v1.0.8.6 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Sun, 24 Mar 2024 13:36:54 -0400, Grimble <grimble@nomail.afraid.org> wrote:

I use dnf to manage updates on two machines. On one, the recent 200+
list of packages was successfully completed. On this machine, dnf
continually returns "Nothing to do" despite the mgaapplet showing that updates are available.
The list of enabled repos is the same, and the contents of dnf.conf are
#dnf install dnf had no effect.
This is a recent development, because dnf ran last successfully on this machine on 21 March with 4 updates.
Anyone with an idea where else to look?

What's the output of "dnf -v list --upgrades --refresh"?

Regards, Dave Hodgins

--- MBSE BBS v1.0.8.6 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 24/03/2024 19:19, David W. Hodgins wrote:

dnf -v list --upgrades --refresh

Interesting Dave. Both updates-x86_64-nonfree and updates-x86_64 had out-of-date metadata:

mageia-x86_64-nonfree: using metadata from Sat 19 Aug 2023 20:05:01 BST.
Mageia 9 - x86_64 - Nonfree - Updates
reviving: failed for 'updates-x86_64-nonfree', mismatched repomd.
repo: downloading from remote: updates-x86_64-nonfree
Mageia 9 - x86_64 - Nonfree - Updates
updates-x86_64-nonfree: using metadata from Thu 21 Mar 2024 04:44:16 GMT. Mageia 9 - x86_64
reviving: 'mageia-x86_64' can be revived - repomd matches.
mageia-x86_64: using metadata from Sat 19 Aug 2023 22:28:00 BST.
Mageia 9 - x86_64 - Updates
reviving: failed for 'updates-x86_64', mismatched repomd.
repo: downloading from remote: updates-x86_64
Mageia 9 - x86_64 - Updates
updates-x86_64: using metadata from Mon 18 Mar 2024 16:08:01 GMT.

However, dnf still claims no updates available.
--
Grimble
Machine 'Haydn' running Plasma 5.27.10 on 6.6.18-desktop-1.mga9 kernel.
Mageia release 9 (Official) for x86_64


--- MBSE BBS v1.0.8.6 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Mon, 25 Mar 2024 09:36:02 -0400, Grimble <grimble@nomail.afraid.org> wrote:

On 24/03/2024 19:19, David W. Hodgins wrote:

dnf -v list --upgrades --refresh

Interesting Dave. Both updates-x86_64-nonfree and updates-x86_64 had out-of-date metadata:

mageia-x86_64-nonfree: using metadata from Sat 19 Aug 2023 20:05:01 BST. Mageia 9 - x86_64 - Nonfree - Updates
reviving: failed for 'updates-x86_64-nonfree', mismatched repomd.
repo: downloading from remote: updates-x86_64-nonfree
Mageia 9 - x86_64 - Nonfree - Updates
updates-x86_64-nonfree: using metadata from Thu 21 Mar 2024 04:44:16 GMT. Mageia 9 - x86_64
reviving: 'mageia-x86_64' can be revived - repomd matches.
mageia-x86_64: using metadata from Sat 19 Aug 2023 22:28:00 BST.
Mageia 9 - x86_64 - Updates
reviving: failed for 'updates-x86_64', mismatched repomd.
repo: downloading from remote: updates-x86_64
Mageia 9 - x86_64 - Updates
updates-x86_64: using metadata from Mon 18 Mar 2024 16:08:01 GMT.

However, dnf still claims no updates available.

Including the "list" command just shows if there are updates available

To actually update the metadata run it again without list.

"dnf -v --upgrades --refresh".

It would be better to figure out why dnfdragora is not updating the list
as it should, but I haven't used it much and am not sure how to go about debugging it.

Regards, Dave Hodgins

--- MBSE BBS v1.0.8.6 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 2024-03-25 12:47, David W. Hodgins wrote:

On Mon, 25 Mar 2024 09:36:02 -0400, Grimble <grimble@nomail.afraid.org> wrote:

On 24/03/2024 19:19, David W. Hodgins wrote:

dnf -v list --upgrades --refresh

Interesting Dave. Both updates-x86_64-nonfree and updates-x86_64 had
out-of-date metadata:

mageia-x86_64-nonfree: using metadata from Sat 19 Aug 2023 20:05:01 BST.
Mageia 9 - x86_64 - Nonfree - Updates
reviving: failed for 'updates-x86_64-nonfree', mismatched repomd.
repo: downloading from remote: updates-x86_64-nonfree
Mageia 9 - x86_64 - Nonfree - Updates
updates-x86_64-nonfree: using metadata from Thu 21 Mar 2024 04:44:16 GMT.
Mageia 9 - x86_64
reviving: 'mageia-x86_64' can be revived - repomd matches.
mageia-x86_64: using metadata from Sat 19 Aug 2023 22:28:00 BST.
Mageia 9 - x86_64 - Updates
reviving: failed for 'updates-x86_64', mismatched repomd.
repo: downloading from remote: updates-x86_64
Mageia 9 - x86_64 - Updates
updates-x86_64: using metadata from Mon 18 Mar 2024 16:08:01 GMT.

However, dnf still claims no updates available.

Including the "list" command just shows if there are updates available

To actually update the metadata run it again without list.

"dnf -v --upgrades --refresh".

It would be better to figure out why dnfdragora is not updating the list
as it should, but I haven't used it much and am not sure how to go about debugging it.

Regards, Dave Hodgins

FWIW, the distrib-coffee Tier 1 mirror has been down for a few days, and
that means all the mirrors that use it as a source are also out-of-date.

If you are using one of those mirrors, you should switch to one from https://mirrors.mageia.org/status that shows as green.

TJ

--- MBSE BBS v1.0.8.6 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 25/03/2024 16:47, David W. Hodgins wrote:

On Mon, 25 Mar 2024 09:36:02 -0400, Grimble <grimble@nomail.afraid.org> wrote:

On 24/03/2024 19:19, David W. Hodgins wrote:

dnf -v list --upgrades --refresh

Interesting Dave. Both updates-x86_64-nonfree and updates-x86_64 had
out-of-date metadata:

mageia-x86_64-nonfree: using metadata from Sat 19 Aug 2023 20:05:01 BST.
Mageia 9 - x86_64 - Nonfree - Updates
reviving: failed for 'updates-x86_64-nonfree', mismatched repomd.
repo: downloading from remote: updates-x86_64-nonfree
Mageia 9 - x86_64 - Nonfree - Updates
updates-x86_64-nonfree: using metadata from Thu 21 Mar 2024 04:44:16 GMT.
Mageia 9 - x86_64
reviving: 'mageia-x86_64' can be revived - repomd matches.
mageia-x86_64: using metadata from Sat 19 Aug 2023 22:28:00 BST.
Mageia 9 - x86_64 - Updates
reviving: failed for 'updates-x86_64', mismatched repomd.
repo: downloading from remote: updates-x86_64
Mageia 9 - x86_64 - Updates
updates-x86_64: using metadata from Mon 18 Mar 2024 16:08:01 GMT.

However, dnf still claims no updates available.

Including the "list" command just shows if there are updates available

To actually update the metadata run it again without list.

"dnf -v --upgrades --refresh".

It would be better to figure out why dnfdragora is not updating the list
as it should, but I haven't used it much and am not sure how to go about debugging it.

Regards, Dave Hodgins

Thanks, Dave. I don't use dnfdragora - I run dnf from a script in
cron.daily. I first run dnf check-update to see how many updates are
waiting (I thought about doing a checkpoint if there many updates to
apply). There must be something amiss with this, because that is where I
exit if no updates are expected. It ran at 4:02 this morning with zero
result, but I've just run #dnf -v upgrade from the command line and it
all worked - 242 packages.
Further investigation needed.
--
Grimble
Machine 'Haydn' running Plasma 5.27.10 on 6.6.18-desktop-1.mga9 kernel.
Mageia release 9 (Official) for x86_64


--- MBSE BBS v1.0.8.6 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 25/03/2024 16:47, David W. Hodgins wrote:

On Mon, 25 Mar 2024 09:36:02 -0400, Grimble <grimble@nomail.afraid.org>
wrote:

On 24/03/2024 19:19, David W. Hodgins wrote:

dnf -v list --upgrades --refresh

Interesting Dave. Both updates-x86_64-nonfree and updates-x86_64 had
out-of-date metadata:

mageia-x86_64-nonfree: using metadata from Sat 19 Aug 2023 20:05:01
BST. Mageia 9 - x86_64 - Nonfree - Updates reviving: failed for
'updates-x86_64-nonfree', mismatched repomd.
repo: downloading from remote: updates-x86_64-nonfree Mageia 9 -
x86_64 - Nonfree - Updates updates-x86_64-nonfree: using metadata from
Thu 21 Mar 2024 04:44:16 GMT.
Mageia 9 - x86_64 reviving: 'mageia-x86_64' can be revived - repomd
matches. mageia-x86_64: using metadata from Sat 19 Aug 2023 22:28:00
BST.
Mageia 9 - x86_64 - Updates reviving: failed for 'updates-x86_64',
mismatched repomd.
repo: downloading from remote: updates-x86_64 Mageia 9 - x86_64 -
Updates updates-x86_64: using metadata from Mon 18 Mar 2024 16:08:01
GMT.

However, dnf still claims no updates available.

Including the "list" command just shows if there are updates available

To actually update the metadata run it again without list.

"dnf -v --upgrades --refresh".

It would be better to figure out why dnfdragora is not updating the
list as it should, but I haven't used it much and am not sure how to go
about debugging it.

Regards, Dave Hodgins

Thanks, Dave. I don't use dnfdragora - I run dnf from a script in
cron.daily. I first run dnf check-update to see how many updates are
waiting (I thought about doing a checkpoint if there many updates to
apply). There must be something amiss with this, because that is where I
exit if no updates are expected. It ran at 4:02 this morning with zero result, but I've just run #dnf -v upgrade from the command line and it
all worked - 242 packages.
Further investigation needed.

Timing differences between when metada was last updated, script run and
when you ran dnf upgrade.

Might help to update metadata when you run script.
E.G.: dnf --refresh check-update





--
Jim Whitby


<Culus-> libc6 is not essential :|
----------------------
Mageia release 9 (Official) for x86_64
6.6.18-server-1.mga9
----------------------

--- MBSE BBS v1.0.8.6 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 26/03/2024 14:54, jim whitby wrote:

On 25/03/2024 16:47, David W. Hodgins wrote:

On Mon, 25 Mar 2024 09:36:02 -0400, Grimble <grimble@nomail.afraid.org>
wrote:

On 24/03/2024 19:19, David W. Hodgins wrote:

dnf -v list --upgrades --refresh

Interesting Dave. Both updates-x86_64-nonfree and updates-x86_64 had
out-of-date metadata:

mageia-x86_64-nonfree: using metadata from Sat 19 Aug 2023 20:05:01
BST. Mageia 9 - x86_64 - Nonfree - Updates reviving: failed for
'updates-x86_64-nonfree', mismatched repomd.
repo: downloading from remote: updates-x86_64-nonfree Mageia 9 -
x86_64 - Nonfree - Updates updates-x86_64-nonfree: using metadata from >>>> Thu 21 Mar 2024 04:44:16 GMT.
Mageia 9 - x86_64 reviving: 'mageia-x86_64' can be revived - repomd
matches. mageia-x86_64: using metadata from Sat 19 Aug 2023 22:28:00
BST.
Mageia 9 - x86_64 - Updates reviving: failed for 'updates-x86_64',
mismatched repomd.
repo: downloading from remote: updates-x86_64 Mageia 9 - x86_64 -
Updates updates-x86_64: using metadata from Mon 18 Mar 2024 16:08:01
GMT.

However, dnf still claims no updates available.

Including the "list" command just shows if there are updates available

To actually update the metadata run it again without list.

"dnf -v --upgrades --refresh".

It would be better to figure out why dnfdragora is not updating the
list as it should, but I haven't used it much and am not sure how to go
about debugging it.

Regards, Dave Hodgins

Thanks, Dave. I don't use dnfdragora - I run dnf from a script in
cron.daily. I first run dnf check-update to see how many updates are
waiting (I thought about doing a checkpoint if there many updates to
apply). There must be something amiss with this, because that is where I
exit if no updates are expected. It ran at 4:02 this morning with zero
result, but I've just run #dnf -v upgrade from the command line and it
all worked - 242 packages.
Further investigation needed.

Timing differences between when metada was last updated, script run and
when you ran dnf upgrade.

Might help to update metadata when you run script.
E.G.: dnf --refresh check-update

Sorry Jim, I didn't show the complete command - I do --refresh
--
Grimble
Machine 'Haydn' running Plasma 5.27.10 on 6.6.18-desktop-1.mga9 kernel.
Mageia release 9 (Official) for x86_64


--- MBSE BBS v1.0.8.6 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

<snip>

Sorry Jim, I didn't show the complete command - I do --refresh

Is this occuring *all* the time? If not.

Still might be a timing proplem...
If the mirror was updated after the check, and before you ran manually... Presuming the metadata was updated when you ran manually.

Otherwise, I'm a lost babe in the woods.


--
Jim Whitby


This fortune intentionally says nothing.
----------------------
Mageia release 9 (Official) for x86_64
6.6.18-server-1.mga9
----------------------

--- MBSE BBS v1.0.8.6 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)