<br><br><div class="gmail_quote">On Wed, Apr 6, 2011 at 8:11 PM, Jeffrey Ness <span dir="ltr"><<a href="mailto:jeffrey.ness@rackspace.com">jeffrey.ness@rackspace.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello everyone,<br>
<br>
As I'm new to the community and RPM Package Review (and development), I figured a tool to assist with reviews would be a nice time saver.<br>
<br>
With that said I have a simple Python tool (still in early beta stages) which does just that.<br>
<br>
Keeping with the concept of sharing, I wanted to hand this tool out to the community and get any feedback from y'all:<br>
<br>
<a href="https://github.com/jness/spec_checks" target="_blank">https://github.com/jness/spec_checks</a><br>
<br>
This tool uses the "Package Review Guidelines" written by Tom 'spot' Callaway:<br>
<br>
<a href="http://fedoraproject.org/wiki/Packaging/ReviewGuidelines" target="_blank">http://fedoraproject.org/wiki/Packaging/ReviewGuidelines</a><br>
<br>
Thanks for your time<br>
Jeffrey-<br>
<font color="#888888"><br>
--<br>
devel mailing list<br>
<a href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/devel" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/devel</a><br>
</font></blockquote></div><br><br>I am working on a tool too, there automates much of the dirty work when reviewing a package<br><br>Like:<br>- Downloading SRPM & SPEC from bugzilla report<br>- Download upstream source<br>
- check md5sums<br>- do a total review report will both manual & automated checks, ready to complete and paste into the bugzilla report.<br><br><a href="https://github.com/timlau/FedoraReview">https://github.com/timlau/FedoraReview</a><br>
<br>checkout and cd to the src/ dir.<br><br>./review.py -b <bugzilla report number><br><br>it will download the spec & srpm from the bugzilla report and build them in mock and run a number of test and generate<br>
a report there will be opened in gedit along with the spec file, so the stuff no automated can be reviewed manually.<br><br>You will need to have mock installed and be member of the mock group for the build to work.<br><br>
./review.py --help <br><br>Will show you the other options of the tools. <br><br>./review.py -b <bugzilla report number> -u <bugzilla user> -p <bugzilla password> --assign<br><br>Will assign the review to <bugzilla user> and set the review flags in the bugzilla report.<br>
<br>It is still under heavy development, but can be very useful.<br><br>Tim<br>