Bug 1830267 - Review Request: python-nanoid - Unique string ID generator for Python
Summary: Review Request: python-nanoid - Unique string ID generator for Python
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Robert-André Mauchin 🐧
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-01 12:11 UTC by Fabian Affolter
Modified: 2020-07-12 00:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-05 01:48:27 UTC
Type: ---
Embargoed:
zebob.m: fedora-review+


Attachments (Terms of Use)

Description Fabian Affolter 2020-05-01 12:11:04 UTC
Spec URL: https://fab.fedorapeople.org/packages/SRPMS/python-nanoid.spec
SRPM URL: https://fab.fedorapeople.org/packages/SRPMS/python-nanoid-2.0.0-1.fc31.src.rpm

Project URL: https://github.com/puyuan/py-nanoid

Description:
Nano ID is a tiny, secure, URL-friendly, unique string ID generator for
Python. It uses cryptographically strong random APIs and tests distribution
of symbols and a larger alphabet than UUID (A-Za-z0-9_-).

Koji scratch build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=43976766

rpmlint output:
$ rpmlint python3-nanoid-2.0.0-1.fc31.noarch.rpm 
python3-nanoid.noarch: W: spelling-error %description -l en_US Nano -> Nona, Nan, Kano
python3-nanoid.noarch: W: spelling-error %description -l en_US cryptographically -> photographically, typographically, topographically
1 packages and 0 specfiles checked; 0 errors, 2 warnings.

$ rpmlint python-nanoid-2.0.0-1.fc31.src.rpm
python-nanoid.src: W: spelling-error %description -l en_US Nano -> Nona, Nan, Kano
python-nanoid.src: W: spelling-error %description -l en_US cryptographically -> photographically, typographically, topographically
1 packages and 0 specfiles checked; 0 errors, 2 warnings.

Fedora Account System Username: fab

Comment 1 Raphael Groner 2020-05-01 17:39:07 UTC
"# License file missing: "
???
Add one-liner: %license LICENSE
https://github.com/puyuan/py-nanoid/blob/master/LICENSE

Otherwise: Did you poke upstream? We're not able to validate MIT without any provided license file. Did not check tarball from pypi, maybe upstream forgot to add the license file? Last commit "2 years ago".

Comment 2 Fabian Affolter 2020-05-01 19:06:15 UTC
My bad. Forgot to add the link to the issue in the spec file: https://github.com/puyuan/py-nanoid/pull/19

Comment 3 Robert-André Mauchin 🐧 2020-06-22 16:18:44 UTC
Meanwhile d/l the license file as a separate source.


Package approved otherwise.


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.
[!]: 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: "Unknown or generated". 10 files have unknown license. Detailed
     output of licensecheck in /home/bob/packaging/review/python-
     nanoid/review-python-nanoid/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 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 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.
[x]: 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.
[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.

===== 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-nanoid-2.0.0-1.fc33.noarch.rpm
          python-nanoid-2.0.0-1.fc33.src.rpm
python3-nanoid.noarch: W: spelling-error %description -l en_US Nano -> Nona, Nan, Kano
python3-nanoid.noarch: W: spelling-error %description -l en_US cryptographically -> photographically, typographically, topographically
python-nanoid.src: W: spelling-error %description -l en_US Nano -> Nona, Nan, Kano
python-nanoid.src: W: spelling-error %description -l en_US cryptographically -> photographically, typographically, topographically
2 packages and 0 specfiles checked; 0 errors, 4 warnings.

Comment 4 Gwyn Ciesla 2020-06-24 14:05:08 UTC
(fedscm-admin):  The Pagure repository was created at https://src.fedoraproject.org/rpms/python-nanoid

Comment 5 Fedora Update System 2020-06-26 07:31:53 UTC
FEDORA-2020-59b7ccb419 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-59b7ccb419

Comment 6 Fedora Update System 2020-06-26 07:36:42 UTC
FEDORA-2020-8eea07b4c0 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-8eea07b4c0

Comment 7 Fedora Update System 2020-06-26 07:41:40 UTC
FEDORA-EPEL-2020-527b710bcb has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-527b710bcb

Comment 8 Fedora Update System 2020-06-27 01:21:00 UTC
FEDORA-2020-8eea07b4c0 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2020-8eea07b4c0 \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8eea07b4c0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2020-06-27 03:12:33 UTC
FEDORA-2020-59b7ccb419 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2020-59b7ccb419 \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-59b7ccb419

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2020-06-27 03:17:24 UTC
FEDORA-EPEL-2020-527b710bcb has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-527b710bcb

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2020-07-05 01:48:27 UTC
FEDORA-2020-8eea07b4c0 has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2020-07-05 02:09:20 UTC
FEDORA-2020-59b7ccb419 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2020-07-12 00:51:26 UTC
FEDORA-EPEL-2020-527b710bcb has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, 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.