Spec URL: http://goldmann.fedorapeople.org/package_review/jboss-marshalling/1/jboss-marshalling.spec SRPM URL: http://goldmann.fedorapeople.org/package_review/jboss-marshalling/1/jboss-marshalling-1.3.0-1.fc15.src.rpm Description: This package contains JBoss Marshalling $ rpmlint jboss-marshalling-1.3.0-1.fc15.src.rpm jboss-marshalling.src: I: enchant-dictionary-not-found en_US jboss-marshalling.src: W: invalid-url URL: http://www.jboss.org/jbossmarshalling HTTP Error 403: Forbidden jboss-marshalling.src: W: invalid-url Source0: jboss-marshalling-1.3.0.GA.tar.xz 1 packages and 0 specfiles checked; 0 errors, 2 warnings. $ rpmlint jboss-marshalling.spec jboss-marshalling.spec: W: invalid-url Source0: jboss-marshalling-1.3.0.GA.tar.xz 0 packages and 1 specfiles checked; 0 errors, 1 warnings.
Removing FE-Legal block.
Mock build attempt shows this is blocked on jboss-modules
Andy, when you take smth for review please set the state to ASSIGNED. I'm doing it for you now. This way it's way easier to monitor things.
I just noticed that this is unblocked now. I will continue the review today.
Package Review ============== Key: - = N/A x = Check ! = Problem ? = Not evaluated === REQUIRED ITEMS === [x] Rpmlint output: These are ok (I still don't understand why the first one happens, as the page is fine in a browser): jboss-marshalling.src: W: invalid-url URL: http://www.jboss.org/jbossmarshalling HTTP Error 403: Forbidden jboss-marshalling.src: W: invalid-url Source0: jboss-marshalling-1.3.0.GA.tar.xz You might want to fix this, but it is very minor: jboss-marshalling-javadoc.noarch: W: spelling-error Summary(en_US) Javadocs -> Java docs, Java-docs, Avocados [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: LGPLv2+ [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. [-] 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. MD5SUM this package : ad845282351608abce7f852a0e4ed00c MD5SUM upstream package: ad845282351608abce7f852a0e4ed00c [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 or must require other packages for directories it uses. [x] Package does not contain duplicates in %files. [x] File sections do not contain %defattr(-,root,root,-) unless changed with good reason [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. [-] Fully versioned dependency in subpackages, if present. [-] Package contains a properly installed %{name}.desktop file if it is a GUI application. [!] 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 [x] If package uses tarball from VCS include comment how to re-create that tarball (svn export URL, git clone URL, ...) [-] 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_maven_depmap === Maven === [x] Use %{_mavenpomdir} macro for placing pom files instead of %{_datadir}/maven2/poms [x] If package uses "-Dmaven.test.skip=true" explain why it was needed in a comment [-] If package uses custom depmap "-Dmaven.local.depmap.file=*" explain why it's needed in a comment [x] Package DOES NOT use %update_maven_depmap in %post/%postun [x] Packages DOES NOT 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. Please fix the following: * BuildRequires must use jdk 1.6.0, as the build fails with 1.7.0 * javadocs are in %{_javadocdir}/%{name}/apidocs and should be in %{_javadocdir}/%{name} Other notes: As discussed on IRC, /usr/share/java/jboss is owned my multiple packages. It seems that people are okay with this for now, but I suspect that this will be reconsidered at some point.
Fixed! Spec URL: http://goldmann.fedorapeople.org/package_review/jboss-marshalling/2/jboss-marshalling.spec SRPM URL: http://goldmann.fedorapeople.org/package_review/jboss-marshalling/2/jboss-marshalling-1.3.0-2.fc17.src.rpm
Koji scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=3412389
The changes look good. APPROVED
Thanks for review! New Package SCM Request ======================= Package Name: jboss-marshalling Short Description: JBoss Marshalling Owners: goldmann
Git done (by process-git-requests).
Thanks for git, closing.