Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=628030 --- Comment #2 from Stanislav Ochotnicky <sochotni@xxxxxxxxxx> 2010-08-30 11:29:36 EDT --- NEEDSWORK: rpmlint must be run on every package. The output should be posted in the review. maven-ant-tasks.noarch: W: spelling-error %description -l en_US Mavent -> Maven, Mavens, Ma vent maven-ant-tasks.noarch: W: spelling-error %description -l en_US xml -> XML, cml, ml maven-ant-tasks.noarch: W: non-conffile-in-etc /etc/maven/fragments/maven-ant-tasks maven-ant-tasks.src: W: spelling-error %description -l en_US Mavent -> Maven, Mavens, Ma vent maven-ant-tasks.src: W: spelling-error %description -l en_US xml -> XML, cml, ml maven-ant-tasks-javadoc.noarch: W: spelling-error Summary(en_US) Javadocs -> Java docs, Java-docs, Javanese maven-ant-tasks-javadoc.noarch: W: non-standard-group Development/Documentation 3 packages and 0 specfiles checked; 0 errors, 7 warnings. Mavent -> Maven Development/Documentation -> Documentation 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. NEEDSWORK: All independent sub-packages have License of their own (if it exists) javadoc subpackage needs either LICENSE in %files or it needs to Require main package 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. Reviewers should use md5sum for this task. If no upstream URL can be specified for this package, please see the Source URL Guidelines for how to deal with this. 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. (The definition of large is left up to the packager's best judgement, but is not restricted to size. Large can refer to either size or quantity). OK: If a package includes something as %doc, it must not affect the runtime of the application. To summarize: If it is in %doc, the program must run properly if it is not present. NEEDSWORK: Packages must not own files or directories already owned by other packages. %{_mavendepmapfragdir} and pom directory are provided by jpackage-utils, use "/*" at the end to include only files, not directories themselves OK: All filenames in rpm packages must be valid UTF-8. Other: * You use maven to first install dependencies (ant and plexus-container) into local repo. Instead you should use depmap file (-Dmaven2.jpp.depmap.file). See for example apache-commons-logging package for usage/file format. * instead of %{_datadir}/maven2/poms you can use %{_mavenpomdir} * while you are changing stuff can you rename maven2-plugin-X BRs to new names? * usually there is also versioned symlink to javadoc dir All in all package is pretty good, no major issue. Fix those small things and I'll approve. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review