<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Wed, Oct 9, 2019, at 14:53, John Broome wrote:<br></div><blockquote type="cite" id="qt"><div dir="ltr"><div dir="ltr"><br></div><div><br></div><div class="qt-gmail_quote"><div class="qt-gmail_attr" dir="ltr">On Wed, Oct 9, 2019 at 1:54 PM Lance Albertson <<a href="mailto:lance@osuosl.org">lance@osuosl.org</a>> wrote:<br></div><blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-color:rgb(204, 204, 204);border-left-style:solid;border-left-width:1px;padding-left:1ex;" class="qt-gmail_quote"><div dir="ltr"><div dir="ltr"><div style="font-family:arial, helvetica, sans-serif;"><br></div></div><div><br></div><div class="qt-gmail_quote"><div class="qt-gmail_attr" dir="ltr">On Wed, Oct 9, 2019 at 10:36 AM Trevor Hemsley <<a href="mailto:trevor.hemsley@ntlworld.com">trevor.hemsley@ntlworld.com</a>> wrote:<br></div><blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-color:rgb(204, 204, 204);border-left-style:solid;border-left-width:1px;padding-left:1ex;" class="qt-gmail_quote"><div bgcolor="#FFFFFF"><div>On 09/10/2019 18:22, Lance Albertson
wrote:<br></div><blockquote type="cite"><div dir="ltr"><div style="font-family:arial, helvetica, sans-serif;">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:<br></div><div style="font-family:arial, helvetica, sans-serif;"><br></div><div style="font-family:arial, helvetica, sans-serif;"><div>[cr]<br></div><div> name=CentOS-$releasever - cr<br></div><div> baseurl=<a href="http://mirror.centos.org/$contentdir/$releasever/cr/$basearch/os/">http://mirror.centos.org/$contentdir/$releasever/cr/$basearch/os/</a><br></div><div> gpgcheck=1<br></div><div> enabled=1<br></div><div> gpgkey=<a>file:///etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial</a><br></div></div><div style="font-family:arial, helvetica, sans-serif;"><br></div><div style="font-family:arial, helvetica, sans-serif;">$ <span style="font-family:Arial, Helvetica, sans-serif" class="font">dnf repolist </span><br></div><div>CentOS-8 - AppStream
173 kB/s | 5.6 MB 00:33 <br></div><div> CentOS-8 - Base
976 kB/s | 5.3 MB 00:05 <br></div><div> CentOS-8 - cr
222 B/s | 239 B 00:01 <br></div><div> Error: Failed to synchronize cache for repo 'cr'<br></div><div> <br></div><div style="font-family:arial, helvetica, sans-serif;"><br></div><div style="font-family:arial, helvetica, sans-serif;">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?<br></div></div></blockquote><div><br></div><div><br></div><div>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.<br></div><div> <br></div><div> 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.<br></div></div></blockquote><div><br></div><div style="font-family:arial, helvetica, sans-serif;">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?<br></div></div></div></blockquote><div><br></div><div><br></div><div>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. <br></div></div></div><div>_______________________________________________<br></div><div>CentOS-devel mailing list<br></div><div>CentOS-devel@centos.org<br></div><div>https://lists.centos.org/mailman/listinfo/centos-devel<br></div><div><br></div></blockquote><div><br></div><div>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.<br></div><div><br></div><div>We plan to do the latter with the next batch of updates. Stay tuned!<br></div><div><br></div><div>--Brian<br></div></body></html>