Bug 2323071 - Review Request: python-etelemetry - Etelemetry python client API
Summary: Review Request: python-etelemetry - Etelemetry python client API
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: https://github.com/sensein/etelemetry...
Whiteboard:
Depends On: 2323068
Blocks: fedora-neuro, NeuroFedora 2323073
TreeView+ depends on / blocked
 
Reported: 2024-10-31 22:25 UTC by Sandro
Modified: 2025-01-20 17:16 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-01-20 17:16:59 UTC
Type: ---
Embargoed:
code: fedora-review+


Attachments (Terms of Use)
The .spec file difference from Copr build 8329230 to 8548434 (981 bytes, patch)
2025-01-20 08:14 UTC, Fedora Review Service
no flags Details | Diff

Description Sandro 2024-10-31 22:25:22 UTC
Spec URL: https://gui1ty.fedorapeople.org/review/python-etelemetry.spec
SRPM URL: https://gui1ty.fedorapeople.org/review/python-etelemetry-0.3.1-1.fc42.src.rpm

Description:
A lightweight python client to communicate with the etelemetry server.

Fedora Account System Username: gui1ty

Comment 1 Fedora Review Service 2024-10-31 22:27:17 UTC
Copr build:
https://copr.fedorainfracloud.org/coprs/build/8196957
(failed)

Build log:
https://download.copr.fedorainfracloud.org/results/@fedora-review/fedora-review-2323071-python-etelemetry/fedora-rawhide-x86_64/08196957-python-etelemetry/builder-live.log.gz

Please make sure the package builds successfully at least for Fedora Rawhide.

- If the build failed for unrelated reasons (e.g. temporary network
  unavailability), please ignore it.
- If the build failed because of missing BuildRequires, please make sure they
  are listed in the "Depends On" field


---
This comment was created by the fedora-review-service
https://github.com/FrostyX/fedora-review-service

If you want to trigger a new Copr build, add a comment containing new
Spec and SRPM URLs or [fedora-review-service-build] string.

Comment 2 Ben Beasley 2024-11-29 06:36:52 UTC
This looks good, except for a nit-pick about the License tag and versioneer: the License should be "Apache-2.0 AND Unlicense" because the versioneer-generated _version.py is under the same license as Versioneer itself.

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

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


Issues:
=======
- Dist tag is present.

  OK: fedora-review does not understand rpmautospec

- Package must not depend on deprecated() packages.
  Note: python3-pytest7 is deprecated, you must not depend on it.
  See: https://docs.fedoraproject.org/en-US/packaging-
  guidelines/deprecating-packages/

  OK: spurious diagnostic, built with pytest 8

- Versioneer is always a pain. The bundled versioneer.py is CC0-1.0, which is
  not-allowed for code, but since copies were packaged in Fedora prior to
  2022-08-01, it’s OK for distribution, so you don’t have to filter it out of
  the source archive before uploading.
  https://gitlab.com/fedora/legal/fedora-license-data/-/issues/91#note_1151947383

    ## License
    
    To make Versioneer easier to embed, all its code is dedicated to the public
    domain. The `_version.py` that it creates is also in the public domain.
    Specifically, both are released under the Creative Commons "Public Domain
    Dedication" license (CC0-1.0), as described in
    https://creativecommons.org/publicdomain/zero/1.0/ .

  Fedora has versioneer 0.29, and you’re using the system versioneer, so you
  have an Unlicense-licensed version of versioneer – although with similar
  language conflating the “public domain” with the chosen ultra-permissive
  license. Why does that matter? Because as described in versioneer’s
  README.md, the _version.py generated by Versioneer is considered to be under
  the same license as Versioneer itself:
  https://github.com/python-versioneer/python-versioneer/tree/0.29?tab=readme-ov-file#license

  Therefore, strictly speaking, the license for this package should be
  "Apache-2.0 AND Unlicense".
  

===== 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.
[!]: License field in the package spec file matches the actual license.
     Note: Checking patched sources after %prep for licenses. Licenses
     found: "Unknown or generated", "Apache License 2.0", "*No copyright*
     Apache License", "*No copyright* Public domain". 12 files have unknown
     license. Detailed output of licensecheck in
     /home/ben/fedora/review/2323071-python-etelemetry/licensecheck.txt

     The _version.py generated by the system python-versioneer is technically
     Unlicense; see Issues.

[x]: Package must own all directories that it creates.
     Note: Directories without known owners: /usr/lib/python3.13,
     /usr/lib/python3.13/site-packages

     Spurious.

[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]: 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]: The License field must be a valid SPDX expression.
[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]: 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]: Large documentation must go in a -doc subpackage. Large could be size
     (~1MB) or number of files.
     Note: Documentation size is 1897 bytes in 1 files.
[x]: Packages must not store files under /srv, /opt or /usr/local

Python:
[-]: 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).
[x]: Package functions as described.

     Tests pass – although there is only one test we can run offline.

[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.
[-]: Sources are verified with gpgverify first in %prep if upstream
     publishes signatures.
     Note: gpgverify is not used.
[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]: 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:
[!]: 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: No rpmlint messages.


Rpmlint
-------
Checking: python3-etelemetry-0.3.1-1.fc42.noarch.rpm
          python-etelemetry-0.3.1-1.fc42.src.rpm
============================ rpmlint session starts ============================
rpmlint: 2.5.0
configuration:
    /usr/lib/python3.13/site-packages/rpmlint/configdefaults.toml
    /etc/xdg/rpmlint/fedora-legacy-licenses.toml
    /etc/xdg/rpmlint/fedora-spdx-licenses.toml
    /etc/xdg/rpmlint/fedora.toml
    /etc/xdg/rpmlint/scoring.toml
    /etc/xdg/rpmlint/users-groups.toml
    /etc/xdg/rpmlint/warn-on-functions.toml
rpmlintrc: [PosixPath('/tmp/tmpc8fgz5sq')]
checks: 32, packages: 2

python-etelemetry.spec: W: patch-not-applied Patch0: %{forgeurl}/pull/56.patch
 2 packages and 0 specfiles checked; 0 errors, 1 warnings, 10 filtered, 0 badness; has taken 0.4 s 




Rpmlint (installed packages)
----------------------------
============================ rpmlint session starts ============================
rpmlint: 2.5.0
configuration:
    /usr/lib/python3.13/site-packages/rpmlint/configdefaults.toml
    /etc/xdg/rpmlint/fedora-spdx-licenses.toml
    /etc/xdg/rpmlint/fedora.toml
    /etc/xdg/rpmlint/scoring.toml
    /etc/xdg/rpmlint/users-groups.toml
    /etc/xdg/rpmlint/warn-on-functions.toml
checks: 32, packages: 1

 1 packages and 0 specfiles checked; 0 errors, 0 warnings, 6 filtered, 0 badness; has taken 0.1 s 



Source checksums
----------------
https://github.com/sensein/etelemetry-client/archive/v0.3.1/etelemetry-client-0.3.1.tar.gz :
  CHECKSUM(SHA256) this package     : 91861fc0e9593e583ad12610a99859d88a45216f59e803c96cfa8b7334f6171f
  CHECKSUM(SHA256) upstream package : 91861fc0e9593e583ad12610a99859d88a45216f59e803c96cfa8b7334f6171f


Requires
--------
python3-etelemetry (rpmlib, GLIBC filtered):
    python(abi)
    python3.13dist(ci-info)
    python3.13dist(packaging)
    python3.13dist(requests)



Provides
--------
python3-etelemetry:
    python-etelemetry
    python3-etelemetry
    python3.13-etelemetry
    python3.13dist(etelemetry)
    python3dist(etelemetry)



Diff spec file in url and in SRPM
---------------------------------
--- /home/ben/fedora/review/2323071-python-etelemetry/srpm/python-etelemetry.spec	2024-11-29 01:11:28.795678043 -0500
+++ /home/ben/fedora/review/2323071-python-etelemetry/srpm-unpacked/python-etelemetry.spec	2024-10-30 20:00:00.000000000 -0400
@@ -1,2 +1,12 @@
+## START: Set by rpmautospec
+## (rpmautospec version 0.7.2)
+## RPMAUTOSPEC: autorelease, autochangelog
+%define autorelease(e:s:pb:n) %{?-p:0.}%{lua:
+    release_number = 1;
+    base_release_number = tonumber(rpm.expand("%{?-b*}%{!?-b:1}"));
+    print(release_number + base_release_number - 1);
+}%{?-e:.%{-e*}}%{?-s:.%{-s*}}%{!?-n:%{?dist}}
+## END: Set by rpmautospec
+
 %global pypi_name etelemetry
 
@@ -78,3 +88,6 @@
 
 %changelog
-%autochangelog
+## START: Generated by rpmautospec
+* Thu Oct 31 2024 Sandro <devel> - 0.3.1-1
+- Initial package
+## END: Generated by rpmautospec


Generated by fedora-review 0.10.0 (e79b66b) last change: 2023-07-24
Command line :/usr/bin/fedora-review -b 2323071
Buildroot used: fedora-rawhide-x86_64
Active plugins: Python, Generic, Shell-api
Disabled plugins: R, Java, C/C++, PHP, Perl, SugarActivity, fonts, Ocaml, Haskell
Disabled flags: EXARCH, EPEL6, EPEL7, DISTTAG, BATCH

Comment 3 Sandro 2024-11-30 11:12:28 UTC
Thanks for the review

(In reply to Ben Beasley from comment #2)
> Issues:
> =======

<snip>

>     ## License
>     
>     To make Versioneer easier to embed, all its code is dedicated to the
> public
>     domain. The `_version.py` that it creates is also in the public domain.
>     Specifically, both are released under the Creative Commons "Public Domain
>     Dedication" license (CC0-1.0), as described in
>     https://creativecommons.org/publicdomain/zero/1.0/ .
> 
>   Fedora has versioneer 0.29, and you’re using the system versioneer, so you
>   have an Unlicense-licensed version of versioneer – although with similar
>   language conflating the “public domain” with the chosen ultra-permissive
>   license. Why does that matter? Because as described in versioneer’s
>   README.md, the _version.py generated by Versioneer is considered to be
> under
>   the same license as Versioneer itself:
>  
> https://github.com/python-versioneer/python-versioneer/tree/0.29?tab=readme-
> ov-file#license
> 
>   Therefore, strictly speaking, the license for this package should be
>   "Apache-2.0 AND Unlicense".

Thanks for the detailed explanation.

What about packages that use Versioneer prior to the switch to Unlicense (<0.27)? Would I have to add "AND CC0-1.0"? I believe I maintain a couple of packages using Versioneer. So far, I have never paid attention to the license of _version.py nor to which version of Versioneer is shipped in the sources if any.

Spec URL: https://gui1ty.fedorapeople.org/review/python-etelemetry.spec
SRPM URL: https://gui1ty.fedorapeople.org/review/python-etelemetry-0.3.1-2.fc42.src.rpm

Comment 4 Fedora Review Service 2024-11-30 11:16:19 UTC
Copr build:
https://copr.fedorainfracloud.org/coprs/build/8329230
(succeeded)

Review template:
https://download.copr.fedorainfracloud.org/results/@fedora-review/fedora-review-2323071-python-etelemetry/fedora-rawhide-x86_64/08329230-python-etelemetry/fedora-review/review.txt

Found issues:

- python3-pytest7 is deprecated, you must not depend on it.
  Read more: https://docs.fedoraproject.org/en-US/packaging-guidelines/deprecating-packages/

Please know that there can be false-positives.

---
This comment was created by the fedora-review-service
https://github.com/FrostyX/fedora-review-service

If you want to trigger a new Copr build, add a comment containing new
Spec and SRPM URLs or [fedora-review-service-build] string.

Comment 5 Ben Beasley 2025-01-15 04:56:50 UTC
Sorry, I didn’t realize I never finished this review. I’ll review the updated submission ASAP.

> What about packages that use Versioneer prior to the switch to Unlicense (<0.27)? Would I have to add "AND CC0-1.0"? I believe I maintain a couple of packages using Versioneer. So far, I have never paid attention to the license of _version.py nor to which version of Versioneer is shipped in the sources if any.

Yes, technically, as I understand it, Versioneer has been LicenseRef-Fedora-Public-Domain, then CC0-1.0, and then Unlicense, in different versions, and the generated _version.py files have always had the same licenses as the copy of Versioneer that generated them. I don’t think that making a mistake here has much consequence since these are all ultra-permissive and the _version.py files are so trivial that it’s questionable whether they contain anything copyrightable, but I do *try* to get this right.

Comment 6 Ben Beasley 2025-01-15 05:03:23 UTC
(In reply to Ben Beasley from comment #5)
> Yes, technically, as I understand it, Versioneer has been
> LicenseRef-Fedora-Public-Domain, then CC0-1.0, and then Unlicense, in
> different versions, and the generated _version.py files have always had the
> same licenses as the copy of Versioneer that generated them. I don’t think
> that making a mistake here has much consequence since these are all
> ultra-permissive and the _version.py files are so trivial that it’s
> questionable whether they contain anything copyrightable, but I do *try* to
> get this right.

(When I say _version.py files are trivial, I’m speaking of the _version.py files that are only a few lines and just contain metadata, like the one in the binary RPM here, not the ones with many lines of Python source code, like the one in the source archive here.)

Comment 7 Ben Beasley 2025-01-15 05:07:37 UTC
From the latest submission, I don’t believe this comment is correct:

# _version.py, from the sources (SRPM) as well as the shipped (RPM)
# version are Unlicense.

As noted in https://bugzilla.redhat.com/show_bug.cgi?id=2323071#c2, versioneer.py and etelemetry/_version.py in the source archive are both based on versioneer 0.21, which was in the CC0-1.0 era; see https://github.com/python-versioneer/python-versioneer/commit/dc5cddf5cf3d6ae5048bf1c28df2982ecb20fe4c and https://github.com/python-versioneer/python-versioneer/tree/0.21?tab=readme-ov-file#license.

Since you generate _version.py for the binary RPMs using the system versioneer, the License "Apache-2.0 AND Unlicense" is correct, but if you had a SourceLicense, it would need to be "Apache-2.0 AND CC0-1.0".

Comment 8 Sandro 2025-01-20 08:10:05 UTC
I don't care much about specifying a separate source license. I fixed the comment accordingly.

Spec URL: https://gui1ty.fedorapeople.org/review/python-etelemetry.spec
SRPM URL: https://gui1ty.fedorapeople.org/review/python-etelemetry-0.3.1-3.fc42.src.rpm

Comment 9 Fedora Review Service 2025-01-20 08:14:27 UTC
Created attachment 2066742 [details]
The .spec file difference from Copr build 8329230 to 8548434

Comment 10 Fedora Review Service 2025-01-20 08:14:30 UTC
Copr build:
https://copr.fedorainfracloud.org/coprs/build/8548434
(succeeded)

Review template:
https://download.copr.fedorainfracloud.org/results/@fedora-review/fedora-review-2323071-python-etelemetry/fedora-rawhide-x86_64/08548434-python-etelemetry/fedora-review/review.txt

Found issues:

- python3-pytest7 is deprecated, you must not depend on it.
  Read more: https://docs.fedoraproject.org/en-US/packaging-guidelines/deprecating-packages/

Please know that there can be false-positives.

---
This comment was created by the fedora-review-service
https://github.com/FrostyX/fedora-review-service

If you want to trigger a new Copr build, add a comment containing new
Spec and SRPM URLs or [fedora-review-service-build] string.

Comment 11 Ben Beasley 2025-01-20 15:48:53 UTC
The spec-file diff shows that the license-comment nitpick was addressed, and nothing else was changed that needs further review. The package is APPROVED.

Comment 12 Fedora Admin user for bugzilla script actions 2025-01-20 16:56:34 UTC
The Pagure repository was created at https://src.fedoraproject.org/rpms/python-etelemetry

Comment 13 Fedora Update System 2025-01-20 17:12:39 UTC
FEDORA-2025-aa1f28bdbb (python-etelemetry-0.3.1-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-aa1f28bdbb

Comment 14 Fedora Update System 2025-01-20 17:16:59 UTC
FEDORA-2025-aa1f28bdbb (python-etelemetry-0.3.1-1.fc42) has been pushed to the Fedora 42 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.