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
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@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@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
It's now being pushed to the mirror network. It may take a few hours for it to propagate to all the existing mirrors.
On Tue, 5 Mar 2024 at 16:14, Adam Samalik asamalik@redhat.com wrote:
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@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@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
--
Adam Samalik
Principal Software Engineer Red Hat
Thanks for your quick and detailed reply!
Alfredo
On Tue, Mar 5, 2024 at 4:27 PM Adam Samalik asamalik@redhat.com wrote:
It's now being pushed to the mirror network. It may take a few hours for it to propagate to all the existing mirrors.
On Tue, 5 Mar 2024 at 16:14, Adam Samalik asamalik@redhat.com wrote:
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@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@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
--
Adam Samalik
Principal Software Engineer Red Hat
--
Adam Samalik
Principal Software Engineer Red Hat _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Hi
On 05.03.24 16:26, Adam Samalik wrote:
It's now being pushed to the mirror network. It may take a few hours for it to propagate to all the existing mirrors.
thank you for fixing quickly. However it seems that the repomd.xml.asc file got forgotten:
https://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/repodata/repomd.x...
See older issues like:
https://bugzilla.redhat.com/show_bug.cgi?id=2233486 https://pagure.io/centos-infra/issue/550 https://pagure.io/centos-infra/issue/510
~pete
On Tue, 5 Mar 2024 at 21:30, Peter Meier peter.meier@immerda.ch wrote:
Hi
On 05.03.24 16:26, Adam Samalik wrote:
It's now being pushed to the mirror network. It may take a few hours for it to propagate to all the existing mirrors.
thank you for fixing quickly. However it seems that the repomd.xml.asc file got forgotten:
https://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/repodata/repomd.x...
Just pushed that out. Apologies, this is normally automated, I forgot about this step yesterday.
See older issues like:
https://bugzilla.redhat.com/show_bug.cgi?id=2233486 https://pagure.io/centos-infra/issue/550 https://pagure.io/centos-infra/issue/510
~pete
-
Adam Samalik -
Alfredo Moralejo Alonso -
Peter Meier