Bug 2246219 - Please branch and build python-vobject in epel9
Summary: Please branch and build python-vobject in epel9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-vobject
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michel Lind
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: EPELPackagersSIG 2073952
TreeView+ depends on / blocked
 
Reported: 2023-10-25 20:20 UTC by Michel Lind
Modified: 2023-11-02 18:37 UTC (History)
3 users (show)

Fixed In Version: python-vobject-0.9.6.1-5.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2246807 (view as bug list)
Environment:
Last Closed: 2023-10-27 02:11:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michel Lind 2023-10-25 20:20:59 UTC
Please branch and build python-vobject in epel9.

If you do not wish to maintain python-vobject in 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/python-vobject/addgroup
and grant it commit access, or collaborator access on epel* branches.

I would also be happy to be a co-maintainer (FAS: salimma);
please add me through https://src.fedoraproject.org/rpms/python-vobject/adduser

Comment 1 Dan Horák 2023-10-26 11:45:30 UTC
I believe @pingou wouldn't mind and I have added commit rights to the SIG.

Comment 2 Michel Lind 2023-10-26 15:18:47 UTC
Thank you Dan!

Comment 3 Fedora Update System 2023-10-26 16:19:57 UTC
FEDORA-EPEL-2023-456252377b has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-456252377b

Comment 4 Fedora Update System 2023-10-27 02:11:24 UTC
FEDORA-EPEL-2023-456252377b has been pushed to the Fedora EPEL 9 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.