http://home.nycap.rr.com/nagaland/rpms/mmv.spec http://home.nycap.rr.com/nagaland/rpms/mmv-1.01b-1.src.rpm Description: howdy folks, I'd appreciate a new package review of mmv. it's similar to but more flexible than rename... mmv is a program to move/copy/append/link multiple files according to a set of wildcard patterns. I think the pristine "upstream" source is lost, but since debian's and suse's sources are identical, I just based off of debian's mmv_1.01b.orig.tar.gz (without the annoying .orig appendages). The source is then patched up to debian's 12.2 release which includes compile/segfault/lfs patches. lastly, I added in pie to the build. thanks, zing
Blocker: - Use the full source URL to the tarball in the source tag, even if it contains ".orig." (http://ftp.debian.org/debian/pool/main/m/mmv/mmv_1.01b.orig.tar.gz). Possible improvements : - Add symbolic links to mmv called mcp, mad and mln, as specified in the man page.
Thanks! I've updated the package here: http://home.nycap.rr.com/nagaland/rpms/mmv.spec http://home.nycap.rr.com/nagaland/rpms/mmv-1.01b-2.src.rpm * Wed Sep 28 2005 Zing <shishz> - 1.01b-2 - QA from Aurelien Bompard - don't change source name - symlink mcp/mad/mln
Review for release 2: * RPM name is OK * Source mmv_1.01b.orig.tar.gz is the same as upstream * Builds fine in mock * rpmlint of mmv looks OK * File list of mmv looks OK * Works fine APPROVED
* Wed Sep 28 2005 Zing <shishz> - 1.01b-2 - QA from Aurelien Bompard - don't change source name - symlink mcp/mad/mln This formatting looks a bit strange. You really don't need to mention the QA part and just list what actually changed instead without the indentation.
Changed summary for tracking purposes.
Package Change Request ====================== Package Name: mmv New Branches: EL-5 Owners: till I would like to maintain a EL-5 branch of mmv, afaik the F-* maintainer does not want to participate in EPEL. He was asked a long time ago by Thorsten Leemhuis.
cvs done.
(In reply to comment #7) > cvs done. Which branch did you use as the source for the new EL-5 branch? It seems not to be devel, because the spec is only at revision 9, but in devel it is at revision 11.
By default EL-5 branches use FC-6 (if it exists) and devel if it does not. (Since EL5 is based off of FC-6).