modular bugzilla components

[Orion Poplawski]

The "zabbix" package exists in EPEL8 in two forms:

zabbix40 - non-module 4.0 package.
zabbix - module with 5.0 stream.

Because the "zabbix" dist-git does not have a epel8 branch, there is no 
"zabbix" component in bugzilla for EPEL8.  Should I create an epel8 
branch but then retire it just to create a bugzilla component?  Or 
something else?


-- 
Orion Poplawski
he/him/his - surely the least important thing about me
Manager of NWRA Technical Systems          720-772-5637
NWRA, Boulder/CoRA Office             FAX: [phone]
3380 Mitchell Lane                       orion(a)nwra.com
Boulder, CO 80301                 https://www.nwra.com/

[Troy Dawson]

On Mon, Aug 23, 2021 at 6:41 PM Orion Poplawski <orion(a)nwra.com&gt; wrote:

>  The "zabbix" package exists in EPEL8 in two forms:
>
>  zabbix40 - non-module 4.0 package.
>  zabbix - module with 5.0 stream.
>
>  Because the "zabbix" dist-git does not have a epel8 branch, there is no
>  "zabbix" component in bugzilla for EPEL8.  Should I create an epel8
>  branch but then retire it just to create a bugzilla component?  Or
>  something else?
>  
My opinion, yes.
This does two things.
1 - creates an EPEL zabbix bugzilla component
2 - creates a dead.package file in the dist-git branch, that if people
read, will point them to the right place.

But that is my opinion.  If others know of a good way to get a bugzilla
component in, there might be better ways.

Troy

[Josh Boyer]

On Tue, Aug 24, 2021 at 9:22 AM Troy Dawson <tdawson(a)redhat.com&gt; wrote:
>  On Mon, Aug 23, 2021 at 6:41 PM Orion Poplawski <orion(a)nwra.com&gt; wrote:
> >
> > The "zabbix" package exists in EPEL8 in two forms:
> >
> > zabbix40 - non-module 4.0 package.
> > zabbix - module with 5.0 stream.
> >
> > Because the "zabbix" dist-git does not have a epel8 branch, there is no
> > "zabbix" component in bugzilla for EPEL8.  Should I create an epel8
> > branch but then retire it just to create a bugzilla component?  Or
> > something else?
>
>
>  My opinion, yes.
>  This does two things.
>  1 - creates an EPEL zabbix bugzilla component
>  2 - creates a dead.package file in the dist-git branch, that if people read, will point
> them to the right place.
>
>  But that is my opinion.  If others know of a good way to get a bugzilla component in,
> there might be better ways. 
That seems rather complicated.  Perhaps Ben could just add the
component to the EPEL product in bugzilla directly.

Ben, can you do this via the Program Management interfaces?

josh

[Miro Hrončok]

On 24. 08. 21 3:40, Orion Poplawski wrote:
>  Should I create an epel8 branch but then retire it just to create a
> bugzilla 
>  component? 
AFAIK this wont work. Packages retired on EPEL have the components blocked.

-- 
Miro Hrončok
-- 
Phone: [phone]
IRC: mhroncok

[Kevin Fenzi]

On Tue, Aug 24, 2021 at 09:44:12PM +0200, Miro Hrončok wrote:
>  On 24. 08. 21 3:40, Orion Poplawski wrote:
>  > Should I create an epel8 branch but then retire it just to create a
>  > bugzilla component?
>  
>  AFAIK this wont work. Packages retired on EPEL have the components blocked. 
Right. 

Instead we need to tech our bugzilla sync to sync EPEL modules to
'Fedora EPEL Modules/$name' like our Fedora modules are made under
'Fedora Modules/$name'.

I've filed: 
https://pagure.io/fedora-infra/toddlers/issue/82
about this. 

kevin