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=700537 Andrew Overholt <overh...@redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|nob...@fedoraproject.org |overh...@redhat.com Flag| |fedora-review? --- Comment #1 from Andrew Overholt <overh...@redhat.com> 2011-04-28 15:05:54 EDT --- Package Review ============== Key: - = N/A x = Check ! = Problem ? = Not evaluated === REQUIRED ITEMS === [x] Rpmlint output: eclipse-mylyn-builds.src:93: W: macro-in-comment %{buildroot} (this isn't used in the .spec above but *is* in the SRPM) eclipse-mylyn-builds.src:93: W: macro-in-comment %{install_loc} (this isn't used in the .spec above but *is* in the SRPM) eclipse-mylyn-builds.src:95: W: macro-in-comment %{_javadir} (this isn't used in the .spec above but *is* in the SRPM) eclipse-mylyn-builds.src: W: invalid-url Source0: eclipse-mylyn-builds-R_3_5_0-fetched-src.tar.bz2 1 packages and 0 specfiles checked; 0 errors, 4 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 (tested on x86_64 F15/rawhide) [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: EPL [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. - replace "eclips" with "eclipse" to make it a bit more readable [-] 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 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. [-] Javadoc documentation files are generated and included in -javadoc subpackage [-] Javadocs are placed in %{_javadocdir}/%{name} (no -%{version} symlinks) [-] Packages have proper BuildRequires/Requires on jpackage-utils [-] 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, ...) - I generated the exact same tarball using the provided shell script [x] If source tarball includes bundled jar/class files these need to be removed prior to building - one JAR used for testing so this is okay [x] All filenames in rpm packages must be valid UTF-8. [-] Jar files are installed to %{_javadir}/%{name}.jar (see [6] for details) [-] If package contains pom.xml files install it (including depmaps) even when building with ant === Other suggestions === [-] 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) [!] Latest version is packaged. - I think 3.5.1 is out === Issues === 1. why is ws-jaxme a BR but not an R? 2. perhaps have Requires: java >= 1:1.6.0 to ensure 1.6-level JVM is used? 3. please include a link to a .spec that matches that which was used to create the SRPM 4. have you run the patch by upstream (the 1.6 part)? -- 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@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/package-review