Bug 2124916 - Please branch and build dib-utils in epel8 and epel9
Summary: Please branch and build dib-utils in epel8 and epel9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: dib-utils
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Nemec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: EPELPackagersSIG 1844523
TreeView+ depends on / blocked
 
Reported: 2022-09-07 13:05 UTC by Davide Cavalca
Modified: 2022-10-20 16:12 UTC (History)
5 users (show)

Fixed In Version: dib-utils-0.0.11-12.el9 dib-utils-0.0.11-12.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-20 16:07:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Davide Cavalca 2022-09-07 13:05:23 UTC
Please branch and build dib-utils in epel8 and epel9.

If you do not wish to maintain dib-utils in epel8 and epel9,
or do not think you will be able to do this in a timely manner,
the EPEL Packagers SIG would be happy to be a co-maintainer of the package;
please add the epel-packagers-sig group through
https://src.fedoraproject.org/rpms/dib-utils/addgroup
and grant it commit access, or collaborator access on epel* branches.

Comment 1 Alfredo Moralejo 2022-09-14 11:31:05 UTC
What is requiring dib-utils for cs8 and cs9? anyting in EPEL?. note that dib-utils for centos stream is available in cloud sig.

Comment 2 Davide Cavalca 2022-09-21 15:38:18 UTC
It's a requirement for diskimage-builder, which is being branched for epel8 in https://bugzilla.redhat.com/show_bug.cgi?id=1844523 . As mentioned in that ticket, we can't use the Cloud SIG repos directly, because they include a lot of extra packages that will cause conflicts, and EPEL itself cannot depend on the Cloud SIG repos either.

Comment 3 Alfredo Moralejo 2022-09-22 09:34:11 UTC
Thanks Davide, it makes sense.

@bnemec only the Main admin of the package can add groups to packages. May you add epel-packagers-sig group through https://src.fedoraproject.org/rpms/dib-utils/addgroup and grant it commit access, or collaborator access on epel* branches?

If you prefer you can transfer Main Admin role of this package to me as part of the OpenStack SIG and I will take care.

Comment 4 Ben Nemec 2022-10-12 15:18:41 UTC
Done and done. Sorry for the delay.

Comment 5 Davide Cavalca 2022-10-12 15:38:25 UTC
Thanks! epel9 branch requested: https://pagure.io/releng/fedora-scm-requests/issue/48164

Comment 6 Fedora Update System 2022-10-12 15:45:35 UTC
FEDORA-EPEL-2022-39a1cb3330 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-39a1cb3330

Comment 7 Fedora Update System 2022-10-12 16:04:57 UTC
FEDORA-EPEL-2022-dcb9cd64d7 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-dcb9cd64d7

Comment 8 Fedora Update System 2022-10-12 18:01:17 UTC
FEDORA-EPEL-2022-39a1cb3330 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-39a1cb3330

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2022-10-12 18:03:55 UTC
FEDORA-EPEL-2022-dcb9cd64d7 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-dcb9cd64d7

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2022-10-20 16:07:10 UTC
FEDORA-EPEL-2022-dcb9cd64d7 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2022-10-20 16:12:39 UTC
FEDORA-EPEL-2022-39a1cb3330 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.