Bug 1766375 - Review Request: python-timeunit - python port of java.util.concurrent.TimeUnit
Summary: Review Request: python-timeunit - python port of java.util.concurrent.TimeUnit
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Neal Gompa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-28 21:04 UTC by David McCheyne
Modified: 2019-11-14 03:40 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-11-13 17:56:44 UTC
Type: ---
Embargoed:
ngompa13: fedora-review+


Attachments (Terms of Use)

Description David McCheyne 2019-10-28 21:04:42 UTC
Spec URL: https://copr-be.cloud.fedoraproject.org/results/dmccheyne/TimeUnit/fedora-rawhide-x86_64/01081300-python-timeunit/python-timeunit.spec

SRPM URL: https://copr-be.cloud.fedoraproject.org/results/dmccheyne/TimeUnit/fedora-rawhide-x86_64/01081300-python-timeunit/python-timeunit-1.1.0-1.fc32.src.rpm

Description: Based on java.util.concurrent.TimeUnit and timeunit in npm
TimeUnit is a port of the public domain TimeUnit Java class by Doug Lea
This class is the basis for java.util.concurrent.TimeUnit from JavaSE.

A timeunit represents time durations at a given unit of granularity and
provides utility methods to convert across units, and to perform delay
operations in these units. A timeunit does not maintain time information,
but only helps organize and use time representations that may be maintained
separately across various contexts.

A timeunit is mainly used to inform time-based methods how a given timing
parameter should be interpreted. 

Fedora Account System Username: dmccheyne


This is my first package, so I'm in need of a sponsor. I recently started a new job with a company that pushes a lot of things back out to the community, so my teammate suggested this as a fairly simple first package to get to know the community and the process. Cheers!

Comment 1 Chris Caron 2019-10-30 00:53:12 UTC
Looks good! My only comments/questions for you are:

- Consider separating the License into it's own file and not just a copy and
  paste of the README.md file.
- Your GitHub page identifies you as having 98% test coverage; can you
  add a %check section and run the same unit tests there as well?


Package Review
==============

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


===== 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]: License field in the package spec file matches the actual license.
[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.
[-]: 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]: 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]: 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]: 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 must not depend on deprecated() packages.
[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

Python:
[x]: Python eggs must not download any dependencies during the build
     process.
[-]: A package which is used by another package via an egg interface should
     provide egg info.
[x]: Package meets the Packaging Guidelines::Python
[x]: Package contains BR: python2-devel or python3-devel
[x]: Packages MUST NOT have dependencies (either build-time or runtime) on
     packages named with the unversioned python- prefix unless no properly
     versioned package exists. Dependencies on Python packages instead MUST
     use names beginning with python2- or python3- as appropriate.
[x]: Python packages must not contain %{pythonX_site(lib|arch)}/* in %files
[x]: Binary eggs must be removed in %prep

===== 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.
[x]: Final provides and requires are sane (see attachments).
[?]: Package functions as described.
[x]: Latest version is packaged.
[x]: Package does not include license text files separate from upstream.
[-]: Sources are verified with gpgverify first in %prep if upstream
     publishes signatures.
     Note: gpgverify is not used.
[-]: Description and summary sections in the package spec file contains
     translations for supported Non-English languages, if available.
[-]: 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.

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

Generic:
[x]: Rpmlint is run on all installed packages.
     Note: There are rpmlint messages (see attachment).
[x]: Spec file according to URL is the same as in SRPM.


Rpmlint
-------
Checking: python3-timeunit-1.1.0-1.fc31.noarch.rpm
          python-timeunit-1.1.0-1.fc31.src.rpm
python3-timeunit.noarch: W: spelling-error %description -l en_US npm -> pm, rpm, ppm
python3-timeunit.noarch: W: spelling-error %description -l en_US durations -> duration, duration's, duration s
python-timeunit.src: W: spelling-error %description -l en_US npm -> pm, rpm, ppm
python-timeunit.src: W: spelling-error %description -l en_US durations -> duration, duration's, duration s
2 packages and 0 specfiles checked; 0 errors, 4 warnings.

Comment 2 David McCheyne 2019-10-30 12:33:51 UTC
Thanks for the feedback! I'll include those additions. Cheers!

Comment 3 David McCheyne 2019-11-02 02:11:55 UTC
Updated SPEC: https://copr-be.cloud.fedoraproject.org/results/dmccheyne/TimeUnit/fedora-rawhide-x86_64/01082126-python-timeunit/python-timeunit.spec
Updated SRPM: https://copr-be.cloud.fedoraproject.org/results/dmccheyne/TimeUnit/fedora-rawhide-x86_64/01082126-python-timeunit/python-timeunit-1.1.0-1.fc32.src.rpm

Updated to split the README and LICENSE md's.

The tests aren't actually in the upstream pypi package and the github isn't tagged but I'll see about sending a PR.

Comment 4 Chris Caron 2019-11-02 22:20:56 UTC
Don't worry than; it was just a suggestion! Your justification is fine!

Review is good. Thanks for updating the README/LICENSE

Comment 5 Neal Gompa 2019-11-03 01:36:29 UTC
I'll sponsor this packager into the Fedora Packagers group.

Comment 6 Neal Gompa 2019-11-03 01:39:10 UTC
@David, you have now been sponsored into the packagers group. You may now proceed with the next step for getting your package into Fedora. :)

Comment 7 Neal Gompa 2019-11-04 18:08:45 UTC
Blech, let's fix this for fedscm...

Comment 8 Neal Gompa 2019-11-04 18:09:06 UTC
PACKAGE APPROVED (again...).

Comment 9 Gwyn Ciesla 2019-11-04 19:16:36 UTC
(fedscm-admin):  The Pagure repository was created at https://src.fedoraproject.org/rpms/python-timeunit

Comment 10 Fedora Update System 2019-11-05 12:25:29 UTC
FEDORA-2019-0c7c133b67 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-0c7c133b67

Comment 11 Fedora Update System 2019-11-05 12:29:10 UTC
FEDORA-2019-796e1da0a8 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-796e1da0a8

Comment 12 Fedora Update System 2019-11-05 12:29:44 UTC
FEDORA-2019-a1299f4980 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-a1299f4980

Comment 13 Fedora Update System 2019-11-06 14:03:30 UTC
python-timeunit-1.1.0-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-796e1da0a8

Comment 14 Fedora Update System 2019-11-06 14:13:15 UTC
python-timeunit-1.1.0-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-0c7c133b67

Comment 15 Fedora Update System 2019-11-06 16:11:27 UTC
python-timeunit-1.1.0-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-a1299f4980

Comment 16 Fedora Update System 2019-11-13 17:56:44 UTC
python-timeunit-1.1.0-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Comment 17 Fedora Update System 2019-11-14 01:12:15 UTC
python-timeunit-1.1.0-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.

Comment 18 Fedora Update System 2019-11-14 03:40:16 UTC
python-timeunit-1.1.0-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.


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