Spec URL: http://sochotni.fedorapeople.org/maven-gpg-plugin.spec SRPM URL: http://sochotni.fedorapeople.org/maven-gpg-plugin-1.1-1.fc14.src.rpm Description: This plugin signs all of the project's attached artifacts with GnuPG. It adds goals gpg:sign and gpg:sign-and-deploy-file. Note that this package has dependencies available only in dist-f14-maven221 target. Koji build: https://koji.fedoraproject.org/koji/taskinfo?taskID=2222334
Review: OK: rpmlint must be run on every package. Output: aven-gpg-plugin.noarch: W: no-documentation maven-gpg-plugin.noarch: W: non-conffile-in-etc /etc/maven/fragments/maven-gpg-plugin False positives. OK: The package must be named according to the Package Naming Guidelines . OK: The spec file name must match the base package %{name}, in the format %{name}.spec unless your package has an exemption. OK: The package must meet the Packaging Guidelines . OK: The package must be licensed with a Fedora approved license and meet the Licensing Guidelines . OK: The License field in the package spec file must match the actual license. OK: If (and only if) the source package includes the text of the license(s) in its own file, then that file, containing the text of the license(s) for the package must be included in %doc. OK: The spec file must be written in American English. OK: The spec file for the package MUST be legible. OK: The sources used to build the package must match the upstream source, as provided in the spec URL. OK: The package MUST successfully compile and build into binary rpms on at least one primary architecture. OK: All build dependencies must be listed in BuildRequires, except for any that are listed in the exceptions section of the Packaging Guidelines ; inclusion of those as BuildRequires is optional. Apply common sense. OK: Packages must NOT bundle copies of system libraries. OK: A package must own all directories that it creates. If it does not create a directory that it uses, then it should require a package which does create that directory. OK: A Fedora package must not list a file more than once in the spec file's %files listings. OK: Permissions on files must be set properly. Executables should be set with executable permissions, for example. Every %files section must include a %defattr(...) line. OK: Each package must consistently use macros. OK: The package must contain code, or permissable content. OK: Large documentation files must go in a -doc subpackage. OK: If a package includes something as %doc, it must not affect the runtime of the application. OK: Packages must not own files or directories already owned by other packages. OK: All filenames in rpm packages must be valid UTF-8. OK: Provides/Obsoletes are good. FIXIT: Package is missing Requires: gnupg2 . I know it's not obvious but at runtime this package execs gpg. See http://svn.apache.org/viewvc/maven/plugins/tags/maven-gpg-plugin-1.0/src/main/java/org/apache/maven/plugin/gpg/GpgSigner.java?revision=908991&view=markup line 143
I noticed add_to_maven_depmap maven-antrun-plugin, it should be maven-gpg-plugin.
Thanks huwang. Stanislav: please fix before importing
Ideally it should become %{name}
Thanks huwang for noticing, it's really better to have more pairs of eyes... I was also wondering about gnupg2 dependency, but it wasn't mentioned on the plugin web page so I thought that maybe they used some pure java implementation...Should have checked... Anyway, those things are fixed: SRPM URL: http://sochotni.fedorapeople.org/maven-gpg-plugin-1.1-2.fc13.src.rpm Spec URL: http://sochotni.fedorapeople.org/maven-gpg-plugin.spec Koji build: http://koji.fedoraproject.org/koji/taskinfo?taskID=2224276
Thanks, This package is APPROVED.
Thanks for the review. Requesting CVS: New Package CVS Request ======================= Package Name: maven-gpg-plugin Short Description: Plugin to sign all of the project's attached artifacts with GnuPG. Owners: sochotni Branches: InitialCC:
CVS done (by process-cvs-requests.py).
Package built: https://koji.fedoraproject.org/koji/buildinfo?buildID=176559 Closing.