Second send, since I managed to use the old buildsys list address in my previous forward of this message. Sigh...
I've forwarded Julian's proposed plugin for mock to perform signing since he wasn't sure where best to send it. I have *not* reviewed this patch yet but will be doing so in the near future. Help reviewing from anyone with signing expertise in the Fedora infrastructure would be appreciated. Clark Begin forwarded message: Date: Tue, 10 Feb 2015 01:30:03 +0000 From: Julien Ballet <[email protected]> To: "[email protected]" <[email protected]> Subject: Mock, autosigning Hi, I’ve been wandering around the different mock pages (wiki/trac), and I haven’t found any indications about the preferred way to submit patches for mock. The wiki page tells to go to Trac, and trac doesn’t say anything :) So please forgive me for looking at git logs and reaching out to the most recent/active contributor :) I’ve been working on a small patch to mock that adds automatic signing of built package. It also introduces a small api change, so please let me know if it’s wrong and if you have a better idea :) Let me also know if there’s a better place to post patches :) Regards, Lta.
|
Hi,
I’ve been wandering around the different mock pages (wiki/trac), and I haven’t found any indications about the preferred way to submit patches for mock. The wiki page tells to go to Trac, and trac doesn’t say anything :) So please forgive me for looking at
git logs and reaching out to the most recent/active contributor :)
I’ve been working on a small patch to mock that adds automatic signing of built package. It also introduces a small api change, so please let me know if it’s wrong and if you have a better idea :)
Let me also know if there’s a better place to post patches :)
Regards,
Lta.
|
sign-plugin.patch
Description: Binary data
pgpEcrdPPluO4.pgp
Description: OpenPGP digital signature
-- buildsys mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/buildsys
