On Tue, Aug 24, 2021 at 9:22 AM Troy Dawson <tdawson@xxxxxxxxxx> wrote: > > > > On Mon, Aug 23, 2021 at 6:41 PM Orion Poplawski <orion@xxxxxxxx> 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 _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
