I see that CentOS-CR.repo is included with the centos-release package, however there is no CR repo to be found at the location it has at the base url:
[cr] name=CentOS-$releasever - cr baseurl=http://mirror.centos.org/$contentdir/$releasever/cr/$basearch/os/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial
$ dnf repolist CentOS-8 - AppStream 173 kB/s | 5.6 MB 00:33 CentOS-8 - Base 976 kB/s | 5.3 MB 00:05 CentOS-8 - cr 222 B/s | 239 B 00:01 Error: Failed to synchronize cache for repo 'cr'
My assumption was that the AppStream repo was going to replace the CR repo, is that correct? I'm wondering if that repo file was added accidentally?
Thanks-
On 09/10/2019 18:22, Lance Albertson wrote:
I see that CentOS-CR.repo is included with the centos-release package, however there is no CR repo to be found at the location it has at the base url:
[cr] name=CentOS-$releasever - cr baseurl=http://mirror.centos.org/$contentdir/$releasever/cr/$basearch/os/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial
$ dnf repolist CentOS-8 - AppStream 173 kB/s | 5.6 MB 00:33 CentOS-8 - Base 976 kB/s | 5.3 MB 00:05 CentOS-8 - cr 222 B/s | 239 B 00:01 Error: Failed to synchronize cache for repo 'cr'
My assumption was that the AppStream repo was going to replace the CR repo, is that correct? I'm wondering if that repo file was added accidentally?
No. The CR repo is only used at point release time. It's used to contain the next CentOS point release in the interval between the RHEL point release coming out and the GA release of the equivalent CentOS version a few weeks later. It's designed to allow people to get access to the packages from the next point release while the team work on creating the isos/images etc.
It's so you don't have to wait until the isos are built etc. Means everyone gets access to the content a few weeks earlier than otherwise.
Trevor
On Wed, Oct 9, 2019 at 10:36 AM Trevor Hemsley trevor.hemsley@ntlworld.com wrote:
On 09/10/2019 18:22, Lance Albertson wrote:
I see that CentOS-CR.repo is included with the centos-release package, however there is no CR repo to be found at the location it has at the base url:
[cr] name=CentOS-$releasever - cr baseurl=http://mirror.centos.org/$contentdir/$releasever/cr/$basearch/os/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial
$ dnf repolist CentOS-8 - AppStream 173 kB/s | 5.6 MB 00:33 CentOS-8 - Base 976 kB/s | 5.3 MB 00:05 CentOS-8 - cr 222 B/s | 239 B 00:01 Error: Failed to synchronize cache for repo 'cr'
My assumption was that the AppStream repo was going to replace the CR repo, is that correct? I'm wondering if that repo file was added accidentally?
No. The CR repo is only used at point release time. It's used to contain the next CentOS point release in the interval between the RHEL point release coming out and the GA release of the equivalent CentOS version a few weeks later. It's designed to allow people to get access to the packages from the next point release while the team work on creating the isos/images etc.
It's so you don't have to wait until the isos are built etc. Means everyone gets access to the content a few weeks earlier than otherwise.
If that's the case, should there at least be an empty repo that makes dnf happy until there's time there's actual content to be added there?
On Wed, Oct 9, 2019 at 1:54 PM Lance Albertson lance@osuosl.org wrote:
On Wed, Oct 9, 2019 at 10:36 AM Trevor Hemsley < trevor.hemsley@ntlworld.com> wrote:
On 09/10/2019 18:22, Lance Albertson wrote:
I see that CentOS-CR.repo is included with the centos-release package, however there is no CR repo to be found at the location it has at the base url:
[cr] name=CentOS-$releasever - cr baseurl=http://mirror.centos.org/$contentdir/$releasever/cr/$basearch/os/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial
$ dnf repolist CentOS-8 - AppStream 173 kB/s | 5.6 MB 00:33 CentOS-8 - Base 976 kB/s | 5.3 MB 00:05 CentOS-8 - cr 222 B/s | 239 B 00:01 Error: Failed to synchronize cache for repo 'cr'
My assumption was that the AppStream repo was going to replace the CR repo, is that correct? I'm wondering if that repo file was added accidentally?
No. The CR repo is only used at point release time. It's used to contain the next CentOS point release in the interval between the RHEL point release coming out and the GA release of the equivalent CentOS version a few weeks later. It's designed to allow people to get access to the packages from the next point release while the team work on creating the isos/images etc.
It's so you don't have to wait until the isos are built etc. Means everyone gets access to the content a few weeks earlier than otherwise.
If that's the case, should there at least be an empty repo that makes dnf happy until there's time there's actual content to be added there?
I thought it shipped disabled by default, and you explicitly had to enable if you wanted packages before the next point release was fully released.
On Wed, Oct 9, 2019, at 14:53, John Broome wrote:
On Wed, Oct 9, 2019 at 1:54 PM Lance Albertson lance@osuosl.org wrote:
On Wed, Oct 9, 2019 at 10:36 AM Trevor Hemsley trevor.hemsley@ntlworld.com wrote:
On 09/10/2019 18:22, Lance Albertson wrote:
I see that CentOS-CR.repo is included with the centos-release package, however there is no CR repo to be found at the location it has at the base url:
[cr] name=CentOS-$releasever - cr baseurl=http://mirror.centos.org/$contentdir/$releasever/cr/$basearch/os/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial
$ dnf repolist CentOS-8 - AppStream 173 kB/s | 5.6 MB 00:33 CentOS-8 - Base 976 kB/s | 5.3 MB 00:05 CentOS-8 - cr 222 B/s | 239 B 00:01 Error: Failed to synchronize cache for repo 'cr'
My assumption was that the AppStream repo was going to replace the CR repo, is that correct? I'm wondering if that repo file was added accidentally?
No. The CR repo is only used at point release time. It's used to contain the next CentOS point release in the interval between the RHEL point release coming out and the GA release of the equivalent CentOS version a few weeks later. It's designed to allow people to get access to the packages from the next point release while the team work on creating the isos/images etc.
It's so you don't have to wait until the isos are built etc. Means everyone gets access to the content a few weeks earlier than otherwise.
If that's the case, should there at least be an empty repo that makes dnf happy until there's time there's actual content to be added there?
I thought it shipped disabled by default, and you explicitly had to enable if you wanted packages before the next point release was fully released. _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
It's true that we ship this with enabled=0 by default, but it's also true that it would be correct and friendly to include empty repodata on the mirrors.
We plan to do the latter with the next batch of updates. Stay tuned!
--Brian
On Wed, Oct 9, 2019 at 1:02 PM Brian Stinson brian@bstinson.com wrote:
On Wed, Oct 9, 2019, at 14:53, John Broome wrote:
On Wed, Oct 9, 2019 at 1:54 PM Lance Albertson lance@osuosl.org wrote:
If that's the case, should there at least be an empty repo that makes dnf happy until there's time there's actual content to be added there?
I thought it shipped disabled by default, and you explicitly had to enable if you wanted packages before the next point release was fully released.
It's true that we ship this with enabled=0 by default, but it's also true that it would be correct and friendly to include empty repodata on the mirrors.
We plan to do the latter with the next batch of updates. Stay tuned!
Yes I enabled it manually to test all of the shipped repo files included for something I was working on and discovered that it was missing for 8. I already saw the bug open about the same issue happening with the debuginfo repo so I'll wait for both of those :)
Thanks!
On 10/10/19 1:23 AM, John Broome wrote:
On Wed, Oct 9, 2019 at 1:54 PM Lance Albertson <lance@osuosl.org mailto:lance@osuosl.org> wrote:
If that's the case, should there at least be an empty repo that makes dnf happy until there's time there's actual content to be added there?I thought it shipped disabled by default, and you explicitly had to enable if you wanted packages before the next point release was fully released.
It should still exist.
I, and I presume like others, will often use "dnf --enablerepo=* search hotness" to see if a package is hiding in a repo I keep disabled by default. A missing repo breaks this process. As a result I have the CR and Media repo files completely commented out (if I remove the file it will simply be replaced by an update). For those who want the same, try:
sed --in-place "s/^/# /g" /etc/yum.repos.d/CentOS-Media.repo sed --in-place "s/# #/##/g" /etc/yum.repos.d/CentOS-Media.repo sed --in-place "s/^/# /g" /etc/yum.repos.d/CentOS-Vault.repo sed --in-place "s/# #/##/g" /etc/yum.repos.d/CentOS-Vault.repo sed --in-place "s/^/# /g" /etc/yum.repos.d/CentOS-CR.repo sed --in-place "s/# #/##/g" /etc/yum.repos.d/CentOS-CR.repo
That said, last I checked, the source and debuginfo repos are also defined, but missing. This causes problems. That means I currently need to type "dnf --enablerepo=* --disablerepo=*source --disablerepo=*debuginfo search hotness" ...
I assume the core team simply hasn't had time to set those repos yet ... and I don't mind waiting patiently, but perhaps it's time to create, at the very least, an empty repo, as suggested above.
L~
-
Brian Stinson -
John Broome -
Ladar Levison -
Lance Albertson -
Trevor Hemsley