Bug 1649570 - Review Request: ee4j-parent - Parent POM file for Eclipse Enterprise for Java projects
Summary: Review Request: ee4j-parent - Parent POM file for Eclipse Enterprise for Java...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jie Kang
QA Contact: Fedora Extras Quality Assurance
URL: https://github.com/eclipse-ee4j/ee4j
Whiteboard:
Depends On:
Blocks: 1649574 1649575
TreeView+ depends on / blocked
 
Reported: 2018-11-13 21:49 UTC by Salman Siddiqui
Modified: 2018-11-22 14:50 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-11-21 22:04:34 UTC
Type: ---
Embargoed:
jkang: fedora-review+


Attachments (Terms of Use)
rpmlint - SPEC (58 bytes, text/plain)
2018-11-13 21:53 UTC, Salman Siddiqui
no flags Details
rpmlint - SRPM (95 bytes, text/plain)
2018-11-13 21:54 UTC, Salman Siddiqui
no flags Details
rpmlint - RPM (98 bytes, text/plain)
2018-11-13 21:56 UTC, Salman Siddiqui
no flags Details

Description Salman Siddiqui 2018-11-13 21:49:58 UTC
Spec URL: https://pagure.io/jmc-rpm/blob/master/f/ee4j/ee4j.spec
SRPM URL: https://copr-be.cloud.fedoraproject.org/results/sasiddiq/jmc/fedora-29-x86_64/00823515-ee4j/ee4j-1.0.1-1.fc29.src.rpm

Description: Just submitted my first package. I am seeking a sponsor.
Eclipse Enterprise for Java (EE4J) is an open source initiative to create 
standard APIs, implementations of those APIs, and technology compatibility kits
for Java run-times that enable development, deployment, and management of 
server-side and cloud-native applications.

Fedora Account System Username: sasiddiq
Successful Copr Build: https://copr.fedorainfracloud.org/coprs/sasiddiq/jmc/build/823515/

Comment 1 Salman Siddiqui 2018-11-13 21:53:00 UTC
Created attachment 1505451 [details]
rpmlint - SPEC

Comment 2 Salman Siddiqui 2018-11-13 21:54:34 UTC
Created attachment 1505452 [details]
rpmlint - SRPM

Comment 3 Salman Siddiqui 2018-11-13 21:56:09 UTC
Created attachment 1505453 [details]
rpmlint - RPM

Comment 4 Jie Kang 2018-11-15 15:50:32 UTC
ee4j Package Review 1
==============

Legend:
[x] = Pass, [!] = Fail, [-] = Not applicable, [?] = Not evaluated


Issues:
=======
- Java API documentation MUST be placed into a sub-package called %{name}-javadoc.
- Javadocs are placed in %{_javadocdir}/%{name} (no -%{version} symlink)
  Note: No javadoc subpackage present
  See: https://fedoraproject.org/wiki/Packaging:Java#Javadoc_installation
- Javadoc documentation files are generated and included in -javadoc
  subpackage
  Note: No javadoc subpackage present. Note: Javadocs are optional for
  Fedora versions >= 21
  See: https://fedoraproject.org/wiki/Packaging:Java#Javadoc_installation



===== MUST items =====

Generic:
[!]: Package is licensed with an open-source compatible license and meets
     other legal requirements as defined in the legal section of Packaging
     Guidelines.

     Note:
     The project is dual licensed under EPL-2.0 OR GPL-2.0 WITH
     Classpath-exception-2.0. See e.g. contents of pom @
     https://github.com/eclipse-ee4j/ee4j/blob/master/parent/pom.xml

[-]: 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 %license.
[!]: License field in the package spec file matches the actual license.
     Note: Checking patched sources after %prep for licenses. Licenses
     found: "EPL (v2.0)", "Unknown or generated". 1 files have unknown
     license. Detailed output of licensecheck in /home/jkang/Work/fedora-
     reviews/ee4j/licensecheck.txt
[x]: Package contains no bundled libraries without FPC exception.
[x]: Changelog in prescribed format.
[x]: Sources contain only permissible code or content.
[-]: Package contains desktop file if it is a GUI application.
[-]: Development files must be in a -devel package
[x]: Package uses nothing in %doc for runtime.
[x]: Package consistently uses macros (instead of hard-coded directory
     names).
[x]: Package is named according to the Package Naming Guidelines.
[x]: Package does not generate any conflict.
[x]: Package obeys FHS, except libexecdir and /usr/target.
[-]: If the package is a rename of another package, proper Obsoletes and
     Provides are present.
[x]: Requires correct, justified where necessary.
[x]: Spec file is legible and written in American English.
[-]: Package contains systemd file(s) if in need.
[x]: Package is not known to require an ExcludeArch tag.
[-]: Large documentation must go in a -doc subpackage. Large could be size
     (~1MB) or number of files.
     Note: Documentation size is 10240 bytes in 1 files.
[x]: Package complies to the Packaging Guidelines
[x]: Package successfully compiles and builds into binary rpms on at least
     one supported primary architecture.
[x]: Package installs properly.
[x]: Rpmlint is run on all rpms the build produces.
     Note: There are rpmlint messages (see attachment).
[x]: Package requires other packages for directories it uses.
[x]: Package must own all directories that it creates.
[x]: Package does not own files or directories owned by other packages.
[x]: All build dependencies are listed in BuildRequires, except for any
     that are listed in the exceptions section of Packaging Guidelines.
[x]: Package uses either %{buildroot} or $RPM_BUILD_ROOT
[x]: Package does not run rm -rf %{buildroot} (or $RPM_BUILD_ROOT) at the
     beginning of %install.
[x]: Macros in Summary, %description expandable at SRPM build time.
[x]: Dist tag is present.
[x]: Package does not contain duplicates in %files.
[x]: Permissions on files are set properly.
[x]: Package use %makeinstall only when make install DESTDIR=... doesn't
     work.
[x]: Package is named using only allowed ASCII characters.
[x]: Package does not use a name that already exists.
[x]: Package is not relocatable.
[x]: Sources used to build the package match the upstream source, as
     provided in the spec URL.
[x]: Spec file name must match the spec package %{name}, in the format
     %{name}.spec.
[x]: File names are valid UTF-8.
[x]: Packages must not store files under /srv, /opt or /usr/local

Java:
[x]: Bundled jar/class files should be removed before build
[x]: Packages have proper BuildRequires/Requires on jpackage-utils
     Note: Maven packages do not need to (Build)Require jpackage-utils. It
     is pulled in by maven-local

Maven:
[x]: If package contains pom.xml files install it (including metadata) even
     when building with ant
[x]: POM files have correct Maven mapping
[x]: Maven packages should use new style packaging
[x]: Old add_to_maven_depmap macro is not being used
[x]: Packages DO NOT have Requires(post) and Requires(postun) on jpackage-
     utils for %update_maven_depmap macro
[x]: Package DOES NOT use %update_maven_depmap in %post/%postun
[x]: Packages use .mfiles file list instead of %{_datadir}/maven2/poms

===== SHOULD items =====

Generic:
[!]: If the source package does not include license text(s) as a separate
     file from upstream, the packager SHOULD query upstream to include it.
     
     Note:
     An issue can be opened on the GitHub project
[x]: Final provides and requires are sane (see attachments).
[x]: Package functions as described.
[x]: Latest version is packaged.
[x]: Package does not include license text files separate from upstream.
[-]: Description and summary sections in the package spec file contains
     translations for supported Non-English languages, if available.
[x]: Package should compile and build into binary rpms on all supported
     architectures.
[-]: %check is present and all tests pass.
[x]: Packages should try to preserve timestamps of original installed
     files.
[x]: Reviewer should test that the package builds in mock.
[x]: Buildroot is not present
[x]: Package has no %clean section with rm -rf %{buildroot} (or
     $RPM_BUILD_ROOT)
[x]: No file requires outside of /etc, /bin, /sbin, /usr/bin, /usr/sbin.
[x]: Packager, Vendor, PreReq, Copyright tags should not be in spec file
[x]: Sources can be downloaded from URI in Source: tag
[x]: SourceX is a working URL.
[x]: Spec use %global instead of %define unless justified.

Java:
[x]: Package uses upstream build method (ant/maven/etc.)
[x]: Packages are noarch unless they use JNI

===== EXTRA items =====

Generic:
[x]: Rpmlint is run on all installed packages.
     Note: There are rpmlint messages (see attachment).


Rpmlint
-------
Checking: ee4j-1.0.1-1.fc28.noarch.rpm
          ee4j-1.0.1-1.fc28.src.rpm
ee4j.noarch: W: invalid-license EPL-2.0
ee4j.src: W: invalid-license EPL-2.0
2 packages and 0 specfiles checked; 0 errors, 2 warnings.

Note: These warnings can be ignored.


Rpmlint (installed packages)
----------------------------
sh: /usr/bin/python: No such file or directory
ee4j.noarch: W: invalid-license EPL-2.0
ee4j.noarch: W: invalid-url URL: https://github.com/eclipse-ee4j/ee4j <urlopen error [Errno -2] Name or service not known>
1 packages and 0 specfiles checked; 0 errors, 2 warnings.

Note: These warnings can be ignored


Requires
--------
ee4j (rpmlib, GLIBC filtered):
    java-headless
    javapackages-tools



Provides
--------
ee4j:
    ee4j
    mvn(org.eclipse.ee4j:project:pom:)



Source checksums
----------------
https://github.com/eclipse-ee4j/ee4j/archive/1.0.1.tar.gz :
  CHECKSUM(SHA256) this package     : 68c81c8e2f51b986dbbd0be12bcb1a4366c20bd7cc1cbdce103cdf9216550dfa
  CHECKSUM(SHA256) upstream package : 68c81c8e2f51b986dbbd0be12bcb1a4366c20bd7cc1cbdce103cdf9216550dfa


Generated by fedora-review 0.6.1 (f03e4e7) last change: 2016-05-02
Command line :/usr/bin/fedora-review --rpm-spec -n ./ee4j-1.0.1-1.fc29.src.rpm
Buildroot used: fedora-28-x86_64
Active plugins: Generic, Shell-api, Java
Disabled plugins: C/C++, Python, fonts, SugarActivity, Ocaml, Perl, Haskell, R, PHP
Disabled flags: EXARCH, DISTTAG, EPEL5, BATCH, EPEL6

Comment 6 Severin Gehwolf 2018-11-16 10:34:04 UTC
I think we should consider naming this pom-only package 'ee4j-parent' or some such. That would be following the 'apache-parent'[1] model. It would also make it clearer that it's a parent pom. Thoughts?

[1] https://koji.fedoraproject.org/koji/buildinfo?buildID=1106161

Comment 7 Severin Gehwolf 2018-11-16 10:43:33 UTC
Rawhide build: https://koji.fedoraproject.org/koji/taskinfo?taskID=30920022

Comment 8 Jie Kang 2018-11-16 13:43:55 UTC
I agree with the name 'ee4j-parent'. Thanks for the suggestion!

Comment 10 Jie Kang 2018-11-19 15:17:05 UTC
ee4j-parent Package Review 1
============================

Legend:
[x] = Pass, [!] = Fail, [-] = Not applicable, [?] = Not evaluated

===== MUST items =====

Generic:
[x]: Package is licensed with an open-source compatible license and meets
     other legal requirements as defined in the legal section of Packaging
     Guidelines.
[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 %license.
[x]: License field in the package spec file matches the actual license.
     Note: Checking patched sources after %prep for licenses. Licenses
     found: "EPL (v2.0)", "Unknown or generated". 1 files have unknown
     license. Detailed output of licensecheck in /home/jkang/Work/fedora-
     reviews/ee4j-parent/licensecheck.txt
[x]: If the package is under multiple licenses, the licensing breakdown
     must be documented in the spec.
[x]: Package contains no bundled libraries without FPC exception.
[x]: Changelog in prescribed format.
[x]: Sources contain only permissible code or content.
[-]: Package contains desktop file if it is a GUI application.
[-]: Development files must be in a -devel package
[x]: Package uses nothing in %doc for runtime.
[x]: Package consistently uses macros (instead of hard-coded directory
     names).
[x]: Package is named according to the Package Naming Guidelines.
[x]: Package does not generate any conflict.
[x]: Package obeys FHS, except libexecdir and /usr/target.
[-]: If the package is a rename of another package, proper Obsoletes and
     Provides are present.
[x]: Requires correct, justified where necessary.
[x]: Spec file is legible and written in American English.
[-]: Package contains systemd file(s) if in need.
[x]: Package is not known to require an ExcludeArch tag.
[x]: Large documentation must go in a -doc subpackage. Large could be size
     (~1MB) or number of files.
     Note: Documentation size is 10240 bytes in 1 files.
[x]: Package complies to the Packaging Guidelines
[x]: Package successfully compiles and builds into binary rpms on at least
     one supported primary architecture.
[x]: Package installs properly.
[x]: Rpmlint is run on all rpms the build produces.
     Note: There are rpmlint messages (see attachment).
[x]: Package requires other packages for directories it uses.
[x]: Package must own all directories that it creates.
[x]: Package does not own files or directories owned by other packages.
[x]: All build dependencies are listed in BuildRequires, except for any
     that are listed in the exceptions section of Packaging Guidelines.
[x]: Package uses either %{buildroot} or $RPM_BUILD_ROOT
[x]: Package does not run rm -rf %{buildroot} (or $RPM_BUILD_ROOT) at the
     beginning of %install.
[x]: Macros in Summary, %description expandable at SRPM build time.
[x]: Dist tag is present.
[x]: Package does not contain duplicates in %files.
[x]: Permissions on files are set properly.
[x]: Package use %makeinstall only when make install DESTDIR=... doesn't
     work.
[x]: Package is named using only allowed ASCII characters.
[x]: Package does not use a name that already exists.
[x]: Package is not relocatable.
[x]: Sources used to build the package match the upstream source, as
     provided in the spec URL.
[x]: Spec file name must match the spec package %{name}, in the format
     %{name}.spec.
[x]: File names are valid UTF-8.
[x]: Packages must not store files under /srv, /opt or /usr/local

Java:
[x]: Bundled jar/class files should be removed before build
[x]: Packages have proper BuildRequires/Requires on jpackage-utils
     Note: Maven packages do not need to (Build)Require jpackage-utils. It
     is pulled in by maven-local

Maven:
[x]: If package contains pom.xml files install it (including metadata) even
     when building with ant
[x]: POM files have correct Maven mapping
[x]: Maven packages should use new style packaging
[x]: Old add_to_maven_depmap macro is not being used
[x]: Packages DO NOT have Requires(post) and Requires(postun) on jpackage-
     utils for %update_maven_depmap macro
[x]: Package DOES NOT use %update_maven_depmap in %post/%postun
[x]: Packages use .mfiles file list instead of %{_datadir}/maven2/poms

===== SHOULD items =====

Generic:
[x]: If the source package does not include license text(s) as a separate
     file from upstream, the packager SHOULD query upstream to include it.
[x]: Final provides and requires are sane (see attachments).
[x]: Package functions as described.
[x]: Latest version is packaged.
[x]: Package does not include license text files separate from upstream.
[x]: Description and summary sections in the package spec file contains
     translations for supported Non-English languages, if available.
[x]: Package should compile and build into binary rpms on all supported
     architectures.
[-]: %check is present and all tests pass.
[x]: Packages should try to preserve timestamps of original installed
     files.
[x]: Reviewer should test that the package builds in mock.
[x]: Buildroot is not present
[x]: Package has no %clean section with rm -rf %{buildroot} (or
     $RPM_BUILD_ROOT)
[x]: No file requires outside of /etc, /bin, /sbin, /usr/bin, /usr/sbin.
[x]: Packager, Vendor, PreReq, Copyright tags should not be in spec file
[x]: Sources can be downloaded from URI in Source: tag
[x]: SourceX is a working URL.
[x]: Spec use %global instead of %define unless justified.

Java:
[x]: Package uses upstream build method (ant/maven/etc.)
[x]: Packages are noarch unless they use JNI

===== EXTRA items =====

Generic:
[x]: Rpmlint is run on all installed packages.
     Note: There are rpmlint messages (see attachment).

Rpmlint
-------
Checking: ee4j-parent-1.0.1-1.fc28.noarch.rpm
          ee4j-parent-1.0.1-1.fc28.src.rpm
ee4j-parent.noarch: W: invalid-license EPL-2.0
ee4j-parent.src: W: invalid-license EPL-2.0
2 packages and 0 specfiles checked; 0 errors, 2 warnings.

Note: Warnings can be ignored

Rpmlint (installed packages)
----------------------------
sh: /usr/bin/python: No such file or directory
ee4j-parent.noarch: W: invalid-license EPL-2.0
ee4j-parent.noarch: W: invalid-url URL: https://github.com/eclipse-ee4j/ee4j <urlopen error [Errno -2] Name or service not known>
1 packages and 0 specfiles checked; 0 errors, 2 warnings.

Note: Warnings can be ignored

Requires
--------
ee4j-parent (rpmlib, GLIBC filtered):
    java-headless
    javapackages-tools



Provides
--------
ee4j-parent:
    ee4j-parent
    mvn(org.eclipse.ee4j:project:pom:)



Source checksums
----------------
https://github.com/eclipse-ee4j/ee4j/archive/1.0.1.tar.gz :
  CHECKSUM(SHA256) this package     : 68c81c8e2f51b986dbbd0be12bcb1a4366c20bd7cc1cbdce103cdf9216550dfa
  CHECKSUM(SHA256) upstream package : 68c81c8e2f51b986dbbd0be12bcb1a4366c20bd7cc1cbdce103cdf9216550dfa


Generated by fedora-review 0.6.1 (f03e4e7) last change: 2016-05-02
Command line :/usr/bin/fedora-review --rpm-spec -n ./ee4j-parent-1.0.1-1.fc29.src.rpm
Buildroot used: fedora-28-x86_64
Active plugins: Generic, Shell-api, Java
Disabled plugins: C/C++, Python, fonts, SugarActivity, Ocaml, Perl, Haskell, R, PHP
Disabled flags: EXARCH, DISTTAG, EPEL5, BATCH, EPEL6

Comment 11 Gwyn Ciesla 2018-11-21 19:02:58 UTC
(fedscm-admin):  The Pagure repository was created at https://src.fedoraproject.org/rpms/ee4j-parent

Comment 12 Jie Kang 2018-11-21 22:53:34 UTC
https://fedoraproject.org/wiki/Package_Review_Process#Contributor

at the end has:

You should make sure the review ticket is closed. You are welcome to close it once the package has been built on the requested branches, or if you built for one of the Fedora release branches you can ask Bodhi to close the ticket for you when it completes the process. If you close the ticket yourself, use NEXTRELEASE as the resolution.

So I think resolution state should be NEXTRELEASE instead of RAWHIDE


Note You need to log in before you can comment on or make changes to this bug.