I have begun extracting scripts for the various dist-git repositories, to build maintainer scripts RPM package:
https://pagure.io/glibc-maintainer-scripts https://copr.fedorainfracloud.org/coprs/fweimer/glibc-maintainer-scripts/
I will happily add you as co-maintainers, but I think you have to request access on COPR first (and you need a pagure.io account by logging into it).
So far, I have only converted and extended sync-upstream.sh. quilt-patch.sh and gen-series.sh are likely to follow, and then something to convert our internal dist-git to an SRPM for submission to COPR, and a bit of Beaker automation stuff. I also have something to insert Patch/%patch references into the .spec file, but I don't know how useful that is (there are probably better tools for that).
Florian
On 08/26/2016 02:03 PM, Florian Weimer wrote:
I have begun extracting scripts for the various dist-git repositories, to build maintainer scripts RPM package:
https://pagure.io/glibc-maintainer-scripts https://copr.fedorainfracloud.org/coprs/fweimer/glibc-maintainer-scripts/
I will happily add you as co-maintainers, but I think you have to request access on COPR first (and you need a pagure.io account by logging into it).
So far, I have only converted and extended sync-upstream.sh. quilt-patch.sh and gen-series.sh are likely to follow, and then something to convert our internal dist-git to an SRPM for submission to COPR, and a bit of Beaker automation stuff. I also have something to insert Patch/%patch references into the .spec file, but I don't know how useful that is (there are probably better tools for that).
Awesome! Thanks for doing this!
Regarding insert Patch/%patch, I wanted this to be as automatic as possible with all the metadata in the patch file, and then have the spec file be assembled rather than ever having any merge conflicts in that file.
e.g.
cat ~/fedsrc/glibc-rawhide/template.patch # Fill in the "?", delete the <*> notes, and add any comments you need. Short description: ? <* Short description> Author(s): ? <* Who wrote them. Comma separated.> Origin: ? <* Source repo(s) where it came from or keyword "patch" if this is simply a patch> # Likely git://sourceware.org/git/glibc.git Bug-RHEL: ? <* Rhel bug #'s, comma separated e.g. #XXX, #YYY, #ZZZ> Bug-Fedora: ? <* Fedora bug #'s, comma separated e.g. #XXX, #YYY, #ZZZ> Bug-Upstream: ? <* Upstream bug#'s, comma separated e.g. #XXX, #YYY, #ZZZ> Upstream status: ? <* [not-needed|not-submitted|Patchwork URL|committed] for each commit> Spec status: ? <* [suppexc|hotfix|testfix] optional status marker for the release> <* The spec file is for a support exception build, hotfix build, or testing fix.> Spec changelog author: ? <* Optional: Email of the author as it should appear in the %changelog in the spec file> <* It is an error to list a Changelog Author and have no changelog block> [Spec changelog start] <* Optional: Contents of the changelog to be added into the spec file when updated> <* Include only the text of the changelog, no author or NVR line> [Spec changelog end] <* Additional descriptive text in comment block> <* If upstream status == committed then a copy of the upstream commit log follows> <* The actual patch contents>