Bug 2037871

Summary:	Import external repository definition and gpg public key for Extras pkgs (built/maintained by CentOS SIGs)
Product:	Red Hat Enterprise Linux 9	Reporter:	farrotin
Component:	distribution	Assignee:	Brian Stinson <bstinson>
Status:	CLOSED WONTFIX	QA Contact:	Brian Stinson <bstinson>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	bstinson, jwboyer, lisas, ngompa13
Target Milestone:	rc	Keywords:	Triaged
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:	2023-07-06 07:28:06 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:

Description farrotin 2022-01-06 17:41:12 UTC

Description of problem:

Starting from Stream 9 , we'd like to have SIGs be able to just build and push their own -release packages (containining their own .repo and gpg pub key) for the content they build for/on CentOS Stream 9 (on https://cbs.centos.org)

Instead of relying on someone internal to just build such packages, another approach was proposed by Brian Stinson on the centos-devel list (https://lists.centos.org/pipermail/centos-devel/2021-November/098666.html)

Creating this ticket to have a reference for the upcoming MR against centos-release (it's *not* against redhat-release but centos-release isn't listed as possible component and this change is *CentOS* specific (for Special Interest Groups) and no for RHEL9

Comment 2 Neal Gompa 2022-01-17 12:07:50 UTC

This is not exactly configured correctly in centos-stream-release yet. I've proposed an MR to fix that: https://gitlab.com/redhat/centos-stream/rpms/centos-release/-/merge_requests/24

Comment 7 RHEL Program Management 2023-07-06 07:28:06 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.