#1342 Exception procedure: nonresponsive package maintainer
Closed None Opened 9 years ago by fcami.

Hi,

As mentioned on devel, I need an up-to-date disper build for EPEL6 and EPEL7.
There are no EPEL branches for disper and the package is outdated (by
~18 months) in rawhide.

I've opened a bug mentioning I can help maintaining the package with
an updated srpm:
https://bugzilla.redhat.com/show_bug.cgi?id=1143055
& asked for commit access in pkgdb.
Unfortunately there hasn't been any answer yet.
I've checked koji - marionline hasn't built anything for a year or so.

Note that I only really want to create and maintain the EPEL6/EPEL7
branches at the moment, so I'd like to use the exception procedure
instead of the normal 3-week-long procedure - to be able to create said branches ASAP.

Best regards,
François


I'm +1 to granting François access to the EPEL 6 and EPEL 7 branches.

That being said, I'm not sure you even need the exception process here. Given that the branches you want don't yet exist, you can probably just file an SCM request to have it created with you as the point-of-contact: http://fedoraproject.org/wiki/Package_SCM_admin_requests#Package_Change_Requests_for_existing_packages

Given that I can't find a review BZ for the original disper package, you should use the BZ you mentioned in the description for this ticket.

Right. If the fedora maintainer does not wish to maintain in EPEL, or if they fail to reply after a week, you are free to move forward and create/maintain the epel branches.

In this case it might be nice however to also update rawhide as the current maintainer is missing. So, +1 to adding you there as well from me. ;)

Waiting one week is fine, thank you!

For the record, Mario replied to the bug report and added me as co-maintainer.
I'll be opening the EPEL branches shortly.

Login to comment on this ticket.

Metadata