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=647885 --- Comment #10 from Stanislav Ochotnicky <sochotni@xxxxxxxxxx> 2010-12-22 09:45:48 EST --- Package Review ============== Key: - = N/A x = Check ! = Problem ? = Not evaluated === REQUIRED ITEMS === [!] Rpmlint output: apache-rat.noarch: W: spelling-error %description -l en_US labour -> labor, lab our, lab-our Yeah, I'd also prefer labour, but it's supposed to be en_US apache-rat.noarch: W: spelling-error %description -l en_US metadata -> meta data, meta-data, metatarsus apache-rat.noarch: W: spelling-error %description -l en_US plugin -> plug in, plug-in, plugging apache-rat.noarch: W: non-conffile-in-etc /etc/maven/fragments/apache-rat apache-rat.src: W: spelling-error %description -l en_US labour -> labor, lab our, lab-our apache-rat.src: W: spelling-error %description -l en_US metadata -> meta data, meta-data, metatarsus apache-rat.src: W: spelling-error %description -l en_US plugin -> plug in, plug-in, plugging apache-rat.src:45: W: macro-in-comment %{name} apache-rat.src:45: W: macro-in-comment %{version} apache-rat.src:45: W: macro-in-comment %{release} apache-rat.src:46: W: macro-in-comment %{name} apache-rat.src:46: W: macro-in-comment %{version} apache-rat.src:46: W: macro-in-comment %{release} Remove those commented Requires please apache-rat.src: W: invalid-url Source0: apache-rat-0.8-20100827.tar.bz2 apache-rat-core.noarch: W: spelling-error %description -l en_US plugin -> plug in, plug-in, plugging apache-rat-javadoc.noarch: W: spelling-error Summary(en_US) Javadocs -> Java docs, Java-docs, Javanese apache-rat-tasks.noarch: W: non-conffile-in-etc /etc/ant.d/apache-rat 6 packages and 0 specfiles checked; 0 errors, 17 warnings [x] Package is named according to the Package Naming Guidelines[1]. [x] Spec file name must match the base package name, in the format %{name}.spec. [x] Package meets the Packaging Guidelines[2]. [x] Package successfully compiles and builds into binary rpms. [x] Buildroot definition is not present [x] Package is licensed with an open-source compatible license and meets other legal requirements as defined in the legal section of Packaging Guidelines[3,4]. [x] License field in the package spec file matches the actual license. License type: ASL 2.0 [x] 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 is included in %doc. [x] All independent sub-packages have license of their own [!] Spec file is legible and written in American English. Well..en_GB would be fine with me. Just that labour... [?] Sources used to build the package matches the upstream source, as provided in the spec URL. It would be good to have reasoning for use of snapshot. Plus giving svn export with "-r 990212" argument. [x] All build dependencies are listed in BuildRequires, except for any that are listed in the exceptions section of Packaging Guidelines[5]. [x] Package must own all directories that it creates. [x] Package requires other packages for directories it uses. core/plugin/tasks all have requires in jpackage utils and also on main package. You should probably respect dependencies so that when main package requires jpackage-utils don't put it also in dependencies. Same thing for example plugin requiring main package and also core. Core is enough because it pulls in main. IMO the less lines of code the better... [x] Package does not contain duplicates in %files. [x] Permissions on files are set properly. [x] Package does NOT have a %clean section which contains rm -rf %{buildroot} (or $RPM_BUILD_ROOT). (not needed anymore) [x] Package consistently uses macros (no %{buildroot} and $RPM_BUILD_ROOT mixing) [x] Package contains code, or permissable content. [x] Fully versioned dependency in subpackages, if present. [-] Package contains a properly installed %{name}.desktop file if it is a GUI application. [x] Package does not own files or directories owned by other packages. [x] Javadoc documentation files are generated and included in -javadoc subpackage [x] Javadocs are placed in %{_javadocdir}/%{name} (no -%{version} symlinks) [x] Packages have proper BuildRequires/Requires on jpackage-utils [x] Javadoc subpackages have Require: jpackage-utils [x] Package uses %global not %define [!] If package uses tarball from VCS include comment how to re-create that tarball (svn export URL, git clone URL, ...) Put that revision directly into svn export command I guess so it's not scattered. [-] If source tarball includes bundled jar/class files these need to be removed prior to building [x] All filenames in rpm packages must be valid UTF-8. [x] Jar files are installed to %{_javadir}/%{name}.jar (see [6] for details) [x] If package contains pom.xml files install it (including depmaps) even when building with ant [x] pom files has correct add_to_maven_depmap call which resolves to the pom file (use "JPP." and "JPP-" correctly) === Maven === [!] Use %{_mavenpomdir} macro for placing pom files instead of %{_datadir}/maven2/poms [!] If package uses "-Dmaven.test.skip=true" explain why it was needed in a comment Please add reasoning (and prefer to use -Dmaven.test.ignore.failure=true) [-] If package uses custom depmap "-Dmaven2.jpp.depmap.file=*" explain why it's needed in a comment [-] Package uses %update_maven_depmap in %post/%postun [x] Packages have Requires(post) and Requires(postun) on jpackage-utils (for %update_maven_depmap macro) === Other suggestions === [x] If possible use upstream build method (maven/ant/javac) [x] Avoid having BuildRequires on exact NVR unless necessary [x] Package has BuildArch: noarch (if possible) [x] Latest version is packaged. [x] Reviewer should test that the package builds in mock. Tested on: fedora-rawhide-x86_64 === Other Issues === 1. patch adding maven-settings to deps is no longer needed (bug in maven that was fixed recently) -- 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