Hi everyone, I'm working on a fix and will be pushing it to mirrors ASAP. Background: There was an issue with a mariadb module being set as default by mistake, and that generated all sorts of problems while trying to get rid of it from the repos again. (There's a thread on centos-devel about that.) The fix was based on removing old modular metadata that were used as cache (including the module default). However, because we keep a few older RPM versions around on the mirrors, this left some modular RPMs without modular metadata present. DNF then went ahead and offered them for installation as non-modular packages, realising they are modular, and failing with the "No available modular metadata for modular package" error. So I'm removing the old modular packages now from our "to be released" area, getting all the latest ones from the latest compose which works fine, regenerating all the repodata etc., and will be syncing it to mirrors shortly if it all works out (my first local test just passed as I'm typing this). Thanks all for your patience, Adam On Tue, 5 Mar 2024 at 13:09, Alfredo Moralejo Alonso <amoralej at redhat.com> wrote: > Hi, > > Latest CentOS Stream compose is failing to install ruby. > > "dnf install ruby" tries to install modularized > 3.1.2-141.module_el9+156+2e0939d1 version and fails with errors: > > Error: No available modular metadata for modular package > > Workaround is to specify unmodular version: > > # sudo dnf install ruby-3.0.4 > > I've reported it in https://issues.redhat.com/browse/RHEL-28082 > > Note that if other packages require 3.0 (in RDO case, via automatic dep on > "libruby.so.3.0()(64bit)" i.e.) it will just work. > > Best regards, > > Alfredo > > _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > https://lists.centos.org/mailman/listinfo/centos-devel > -- Adam Samalik --------------------------- Principal Software Engineer Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20240305/2943489d/attachment.html>