Spec URL: http://www.macs.hw.ac.uk/~mef3/review/gnu-trove.spec SRPM URL: http://www.macs.hw.ac.uk/~mef3/review/gnu-trove-2.1.0-1.fc12.src.rpm Description: The GNU Trove library has two objectives: Provide "free" (as in "free speech" and "free beer"), fast, lightweight implementations of the java.util Collections API. These implementations are designed to be pluggable replacements for their JDK equivalents. Whenever possible, provide the same collections support for primitive types. This gap in the JDK is often addressed by using the "wrapper" classes (java.lang.Integer, java.lang.Float, etc.) with Object-based collections. For most applications, however, collections which store primitives directly will require less space and yield significant performance gains. This package was imported from JPackage
A dup of bug 504891?
I'm somewhat disappointed that there's been no response; what's the point of dumping so many packages on the reviewers if their comments will be ignored? In the absence of other guidance, I'll go ahead and close this as a dup. *** This bug has been marked as a duplicate of bug 504891 ***
*** Bug 504891 has been marked as a duplicate of this bug. ***
Following feedback in the other bug, I've closed it as a duplicate of this one instead. I'll incorporate changes from and comments on that package into this one shortly.
New packages here: Spec URL: http://www.macs.hw.ac.uk/~mef3/review/trove4j.spec SRPM URL: http://www.macs.hw.ac.uk/~mef3/review/trove4j-2.1.0-2.fc12.src.rpm Changelog: - Rename to trove4j - Re-add GCJ stuff per discussion on fedora-java-devel-list - Link javadoc to unversioned directory - Fix License tag and include all documentation
Is the jboss stuff relevant in Fedora or just a jpackage feature? I think you should at least enclose the repolib package building inside a conditional, or drop it. About maven, are you missing the installation of the pom file? (is maven used at all in building?). Other notes: - change %define-s with %global-s - you are missing BuildRequire: java-devel and Require: java - better use name and version macros in Source0 - is there a reason why you dont run junit tests? - -repolib subpackage should not own %{_javadir}/repository.jboss.com , but %{repodir}
ping?
Growl, dammit, sorry -- will get to this asap
AFAIK, jboss is moving away of repolib and because of this repolib packages should not enter Fedora.
Sorry about that -- here's a new version. Changes: - Remove jboss stuff - Remove maven depmap stuff -- it doesn't seem to provide a POM - Run tests as part of build - Make javadoc package noarch Spec URL: http://www.macs.hw.ac.uk/~mef3/review/trove4j.spec SRPM URL: http://www.macs.hw.ac.uk/~mef3/review/trove4j-2.1.0-3.fc12.src.rpm
NEEDSWORK - The package MUST successfully compile and build koji build: http://koji.fedoraproject.org/koji/taskinfo?taskID=2033734 The build failed during junit tests. Please find the cause of the problem, and eventually skip junit tests in case it can be ignored. OK - rpmlint output: 1 packages and 1 specfiles checked; 0 errors, 4 warnings. trove4j.src: W: spelling-error %description -l en_US util -> til, until, u til trove4j.src: W: spelling-error %description -l en_US pluggable -> plug gable, plug-gable, plugged trove4j.src: W: spelling-error %description -l en_US lang -> Lang, lag, slang - Can ignore those. trove4j.src:139: W: libdir-macro-in-noarch-package (main package) %attr(-,root,root) %{_libdir}/gcj/%{name} - This one too (its inside %if %{with_gcj} conditional) OK - The package must be named according to the Package Naming Guidelines (discussion about naming in bug 504891). OK - The spec file name must match the base package %{name} OK - The package must meet the Packaging Guidelines (Java: good - GCJ: good) 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 package must be licensed with a Fedora approved license and meet the Licensing Guidelines (license is LGPLv2+ and MIT) OK - Every binary RPM package which stores shared library files must call ldconfig in %post and %postun 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. 09375a0b74eb8560270331239d2f94c3 trove-2.1.0.tar.gz NA - The spec file MUST handle locales properly NA - package not relocatable OK - A package must own all directories that it creates 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 OK - Each package must have a %clean section OK - Each package must consistently use macros NA - The package must contain code, or permissable content (no content) OK - Large documentation files must go in a -doc subpackage (-javadoc package) OK - If a package includes something as %doc, it must not affect the runtime of the application NA - Header files must be in a -devel package NA - Static libraries must be in a -static package (no static package) NA - Packages containing pkgconfig(.pc) files must 'Requires: pkgconfig' OK - Packages must NOT contain any .la libtool archives NA - Packages containing GUI applications MUST include a .desktop file OK - No file conflicts with other packages and no general names. OK - At the beginning of %install, each package MUST run rm -rf %{buildroot} OK - All filenames in rpm packages must be valid UTF-8 OK - The package does not yet exist in Fedora. The Review Request is not a duplicate. OK - %{?dist} tag is used in release ADDITIONAL NOTE: Looking at Java Guidelines, it seems that specifying Require: java version is mandatory, while it is optional for BuildRequires. BuildRequires: java-devel [>= specific_version] BuildRequires: jpackage-utils Requires: java >= specific_version Requires: jpackage-utils I think its safe for this package, so ill leave up to you whether to fix it or not.
Please consider removing the gcj part. It's stupid to force every user of the package to install gcj even if he is using openjdk.
I've removed the gcj stuff and explicitly BuildRequire'd openjdk -- trove seems to fail its own tests with gcj (?) Updated stuff at: http://www.macs.hw.ac.uk/~mef3/review/gnu-trove.spec http://www.macs.hw.ac.uk/~mef3/review/gnu-trove-2.1.0-4.fc12.src.rpm Sorry for the delay
Sorry, make that http://www.macs.hw.ac.uk/~mef3/review/trove4j.spec http://www.macs.hw.ac.uk/~mef3/review/trove4j-2.1.0-4.fc12.src.rpm
Thank you very much; koji build: http://koji.fedoraproject.org/koji/taskinfo?taskID=2058059 Package APPROVED.
New Package CVS Request ======================= Package Name: trove4j Short Description: High performance collections for Java Owners: mef Branches: F-12 F-13
CVS done (by process-cvs-requests.py).
Mary, are you putting this one in rawhide anytime soon?
trove4j-2.1.0-4.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/trove4j-2.1.0-4.fc13
trove4j-2.1.0-4.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/trove4j-2.1.0-4.fc12
Sorry about the delay :(
trove4j-2.1.0-4.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update trove4j'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/trove4j-2.1.0-4.fc12
trove4j-2.1.0-4.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update trove4j'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/trove4j-2.1.0-4.fc13
trove4j-2.1.0-4.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
trove4j-2.1.0-4.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.