Bug 797165
Summary: | Review Request: jboss-el-2.2-api - Expression Language 2.2 API | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Juan Hernández <juan.hernandez> |
Component: | Package Review | Assignee: | Marek Goldmann <mgoldman> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | mgoldman, notting, package-review, rfontana |
Target Milestone: | --- | Flags: | mgoldman:
fedora-review+
gwync: fedora-cvs+ |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | jboss-el-2.2-api-1.0.1-0.2.20120212git2fabd8.fc17 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-03-12 16:50:17 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Juan Hernández
2012-02-24 12:38:54 UTC
License cleanup pull request: https://github.com/jboss/jboss-el-api_spec/pull/1 I think proper license header after it gets pushed will be: "CDDL or GPLv2 with exceptions or ASL 2.0" (In reply to comment #1) > License cleanup pull request: https://github.com/jboss/jboss-el-api_spec/pull/1 > > I think proper license header after it gets pushed will be: "CDDL or GPLv2 with > exceptions or ASL 2.0" Not sure if the upstream cleanup was necessary here, but it seems harmless. I would simply use "CDDL" here for the license tag as in the similarly odd case of BZ# 730232 because of the presence of incorporated Apache code. (Were there no such Apache notices "CDDL or GPLv2 with exceptions" would otherwise make sense.) Please update the package with sources from commit 2fabd8013214d50b03a65853673c111bdf39e87f. Example cleanup: https://bugzilla.redhat.com/show_bug.cgi?id=740799#c4 The updated spec and SRPM are available here: http://jhernand.fedorapeople.org/rpms/jboss-el-2.2-api/1.0.1-0.1.20120212git2fabd8 I'll take it. Package Review ============== Key: - = N/A x = Check ! = Problem ? = Not evaluated === REQUIRED ITEMS === [x] Rpmlint output: $ rpmlint SPECS/jboss-el-2.2-api.spec SPECS/jboss-el-2.2-api.spec: W: invalid-url Source0: jboss-el-2.2-api-1.0.1.20120212git2fabd8.tar.xz 0 packages and 1 specfiles checked; 0 errors, 1 warnings. $ rpmlint SRPMS/jboss-el-2.2-api-1.0.1-0.1.20120212git2fabd8.fc17.src.rpm jboss-el-2.2-api.src: I: enchant-dictionary-not-found en_US jboss-el-2.2-api.src: W: invalid-url URL: http://www.jboss.org HTTP Error 403: Forbidden jboss-el-2.2-api.src: W: invalid-url Source0: jboss-el-2.2-api-1.0.1.20120212git2fabd8.tar.xz 1 packages and 0 specfiles checked; 0 errors, 2 warnings. $ rpmlint RPMS/noarch/jboss-el-2.2-api-1.0.1-0.1.20120212git2fabd8.fc17.noarch.rpm jboss-el-2.2-api.noarch: I: enchant-dictionary-not-found en_US jboss-el-2.2-api.noarch: W: invalid-url URL: http://www.jboss.org HTTP Error 403: Forbidden jboss-el-2.2-api.noarch: W: no-documentation 1 packages and 0 specfiles checked; 0 errors, 2 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: CDDL or GPLv2 with exceptions [!] 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. See #1. [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. MD5SUM this package : 02fbb809576e9698611d5162b85453b1 MD5SUM upstream package: 02fbb809576e9698611d5162b85453b1 [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. [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 [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 [-] 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. Tested on: === Issues === 1. Please add LICENSE and README files to packages, both for main and javadoc. %doc LICENSE README ================ *** APPROVED *** ================ I'm approving this package, but please add the %doc lines at the time of import. New Package SCM Request ======================= Package Name: jboss-el-2.2-api Short Description: Expression Language 2.2 API Owners: jhernand Branches: f17 InitialCC: goldmann Git done (by process-git-requests). jboss-el-2.2-api-1.0.1-0.1.20120212git2fabd8.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/jboss-el-2.2-api-1.0.1-0.1.20120212git2fabd8.fc17 jboss-el-2.2-api-1.0.1-0.2.20120212git2fabd8.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/jboss-el-2.2-api-1.0.1-0.2.20120212git2fabd8.fc17 jboss-el-2.2-api-1.0.1-0.2.20120212git2fabd8.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |