MariaDB 11.8 modular packages leaking into updates despite all streams disabled

Hello,

I’m seeing what looks like the same compose error that was reported for nginx packages here: Trying to update Rocky Linux 9.8 - gets "No available modular metadata for modular package"

But this time it’s affecting MariaDB.

Setup: Rocky Linux 9.8, MariaDB 10.5 installed from base AppStream (non-modular, no stream ever enabled). Both module streams are showing as disabled :

mariadb   10.11 [x]   client, galera, server [d]
mariadb   11.8  [x]   client, galera, server

When I am running dnf update, proposes upgrading all MariaDB packages to 3:11.8.8-1.module+el9.8.0+40229+87be66a2, which is a major version jump from 10.5 to 11.8.

I aborted the transaction. The modular NVR string module+el9.8.0+40229+87be66a2 suggests this is a modular package leaking into standard AppStream updates without proper metadata, the same pattern as the nginx issue (I think).

Is anyone else seeing this? Is this a known compose issue?

Thank you very much,

Ivan

Yep, I’d say it’s similar to that and would need someone from the Rocky team to fix it. I also see it at my end.

@jdieter can you check on this and get it fixed?

Update: The issue seems to have been fixed on the repository side.

After running dnf clean all && dnf update, MariaDB 11.8 packages no longer appear as available upgrades. Everything looks correct now.

Thanks!

Ivan

Yep, Skip fixed it not long ago.