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=646637 --- Comment #4 from Alexander Kurtakov <akurtako@xxxxxxxxxx> 2010-11-18 13:17:56 EST --- Package Review ============== Key: - = N/A x = Check ! = Problem ? = Not evaluated === REQUIRED ITEMS === [x] Rpmlint output: jnr-netdb.noarch: W: spelling-error %description -l en_US getservbyname -> dynameter jnr-netdb.noarch: W: spelling-error %description -l en_US getservbyport jnr-netdb.src: W: no-buildroot-tag [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. [!] Package meets the Packaging Guidelines[2]. See issues at the end of this comment. [x] Package successfully compiles and builds into binary rpms. [-] Buildroot is correct (%{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)) [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: LGPLv3 [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 [x] Spec file is legible and written in American English. [x] Sources used to build the package matches the upstream source, as provided in the spec URL. [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. [x] Package does not contain duplicates in %files. [x] Permissions on files are set properly. [x] Package has a %clean section, which contains rm -rf %{buildroot} (or $RPM_BUILD_ROOT). [x] Package consistently uses macros. [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] Packages have proper BuildRequires/Requires on jpackage-utils [!] 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, ...) [x] 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. === Other suggestions === [x] If possible use upstream build method (maven/ant/javac) [!] If package contains pom.xml files install it (including depmaps) even when building with ant [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. === Issues === 1. Package ships pom.xml so you must install it and add the maven depmap http://fedoraproject.org/wiki/Packaging:Java#Maven_pom.xml_files_and_depmaps 2.jar should be installed as %{name}.jar without %{name}-%{version}.jar 3. javadoc should be installe as %{buildroot}%{_javadocdir}/%{name} not %{buildroot}%{_javadocdir}/%{name}-%{version} 4. Executing ant jar javadoc instead of 2 ant calls will be a bit faster 5. Javadoc package doesn't really require the jar to be usable thus I would prefer to be able to install javadocs without dependency. This is up to you but if you do it note that you have to add the license file to the javadoc package too. -- 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