May I perform buildroot overrides for EPEL?

Dennis Gilmore dennis at ausil.us
Fri Feb 26 21:04:36 UTC 2010


On Friday 26 February 2010 11:47:42 am Till Maas wrote:
> On Fri, Feb 26, 2010 at 10:14:06AM -0700, Kevin Fenzi wrote:
> > We also usually keep the ticket open after making the request so the
> > submitter can tell us when they don't need it anymore, and we can untag
> > the override. :)
> 
> This is how it usually happens for Fedora, too. The workflow is not
> completely documented, except for how to check whether a request is
> sane:
> https://fedoraproject.org/wiki/Buildroot_override_SOP
> 
> A big / problematic difference is, that in EPEL the owner / state of the
> tickets are not changed if someone processes then. Therefore it seems
> not possible to query trac for unhandled trac requests. For Fedora there
> is a nice RSS feed for all unhandled koji issues. But there seems to be
> no way to get one for all tickets that do not have any comments.
> 
> > If you would like to start doing them I have no objections.
> 
> So in case there will be another ticket for both Fedora and EPEL, does
> there need to be a seperate ticket in the EPEL component to track it or
> can I just track it in the Fedora ticket?
> 
> Regards
> Till
One big difference we have is that we use a koji group to grant permissions and 
you don't need to force the tagging operations. I have added you to the epel-
override group. 

Dennis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://listman.redhat.com/archives/epel-devel-list/attachments/20100226/93f06a6f/attachment.sig>


More information about the epel-devel-list mailing list