Bug 1953226 - Review Request: python-op1svg - Normalize SVG files so that the OP-1 understands them
Summary: Review Request: python-op1svg - Normalize SVG files so that the OP-1 understa...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Beasley
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-24 21:10 UTC by Davide Cavalca
Modified: 2021-05-09 01:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-09 00:51:05 UTC
Type: ---
Embargoed:
code: fedora-review+


Attachments (Terms of Use)
Man page (527 bytes, text/plain)
2021-04-30 11:46 UTC, Ben Beasley
no flags Details

Description Davide Cavalca 2021-04-24 21:10:47 UTC
Spec URL: https://dcavalca.fedorapeople.org/review/python-op1svg/python-op1svg.spec
SRPM URL: https://dcavalca.fedorapeople.org/review/python-op1svg/python-op1svg-0.1.0-1.20210419git50a3b01.fc35.src.rpm

Description:

op1svg normalizes SVG files so that the OP-1 understands them:
- Remove unsupported tags and attributes
- Remove comments
- Convert styles to attributes, and drop unsupported styles
- Fix decimals; a maximum of 4 decimals is supported by the OP-1
- Reformat the path data in paths

Fedora Account System Username: dcavalca

Comment 1 Davide Cavalca 2021-04-24 21:10:49 UTC
This package built on koji:  https://koji.fedoraproject.org/koji/taskinfo?taskID=66617161

Comment 2 Ben Beasley 2021-04-29 17:34:02 UTC
Package approved; please see “Issues” below for recommendations.

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

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

===== Issues =====

- You “SHOULD” provide a man page for the command-line tool
  (https://docs.fedoraproject.org/en-US/packaging-guidelines/#_manpages).

  I am not blocking the package review on this, but here are two good options:

  1. Add

       BuildRequires:  help2man
       BuildRequires:  python3dist(svg-path)

     and in %build, something like:

       mkdir -p man-build
       pushd man-build
       ln -s ../%{pypi_name}.py %{pypi_name}
       help2man --no-info --output %{pypi_name}.1 %{pypi_name}
       popd

     and in %install,

       install -D -t '%{_mandir}/man1' -m 0644 man-build/%{pypi_name}.1

     and in %files:

       %{_mandir}/man1/%{pypi_name}.1*

  2. Add a hand-written man page as an additional source. It will be nicer than
     the generated one, and will be very simple, but you will have to maintain
     it unless upstream wants to.

     If you choose this route, I am happy to provide the initial man page.

  Alternatively, you are *permitted* to do neither, since this guideline is a
  SHOULD.

===== 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.
     Note: Checking patched sources after %prep for licenses. Licenses
     found: "Expat License", "Unknown or generated". 7 files have unknown
     license. Detailed output of licensecheck in
     /home/reviewer/1953226-python-op1svg/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 2 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.
[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.

     Upstream does not provide any tests.

[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: op1svg-0.1.0-1.20210419git50a3b01.fc35.noarch.rpm
          python-op1svg-0.1.0-1.20210419git50a3b01.fc35.src.rpm
op1svg.noarch: W: no-manual-page-for-binary op1svg
2 packages and 0 specfiles checked; 0 errors, 1 warnings.




Rpmlint (installed packages)
----------------------------
op1svg.noarch: W: no-manual-page-for-binary op1svg
1 packages and 0 specfiles checked; 0 errors, 1 warnings.



Source checksums
----------------
https://github.com/op1hacks/op1svg/archive/50a3b01ebb74fd07b33d91c08b1e59e11494801d/op1svg-50a3b01ebb74fd07b33d91c08b1e59e11494801d.tar.gz :
  CHECKSUM(SHA256) this package     : 8f13084f491b8c9de9e69afd717dc4681d52fe13739ec44485e1171c6d4d73e8
  CHECKSUM(SHA256) upstream package : 8f13084f491b8c9de9e69afd717dc4681d52fe13739ec44485e1171c6d4d73e8


Requires
--------
op1svg (rpmlib, GLIBC filtered):
    /usr/bin/python3
    python(abi)
    python3.9dist(setuptools)
    python3.9dist(svg-path)



Provides
--------
op1svg:
    op1svg
    python3.9dist(op1svg)
    python3dist(op1svg)



Generated by fedora-review 0.7.6 (b083f91) last change: 2020-11-10
Command line :/usr/bin/fedora-review -b 1953226
Buildroot used: fedora-rawhide-x86_64
Active plugins: Generic, Python, Shell-api
Disabled plugins: R, C/C++, PHP, Ruby, SugarActivity, Haskell, fonts, Java, Ocaml, Perl
Disabled flags: EPEL6, EPEL7, DISTTAG, BATCH, EXARCH

Comment 3 Davide Cavalca 2021-04-29 22:44:56 UTC
Thanks! Happy to include a man page if you'd like to write one.

$ fedpkg request-repo python-op1svg 1953226
https://pagure.io/releng/fedora-scm-requests/issue/33759

Comment 4 Ben Beasley 2021-04-30 11:46:41 UTC
Created attachment 1777757 [details]
Man page

This is a straightforward translation of the --help output to groff_man(7) format.

Comment 5 Gwyn Ciesla 2021-04-30 13:15:41 UTC
(fedscm-admin):  The Pagure repository was created at https://src.fedoraproject.org/rpms/python-op1svg

Comment 6 Fedora Update System 2021-04-30 15:54:41 UTC
FEDORA-2021-9814835bf7 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-9814835bf7

Comment 7 Fedora Update System 2021-04-30 16:02:03 UTC
FEDORA-2021-6f34e087e3 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-6f34e087e3

Comment 8 Fedora Update System 2021-04-30 16:08:25 UTC
FEDORA-2021-911a407460 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-911a407460

Comment 9 Fedora Update System 2021-05-01 02:05:23 UTC
FEDORA-2021-9814835bf7 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2021-9814835bf7 \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-9814835bf7

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

Comment 10 Fedora Update System 2021-05-01 02:10:34 UTC
FEDORA-2021-6f34e087e3 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2021-6f34e087e3 \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-6f34e087e3

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

Comment 11 Fedora Update System 2021-05-01 02:16:12 UTC
FEDORA-2021-911a407460 has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2021-911a407460 \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-911a407460

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

Comment 12 Fedora Update System 2021-05-09 00:51:05 UTC
FEDORA-2021-911a407460 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 2021-05-09 01:15:23 UTC
FEDORA-2021-6f34e087e3 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2021-05-09 01:34:27 UTC
FEDORA-2021-9814835bf7 has been pushed to the Fedora 34 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.