Bug 2088649 - Review Request: pybind11-json - Using nlohmann::json with pybind11
Summary: Review Request: pybind11-json - Using nlohmann::json with pybind11
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Kadlčík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1225692
TreeView+ depends on / blocked
 
Reported: 2022-05-19 23:46 UTC by Scott K Logan
Modified: 2024-03-23 00:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-03-15 00:38:40 UTC
Type: ---
Embargoed:
jkadlcik: fedora-review+


Attachments (Terms of Use)

Description Scott K Logan 2022-05-19 23:46:28 UTC
Spec URL: https://cottsay.fedorapeople.org/pybind11-json/pybind11-json.spec
SRPM URL: https://cottsay.fedorapeople.org/pybind11-json/pybind11-json-0.2.12-1.fc37.src.rpm

Description:
pybind11_json is an nlohmann::json to pybind11 bridge, it allows you to
automatically convert nlohmann::json to py::object and the other way around.
Simply include the header, and the automatic conversion will be enabled.

Fedora Account System Username: cottsay
Target branches: rawhide f36 f35 epel9 epel8
Koji scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=87264920

Relevant Fedora guidelines: https://docs.fedoraproject.org/en-US/packaging-guidelines/#_packaging_header_only_libraries

Thanks!

Comment 1 lichaoran 2023-02-23 07:46:07 UTC
Hi Soctt, i'd like to try to review this ticket as im still trying to become a packager, @Jakub Kadlčík is my sponsor :)
> Version:        0.2.12
A newer version 0.2.13 is released, any reason to keep using this version?
see: https://github.com/pybind/pybind11_json/releases/tag/0.2.13

Comment 2 lichaoran 2023-02-23 09:34:24 UTC
Package Review
==============

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



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

C/C++:
[x]: Package does not contain kernel modules.
[x]: Package contains no static executables.
[x]: If your application is a C or C++ application you must list a
     BuildRequires against gcc, gcc-c++ or clang.
[x]: Package does not contain any libtool archives (.la)
[x]: Rpath absent or only used for internal libs.

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: "BSD 3-Clause License", "Unknown or generated". 1 files have
     unknown license. Detailed output of licensecheck in
     /root/build_upstream/2088649-pybind11-json/licensecheck.txt
[x]: %build honors applicable compiler flags or justifies otherwise.
[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.
[x]: 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: No rpmlint messages.
[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

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

Generic:
[x]: 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.
[!]: Latest version is packaged. there is a newer version 0.2.13
[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.
[?]: 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:
[x]: Rpmlint is run on all installed packages.
     Note: No rpmlint messages.
[x]: Spec file according to URL is the same as in SRPM.


Rpmlint
-------
Checking: pybind11-json-devel-0.2.12-1.fc39.noarch.rpm
          pybind11-json-0.2.12-1.fc39.src.rpm
========================================================================================================== rpmlint session starts ==========================================================================================================rpmlint: 2.4.0
configuration:
    /usr/lib/python3.11/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
checks: 31, packages: 1

 1 packages and 0 specfiles checked; 0 errors, 0 warnings, 0 badness; has taken 0.0 s



Source checksums
----------------
https://github.com/pybind/pybind11_json/archive/0.2.12/pybind11-json-0.2.12.tar.gz :
  CHECKSUM(SHA256) this package     : a9e308d4cf3de16d192cd0baf641bfe17a3a3046e8652e6724204afa3e736db7
  CHECKSUM(SHA256) upstream package : a9e308d4cf3de16d192cd0baf641bfe17a3a3046e8652e6724204afa3e736db7


Requires
--------
pybind11-json-devel (rpmlib, GLIBC filtered):
    cmake-filesystem
    json-devel
    pybind11-devel



Provides
--------
pybind11-json-devel:
    cmake(pybind11_json)
    pybind11-json-devel
    pybind11-json-static



Generated by fedora-review 0.9.0 (6761b6c) last change: 2022-08-23
Command line :/usr/bin/fedora-review -b 2088649
Buildroot used: fedora-rawhide-x86_64
Active plugins: Shell-api, C/C++, Generic
Disabled plugins: SugarActivity, Java, R, PHP, Python, Haskell, Perl, Ocaml, fonts
Disabled flags: EPEL6, EPEL7, DISTTAG, BATCH, EXARCH

Comment 3 Package Review 2024-02-24 00:45:31 UTC
This is an automatic check from review-stats script.

This review request ticket hasn't been updated for some time. We're sorry
it is taking so long. If you're still interested in packaging this software
into Fedora repositories, please respond to this comment clearing the
NEEDINFO flag.

You may want to update the specfile and the src.rpm to the latest version
available and to propose a review swap on Fedora devel mailing list to increase
chances to have your package reviewed. If this is your first package and you
need a sponsor, you may want to post some informal reviews. Read more at
https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group.

Without any reply, this request will shortly be considered abandoned
and will be closed.
Thank you for your patience.

Comment 4 Jakub Kadlčík 2024-03-06 20:31:43 UTC
Hello Scottt,
I am sorry, I missed the ticket.

> Version:        0.2.12

As lichaoran said, there is already 0.2.13 available. I am not going to block the ticket (any longer) because of this but please don't forget to update after importing the package to DistGit


> # Pulled directly from upstream
> Patch0:         %{name}-0.2.12-add-missing-interpreter-guards.patch

Can you please link the upstream PR from which this is taken?

+1 though

Comment 5 Scott K Logan 2024-03-06 20:51:38 UTC
Thanks Jakub.

> > # Pulled directly from upstream
> > Patch0:         %{name}-0.2.12-add-missing-interpreter-guards.patch
> Can you please link the upstream PR from which this is taken?

This was merged as part of 0.2.13 and is no longer needed. I'll remember to add a reference to the upstream change next time I encounter this situation.

For completeness, here's what I'll by importing:

Spec URL: https://cottsay.fedorapeople.org/pybind11-json/pybind11-json.spec
SRPM URL: https://cottsay.fedorapeople.org/pybind11-json/pybind11-json-0.2.13-1.fc41.src.rpm
Koji scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=114575903

Comment 6 Fedora Admin user for bugzilla script actions 2024-03-06 20:53:53 UTC
The Pagure repository was created at https://src.fedoraproject.org/rpms/pybind11-json

Comment 7 Fedora Update System 2024-03-06 21:34:47 UTC
FEDORA-2024-613c7dfa2d (pybind11-json-0.2.13-1.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-613c7dfa2d

Comment 8 Fedora Update System 2024-03-06 21:34:48 UTC
FEDORA-EPEL-2024-f685f1110f (pybind11-json-0.2.13-1.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-f685f1110f

Comment 9 Fedora Update System 2024-03-06 21:34:49 UTC
FEDORA-2024-944856881b (pybind11-json-0.2.13-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-944856881b

Comment 10 Fedora Update System 2024-03-07 01:47:11 UTC
FEDORA-2024-944856881b has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-944856881b \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-944856881b

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

Comment 11 Fedora Update System 2024-03-07 02:01:59 UTC
FEDORA-EPEL-2024-0f6688c4b9 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-0f6688c4b9

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

Comment 12 Fedora Update System 2024-03-07 02:19:46 UTC
FEDORA-EPEL-2024-f685f1110f 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-2024-f685f1110f

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

Comment 13 Fedora Update System 2024-03-07 02:27:49 UTC
FEDORA-2024-613c7dfa2d has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-613c7dfa2d \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-613c7dfa2d

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

Comment 14 Fedora Update System 2024-03-15 00:38:40 UTC
FEDORA-EPEL-2024-0f6688c4b9 (pybind11-json-0.2.13-1.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2024-03-15 01:01:02 UTC
FEDORA-EPEL-2024-f685f1110f (pybind11-json-0.2.13-1.el8) has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2024-03-15 01:05:37 UTC
FEDORA-2024-613c7dfa2d (pybind11-json-0.2.13-1.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Fedora Update System 2024-03-23 00:29:55 UTC
FEDORA-2024-944856881b (pybind11-json-0.2.13-1.fc40) has been pushed to the Fedora 40 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.