Hi guys
Why are *release* packages are still absent in 9? We (admins/users) read docs - take recently mentioned here Hyperscale SIG - do dns this *release* do dnf that *release* - dnf install centos-hyperscale-release - but, those are nowhere to be found or.. have I gone blind? If this all is delayed deliberately - may I ask why?
many thanks, L.
On Tue, Apr 5, 2022 at 8:39 AM lejeczek via CentOS-devel centos-devel@centos.org wrote:
Hi guys
Why are *release* packages are still absent in 9? We (admins/users) read docs - take recently mentioned here Hyperscale SIG - do dns this *release* do dnf that *release*
- dnf install centos-hyperscale-release - but, those are
nowhere to be found or.. have I gone blind? If this all is delayed deliberately - may I ask why?
They're not delayed. They show up for me in the CentOS Extras repo that is enabled by default on my CentOS Stream 9 systems.
[root@57b98618010c /]# dnf repository-packages extras-common list Last metadata expiration check: 0:00:12 ago on Tue Apr 5 12:41:53 2022. Available Packages centos-release-ceph-pacific.noarch 1.0-2.el9s extras-common centos-release-ceph-quincy.noarch 1.0-2.el9s extras-common centos-release-gluster10.noarch 1.0-2.el9s extras-common centos-release-gluster9.noarch 1.0-2.el9s extras-common centos-release-hyperscale.noarch 9-4.el9s extras-common centos-release-hyperscale-experimental.noarch 9-4.el9s extras-common centos-release-hyperscale-spin.noarch 9-4.el9s extras-common centos-release-kmods.noarch 9-1.el9s extras-common centos-release-nfs-ganesha4.noarch 1.0-2.el9s extras-common centos-release-nfv-common.noarch 1-4.el9s extras-common centos-release-nfv-openvswitch.noarch 1-4.el9s extras-common centos-release-openstackclient-xena.noarch 1-1.el9s extras-common centos-release-opstools.noarch 1-12.el9s extras-common centos-release-ovirt45.noarch 9.0-1.el9s extras-common centos-release-samba414.noarch 1.0-1.el9s extras-common centos-release-samba415.noarch 1.0-1.el9s extras-common centos-release-samba416.noarch 1.0-1.el9s extras-common centos-release-storage-common.noarch 2-4.el9s extras-common centos-release-virt-common.noarch 1-4.el9s extras-common epel-next-release.noarch 9-2.el9 extras-common epel-release.noarch 9-2.el9 extras-common
On 05/04/2022 13:42, Neal Gompa wrote:
On Tue, Apr 5, 2022 at 8:39 AM lejeczek via CentOS-devel centos-devel@centos.org wrote:
Hi guys
Why are *release* packages are still absent in 9? We (admins/users) read docs - take recently mentioned here Hyperscale SIG - do dns this *release* do dnf that *release*
- dnf install centos-hyperscale-release - but, those are
nowhere to be found or.. have I gone blind? If this all is delayed deliberately - may I ask why?
They're not delayed. They show up for me in the CentOS Extras repo that is enabled by default on my CentOS Stream 9 systems.
[root@57b98618010c /]# dnf repository-packages extras-common list Last metadata expiration check: 0:00:12 ago on Tue Apr 5 12:41:53 2022. Available Packages centos-release-ceph-pacific.noarch 1.0-2.el9s extras-common centos-release-ceph-quincy.noarch 1.0-2.el9s extras-common centos-release-gluster10.noarch 1.0-2.el9s extras-common centos-release-gluster9.noarch 1.0-2.el9s extras-common centos-release-hyperscale.noarch 9-4.el9s extras-common centos-release-hyperscale-experimental.noarch 9-4.el9s extras-common centos-release-hyperscale-spin.noarch 9-4.el9s extras-common centos-release-kmods.noarch 9-1.el9s extras-common centos-release-nfs-ganesha4.noarch 1.0-2.el9s extras-common centos-release-nfv-common.noarch 1-4.el9s extras-common centos-release-nfv-openvswitch.noarch 1-4.el9s extras-common centos-release-openstackclient-xena.noarch 1-1.el9s extras-common centos-release-opstools.noarch 1-12.el9s extras-common centos-release-ovirt45.noarch 9.0-1.el9s extras-common centos-release-samba414.noarch 1.0-1.el9s extras-common centos-release-samba415.noarch 1.0-1.el9s extras-common centos-release-samba416.noarch 1.0-1.el9s extras-common centos-release-storage-common.noarch 2-4.el9s extras-common centos-release-virt-common.noarch 1-4.el9s extras-common epel-next-release.noarch 9-2.el9 extras-common epel-release.noarch 9-2.el9 extras-common
I do not think it was in 'extras' in previous centOSes - was it? Is it really necessary to keep those not in default repo(s) - in repos which first have to enabled? But first: -> $ dnf repository-packages extras-common list Error: Unknown repo: 'extras-common' -> $ dnf search extras-common Last metadata expiration check: 0:31:17 ago on Tue 05 Apr 2022 13:32:00 BST. No matches found. -> $ dnf search release --enablerepo extras Extras 98 kB/s | 8.1 kB 00:00 Errors during downloading metadata for repository 'extras': - Status code: 404 for http://mirror.stream.centos.org/SIGs/9-stream/extras/repodata/repomd.xml (IP: 18.195.214.106) Error: Failed to download metadata for repo 'extras': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried Ignoring repositories: extras Last metadata expiration check: 0:31:58 ago on Tue 05 Apr 2022 12:37:08 BST. ================================ Name & Summary Matched: release ================================ centos-stream-release.noarch : CentOS Stream release files ... ... plus a few more but nothing like you showed above also: -> $ dnf repolist all | grep extras
I'm puzzled a bit. thanks, L
On Tue, Apr 5, 2022 at 6:07 AM lejeczek via CentOS-devel < centos-devel@centos.org> wrote:
On 05/04/2022 13:42, Neal Gompa wrote:
On Tue, Apr 5, 2022 at 8:39 AM lejeczek via CentOS-devel centos-devel@centos.org wrote:
Hi guys
Why are *release* packages are still absent in 9? We (admins/users) read docs - take recently mentioned here Hyperscale SIG - do dns this *release* do dnf that *release*
- dnf install centos-hyperscale-release - but, those are
nowhere to be found or.. have I gone blind? If this all is delayed deliberately - may I ask why?
They're not delayed. They show up for me in the CentOS Extras repo that is enabled by default on my CentOS Stream 9 systems.
[root@57b98618010c /]# dnf repository-packages extras-common list Last metadata expiration check: 0:00:12 ago on Tue Apr 5 12:41:53 2022. Available Packages centos-release-ceph-pacific.noarch 1.0-2.el9s
extras-common
centos-release-ceph-quincy.noarch 1.0-2.el9s
extras-common
centos-release-gluster10.noarch 1.0-2.el9s
extras-common
centos-release-gluster9.noarch 1.0-2.el9s
extras-common
centos-release-hyperscale.noarch 9-4.el9s
extras-common
centos-release-hyperscale-experimental.noarch 9-4.el9s
extras-common
centos-release-hyperscale-spin.noarch 9-4.el9s
extras-common
centos-release-kmods.noarch 9-1.el9s
extras-common
centos-release-nfs-ganesha4.noarch 1.0-2.el9s
extras-common
centos-release-nfv-common.noarch 1-4.el9s
extras-common
centos-release-nfv-openvswitch.noarch 1-4.el9s
extras-common
centos-release-openstackclient-xena.noarch 1-1.el9s
extras-common
centos-release-opstools.noarch 1-12.el9s
extras-common
centos-release-ovirt45.noarch 9.0-1.el9s
extras-common
centos-release-samba414.noarch 1.0-1.el9s
extras-common
centos-release-samba415.noarch 1.0-1.el9s
extras-common
centos-release-samba416.noarch 1.0-1.el9s
extras-common
centos-release-storage-common.noarch 2-4.el9s
extras-common
centos-release-virt-common.noarch 1-4.el9s
extras-common
epel-next-release.noarch 9-2.el9
extras-common
epel-release.noarch 9-2.el9
extras-common
I do not think it was in 'extras' in previous centOSes - was it? Is it really necessary to keep those not in default repo(s)
- in repos which first have to enabled?
But first: -> $ dnf repository-packages extras-common list Error: Unknown repo: 'extras-common' -> $ dnf search extras-common Last metadata expiration check: 0:31:17 ago on Tue 05 Apr 2022 13:32:00 BST. No matches found. -> $ dnf search release --enablerepo extras Extras 98 kB/s | 8.1 kB 00:00 Errors during downloading metadata for repository 'extras':
- Status code: 404 for
http://mirror.stream.centos.org/SIGs/9-stream/extras/repodata/repomd.xml (IP: 18.195.214.106) Error: Failed to download metadata for repo 'extras': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried Ignoring repositories: extras Last metadata expiration check: 0:31:58 ago on Tue 05 Apr 2022 12:37:08 BST. ================================ Name & Summary Matched: release ================================ centos-stream-release.noarch : CentOS Stream release files ... ... plus a few more but nothing like you showed above also: -> $ dnf repolist all | grep extras
I'm puzzled a bit. thanks, L
First, yes, that's where the release packages were, in the extras repository in CentOS 8 (both Linux and Stream) [root@cs8 ~]# dnf list "*release*" ... centos-release-gluster9.noarch 1.0-2.el8 extras centos-release-hyperscale.noarch 4-1.el8 extras ...
Second, I think something is wrong with your install if you don't have the extras repository. Maybe you just need an update. [root@cs9 ~]# rpm -qa | grep release | sort centos-stream-release-9.0-12.el9.noarch epel-next-release-9-2.el9.noarch epel-release-9-2.el9.noarch
[root@cs9 ~]# dnf repolist all | grep extras extras-common CentOS Stream 9 - Extras packages enabled extras-common-source CentOS Stream 9 - Extras packages - Source disabled
[root@cs9 ~]# dnf list "*release*" ... centos-release-gluster9.noarch 1.0-2.el9s extras-common centos-release-hyperscale.noarch 9-4.el9s extras-common ...
Troy
On 05/04/2022 14:32, Troy Dawson wrote:
Second, I think something is wrong with your install if you don't have the extras repository. Maybe you just need an update.
If you have modified the yum supplied .repo file at any point then, when yum update updated that package, it will have spotted the modified file and create a .rpmnew file alongside it. It's likely that you need to rename those around and redo whatever modifications you made to the original to the new one.
T
On 05/04/2022 14:44, Trevor Hemsley via CentOS-devel wrote:
On 05/04/2022 14:32, Troy Dawson wrote:
Second, I think something is wrong with your install if you don't have the extras repository. Maybe you just need an update.
If you have modified the yum supplied .repo file at any point then, when yum update updated that package, it will have spotted the modified file and create a .rpmnew file alongside it. It's likely that you need to rename those around and redo whatever modifications you made to the original to the new one.
T
Seems that's what it is but... I do not recall any my own changes, also:
-> $ diff centos-addons.repo centos-addons.repo.rpmnew 9c9 < enabled=1 ---
enabled=0
93c93 < enabled=1 ---
enabled=0
111a112,131
[extras-common] name=CentOS Stream $releasever - Extras packages
metalink=https://mirrors.centos.org/metalink?repo=centos-extras-sig-extras-common-$st...
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Extras-SHA512
gpgcheck=1 repo_gpgcheck=0 metadata_expire=6h countme=1 enabled=1
[extras-common-source] name=CentOS Stream $releasever - Extras packages - Source
metalink=https://mirrors.centos.org/metalink?repo=centos-extras-sig-extras-common-sou...
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Extras-SHA512
gpgcheck=1 repo_gpgcheck=0 metadata_expire=6h enabled=0
Which would confirm no other user-manual changes, so... perhaps a glitch/bug?
many thanks, L.
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 05/04/2022 14:32, Troy Dawson wrote:
On Tue, Apr 5, 2022 at 6:07 AM lejeczek via CentOS-devel centos-devel@centos.org wrote:
On 05/04/2022 13:42, Neal Gompa wrote: > On Tue, Apr 5, 2022 at 8:39 AM lejeczek via CentOS-devel > <centos-devel@centos.org> wrote: >> Hi guys >> >> Why are *release* packages are still absent in 9? >> We (admins/users) read docs - take recently mentioned here >> Hyperscale SIG - do dns this *release* do dnf that *release* >> - dnf install centos-hyperscale-release - but, those are >> nowhere to be found or.. have I gone blind? >> If this all is delayed deliberately - may I ask why? >> > They're not delayed. They show up for me in the CentOS Extras repo > that is enabled by default on my CentOS Stream 9 systems. > > [root@57b98618010c /]# dnf repository-packages extras-common list > Last metadata expiration check: 0:00:12 ago on Tue Apr 5 12:41:53 2022. > Available Packages > centos-release-ceph-pacific.noarch 1.0-2.el9s extras-common > centos-release-ceph-quincy.noarch 1.0-2.el9s extras-common > centos-release-gluster10.noarch 1.0-2.el9s extras-common > centos-release-gluster9.noarch 1.0-2.el9s extras-common > centos-release-hyperscale.noarch 9-4.el9s extras-common > centos-release-hyperscale-experimental.noarch 9-4.el9s extras-common > centos-release-hyperscale-spin.noarch 9-4.el9s extras-common > centos-release-kmods.noarch 9-1.el9s extras-common > centos-release-nfs-ganesha4.noarch 1.0-2.el9s extras-common > centos-release-nfv-common.noarch 1-4.el9s extras-common > centos-release-nfv-openvswitch.noarch 1-4.el9s extras-common > centos-release-openstackclient-xena.noarch 1-1.el9s extras-common > centos-release-opstools.noarch 1-12.el9s extras-common > centos-release-ovirt45.noarch 9.0-1.el9s extras-common > centos-release-samba414.noarch 1.0-1.el9s extras-common > centos-release-samba415.noarch 1.0-1.el9s extras-common > centos-release-samba416.noarch 1.0-1.el9s extras-common > centos-release-storage-common.noarch 2-4.el9s extras-common > centos-release-virt-common.noarch 1-4.el9s extras-common > epel-next-release.noarch 9-2.el9 extras-common > epel-release.noarch 9-2.el9 extras-common > > I do not think it was in 'extras' in previous centOSes - was it? Is it really necessary to keep those not in default repo(s) - in repos which first have to enabled? But first: -> $ dnf repository-packages extras-common list Error: Unknown repo: 'extras-common' -> $ dnf search extras-common Last metadata expiration check: 0:31:17 ago on Tue 05 Apr 2022 13:32:00 BST. No matches found. -> $ dnf search release --enablerepo extras Extras 98 kB/s | 8.1 kB 00:00 Errors during downloading metadata for repository 'extras': - Status code: 404 for http://mirror.stream.centos.org/SIGs/9-stream/extras/repodata/repomd.xml (IP: 18.195.214.106) Error: Failed to download metadata for repo 'extras': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried Ignoring repositories: extras Last metadata expiration check: 0:31:58 ago on Tue 05 Apr 2022 12:37:08 BST. ================================ Name & Summary Matched: release ================================ centos-stream-release.noarch : CentOS Stream release files ... ... plus a few more but nothing like you showed above also: -> $ dnf repolist all | grep extras I'm puzzled a bit. thanks, LFirst, yes, that's where the release packages were, in the extras repository in CentOS 8 (both Linux and Stream) [root@cs8 ~]# dnf list "*release*" ... centos-release-gluster9.noarch 1.0-2.el8 extras centos-release-hyperscale.noarch 4-1.el8 extras ...
Second, I think something is wrong with your install if you don't have the extras repository. Maybe you just need an update.
I certainly do not have those below, I do have 'extras' (my last c&p was short). My install was from early days of cenOS 9, perhaps before offical public image.
[root@cs9 ~]# rpm -qa | grep release | sort centos-stream-release-9.0-12.el9.noarch epel-next-release-9-2.el9.noarch epel-release-9-2.el9.noarch
-> $ rpm -qa | grep release | sort centos-stream-release-9.0-12.el9.noarch epel-next-release-9-2.el9.noarch epel-release-9-2.el9.noarch
[root@cs9 ~]# dnf repolist all | grep extras extras-common CentOS Stream 9 - Extras packages enabled extras-common-source CentOS Stream 9 - Extras packages - Source disabled
What would an "update" constitute? I do check for updates regularly and if there are any I get them, as of today 'dnf' tells me: I'm up to day, no updates. I think that as that error from my c&p, which I did not highlight, might matter here - some relic from that early days which did not, does not, get updated?
[root@cs9 ~]# dnf list "*release*" ... centos-release-gluster9.noarch 1.0-2.el9s extras-common centos-release-hyperscale.noarch 9-4.el9s extras-common ...
Troy
-
lejeczek -
Neal Gompa -
Trevor Hemsley -
Troy Dawson