Bug 1982426

Summary:	centos-stream-release: FTBFS due to missing Git repository
Product:	Red Hat Enterprise Linux 9	Reporter:	Florian Weimer <fweimer>
Component:	distribution	Assignee:	RHEL Program Management <pm-rhel>
Status:	CLOSED NOTABUG	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	bstinson, jwboyer
Target Milestone:	beta	Flags:	pm-rhel: mirror+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-14 19:29:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1975099

Description Florian Weimer 2021-07-14 19:27:17 UTC

(filed against distribution because the component is not in Bugzilla)

centos-stream-release-9.0-1.0.4.el9.noarch is in the buildroot, but cannot be rebuilt. No SRPM can be created because the Git repository is missing. checkout.log from the buildSRPMFromSCM task contains:

$ git clone -n https://gitlab.com/redhat/centos-stream/rpms/centos-stream-release /var/lib/mock/c9s-build-67393-16836/root/chroot_tmpdir/scmroot/centos-stream-release
Cloning into '/var/lib/mock/c9s-build-67393-16836/root/chroot_tmpdir/scmroot/centos-stream-release'...
fatal: could not read Username for 'https://gitlab.com': No such device or address

But the repository does not exist, not even after Gitlab SSO login.

Comment 1 Josh Boyer 2021-07-14 19:29:39 UTC

https://gitlab.com/redhat/centos-stream/rpms/centos-release

Comment 2 Florian Weimer 2021-07-14 19:36:41 UTC

(In reply to Josh Boyer from comment #1)
> https://gitlab.com/redhat/centos-stream/rpms/centos-release

Uh-oh. Is there a reason why the repository and the SRPM name do not match? It makes the repository quite difficult to discover.

Is such a discrepancy common? Thanks.

Comment 3 Josh Boyer 2021-07-14 19:43:20 UTC

It's not common as far as I know, outside of the issues that gitlab has with "tree" and packages with a + in their name (which should be covered by syncing).  There is/was a similar case with dump/restore but that is the only other package I can think of off the top of my head that has a mismatch that isn't forced by gitlab limitations.

My guess is that it doesn't match because centos-release existed before Stream existed, and they retrofitted the existing repo because it's already there for CS8.  Brian could comment further.