[Bug 1215762] Review Request: py4j - Py4J enables Python programs to dynamically access arbitrary Java objects (for Python 2 and 3)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=1215762



--- Comment #28 from gil cattaneo <puntogil@xxxxxxxxx> ---
Package Review
==============

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


Issues:
=======
- POM files have correct Maven mapping
  Note: Old style Maven package found, no add_maven_depmap calls found but POM
  files present
  See: https://fedoraproject.org/wiki/Packaging:Java#add_maven_depmap_macro
 IGNORE already done
- Maven packages should use new style packaging
  Note: If possible update your package to latest guidelines
  See: https://fedoraproject.org/wiki/Packaging:Java#Apache_Maven
 IGNORE already done
- 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.
  Note: Cannot find LICENSE.txt in rpm(s)
  See:
  http://fedoraproject.org/wiki/Packaging/LicensingGuidelines#License_Text
 IGNORE already done


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

Generic:
[x]: Package successfully compiles and builds into binary rpms on at least one
     supported primary architecture.
     Note: Using prebuilt packages
[x]: Package is licensed with an open-source compatible license and meets
     other legal requirements as defined in the legal section of Packaging
     Guidelines.
[ ]: License field in the package spec file matches the actual license.
     Note: Checking patched sources after %prep for licenses. Licenses found:
     "BSD (3 clause)", "Unknown or generated". 50 files have unknown license.
     Detailed output of licensecheck in /home/gil/1215762-py4j/review-
     py4j/licensecheck.txt

py4j-9a8ab938b4024af8f0455edb54f80fdb5195968b/py4j-java/src/py4j/commands/ExceptionCommand.java
 py4j-9a8ab938b4024af8f0455edb54f80fdb5195968b/py4j-python/setup.py
 py4j-9a8ab938b4024af8f0455edb54f80fdb5195968b/py4j-python/src/py4j/compat.py

py4j-9a8ab938b4024af8f0455edb54f80fdb5195968b/py4j-python/src/py4j/finalizer.py

py4j-9a8ab938b4024af8f0455edb54f80fdb5195968b/py4j-python/src/py4j/java_collections.py

py4j-9a8ab938b4024af8f0455edb54f80fdb5195968b/py4j-python/src/py4j/java_gateway.py
 py4j-9a8ab938b4024af8f0455edb54f80fdb5195968b/py4j-python/src/py4j/protocol.py
 py4j-9a8ab938b4024af8f0455edb54f80fdb5195968b/py4j-python/src/py4j/version.py
[x]: License file installed when any subpackage combination is installed.
[x]: Package requires other packages for directories it uses.
     Note: No known owner of /usr/lib/python3.4/site-packages,
     /usr/share/licenses, /usr/share/maven-metadata, /usr/lib/python3.4
[x]: Package must own all directories that it creates.
     Note: Directories without known owners: /usr/lib/python3.4/site-packages,
     /usr/share/licenses, /usr/share/maven-metadata, /usr/lib/python3.4
[x]: All build dependencies are listed in BuildRequires, except for any that
     are listed in the exceptions section of Packaging Guidelines.
     Note: Using prebuilt rpms.
[?]: Package contains no bundled libraries without FPC exception.
 py4j-9a8ab938b4024af8f0455edb54f80fdb5195968b/py4j-java/src/py4j/Base64.java
[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.
[-]: 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 30720 bytes in 6 files.
[x]: Package complies to the Packaging Guidelines
[x]: Package installs properly.
[x]: Rpmlint is run on all rpms the build produces.
     Note: There are rpmlint messages (see attachment).
[x]: Package does not own files or directories owned by other packages.
[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]: 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 do not use a name that already exist
[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
[x]: Javadoc documentation files are generated and included in -javadoc
     subpackage
[x]: Javadoc subpackages should not have Requires: jpackage-utils
[x]: Javadocs are placed in %{_javadocdir}/%{name} (no -%{version} symlink)

Maven:
[!]: If package contains pom.xml files install it (including depmaps) even
     when building with ant
[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 %{_mavenpomdir} instead of %{_datadir}/maven2/poms

Python:
[x]: Python eggs must not download any dependencies during the build process.
[x]: A package which is used by another package via an egg interface should
     provide egg info.
[?]: Package meets the Packaging Guidelines::Python
[x]: Package contains BR: python2-devel or python3-devel
[x]: Binary eggs must be removed in %prep

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

Generic:
[!]: Reviewer should test that the package builds in mock.
[!]: Uses parallel make %{?_smp_mflags} macro.
[-]: 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).
[-]: Fully versioned dependency in subpackages if applicable.
     Note: No Requires: %{name}%{?_isa} = %{version}-%{release} in
     python3-py4j , py4j-java , py4j-javadoc , py4j-doc
[x]: Package functions as described.
[x]: Latest version is packaged.
[x]: Package does not include license text files separate from upstream.
[x]: Patches link to upstream bugs/comments/lists or are otherwise justified.
[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.
[x]: %check is present and all tests pass.
[x]: Packages should try to preserve timestamps of original installed files.
[x]: Packager, Vendor, PreReq, Copyright tags should not be in spec file
[x]: Sources can be downloaded from URI in Source: tag
[x]: Buildroot is not present
[x]: Package has no %clean section with rm -rf %{buildroot} (or
     $RPM_BUILD_ROOT)
[x]: Dist tag is present (not strictly required in GL).
[x]: No file requires outside of /etc, /bin, /sbin, /usr/bin, /usr/sbin.
[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:
[!]: Spec file according to URL is the same as in SRPM.
     Note: Spec file as given by url is not the same as in SRPM (see attached
     diff).
     See: (this test has no URL)
[x]: Rpmlint is run on all installed packages.
     Note: There are rpmlint messages (see attachment).


Rpmlint
-------
Checking: py4j-0.9-0.1.pre.20141101git9a8ab93.fc23.noarch.rpm
          python3-py4j-0.9-0.1.pre.20141101git9a8ab93.fc23.noarch.rpm
          py4j-java-0.9-0.1.pre.20141101git9a8ab93.fc23.noarch.rpm
          py4j-javadoc-0.9-0.1.pre.20141101git9a8ab93.fc23.noarch.rpm
          py4j-doc-0.9-0.1.pre.20141101git9a8ab93.fc23.noarch.rpm
          py4j-0.9-0.1.pre.20141101git9a8ab93.fc23.src.rpm
py4j.noarch: W: name-repeated-in-summary C Py4J
py4j.noarch: W: invalid-url URL: https://py4j.sf.net <urlopen error [Errno 111]
Connection refused>
python3-py4j.noarch: W: invalid-url URL: https://py4j.sf.net <urlopen error
[Errno 111] Connection refused>
py4j-java.noarch: W: invalid-url URL: https://py4j.sf.net <urlopen error [Errno
111] Connection refused>
py4j-java.noarch: W: dangling-relative-symlink /usr/share/py4j/*.jar
%{javadir}/py4j/*.jar
py4j-javadoc.noarch: W: invalid-url URL: https://py4j.sf.net <urlopen error
[Errno 111] Connection refused>
py4j-doc.noarch: W: invalid-url URL: https://py4j.sf.net <urlopen error [Errno
111] Connection refused>
py4j-doc.noarch: W: hidden-file-or-dir /usr/share/doc/py4j-doc/html/.buildinfo
py4j-doc.noarch: W: wrong-file-end-of-line-encoding
/usr/share/doc/py4j-doc/html/_static/jquery.js
py4j.src: W: name-repeated-in-summary C Py4J
py4j.src: W: invalid-url URL: https://py4j.sf.net <urlopen error [Errno 111]
Connection refused>
6 packages and 0 specfiles checked; 0 errors, 11 warnings.




Rpmlint (installed packages)
----------------------------
Cannot parse rpmlint output:


Diff spec file in url and in SRPM
---------------------------------
--- /home/gil/1215762-py4j/py4j.spec    2015-04-30 23:39:00.000000000 +0200
+++ /home/gil/1215762-py4j/review-py4j/srpm-unpacked/py4j.spec    2015-04-30
23:33:32.000000000 +0200
@@ -1,4 +1,6 @@
 %global commit 9a8ab938b4024af8f0455edb54f80fdb5195968b
 %global date   20141101
+# this is a pre-release of upstream
+%global pre    pre

 # python3 for Fedora only (not available at EPEL)
@@ -9,5 +11,5 @@
 Name:           py4j
 Version:        0.9
-Release:        0.1.pre.%{date}git%(c=%{commit}; echo ${c:0:7})%{?dist}
+Release:        0.1.%{pre}.%{date}git%(c=%{commit}; echo ${c:0:7})%{?dist}
 Summary:        Py4J enables Python programs to dynamically access arbitrary
Java objects



Requires
--------
py4j-java (rpmlib, GLIBC filtered):
    java-headless
    jpackage-utils

py4j-doc (rpmlib, GLIBC filtered):

py4j (rpmlib, GLIBC filtered):
    py4j-java
    python(abi)
    python-sphinx

python3-py4j (rpmlib, GLIBC filtered):
    py4j-java
    python(abi)
    python3

py4j-javadoc (rpmlib, GLIBC filtered):
    jpackage-utils



Provides
--------
py4j-java:
    mvn(net.sf.py4j:py4j)
    mvn(net.sf.py4j:py4j:pom:)
    py4j-java

py4j-doc:
    py4j-doc

py4j:
    py4j

python3-py4j:
    python3-py4j

py4j-javadoc:
    py4j-javadoc



Source checksums
----------------
https://github.com/bartdag/py4j/archive/9a8ab938b4024af8f0455edb54f80fdb5195968b/9a8ab938b4024af8f0455edb54f80fdb5195968b.tar.gz#/py4j-9a8ab938b4024af8f0455edb54f80fdb5195968b.tar.gz
:
  CHECKSUM(SHA256) this package     :
863e23cbfc2e2d3d51c2ef76d39d6555f07612c39e8bc49a5675ed458d331f72
  CHECKSUM(SHA256) upstream package :
863e23cbfc2e2d3d51c2ef76d39d6555f07612c39e8bc49a5675ed458d331f72


Generated by fedora-review 0.5.2 (63c24cb) last change: 2014-07-14
Command line :/usr/bin/fedora-review -vpn py4j -m fedora-rawhide-i386
Buildroot used: fedora-rawhide-i386
Active plugins: Python, Shell-api, Generic, Java
Disabled plugins: C/C++, SugarActivity, fonts, Haskell, Ocaml, Perl, R, PHP,
Ruby
Disabled flags: EXARCH, EPEL5, BATCH, DISTTAG

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list
package-review@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/package-review





[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]