Spec URL: https://jjames.fedorapeople.org/python-pytest-regressions/python-pytest-regressions.spec SRPM URL: https://jjames.fedorapeople.org/python-pytest-regressions/python-pytest-regressions-2.2.0-1.fc35.src.rpm Fedora Account System Username: jjames Description: This pytest plugin makes it simple to test general data, images, files, and numeric tables by saving *expected* data in a *data directory* (courtesy of pytest-datadir) that can be used to verify that future runs produce the same data.
Hey, package is APPROVED. See detailed results below. Just a nitpick: the patch is justified, which is great, and it could be mentioned that the changes are present also in upstream, so that it's clear it's not a downstream-only patch forever. --- A bit unrelated part As with the pytest-datadir, I had a prepared specfile using the new pyproject macros. During my run there are three tests that fail in %check. Funnily enough, someone has already reported the same failing tests in the upstream issue: https://github.com/ESSS/pytest-regressions/issues/61 (specifically those in file `test_dataframe_regression.py`). When looking at the results, the problem is that regex doesn't match the expected output. When you look at the test code, you see there are two space characters at the beginning of the expected output, that are not present in the actual project code. So it seems the tests actually should fail - but in your build they all repeatedly pass. I was trying to find out why two set of macros produce different results, but failed in this quest. Do you happen to have any idea what could've happened here? --- 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. Note: Checking patched sources after %prep for licenses. Licenses found: "Unknown or generated", "MIT License", "*No copyright* MIT License". 57 files have unknown license. Detailed output of licensecheck in /home/ksurma/tmp/1981996-python-pytest- regressions/licensecheck.txt [x]: License file installed when any subpackage combination is installed. [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. [-]: Package is not known to require an ExcludeArch tag. [x]: Large documentation must go in a -doc subpackage. Large could be size (~1MB) or number of files. Note: Documentation size is 30720 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]: 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). [-]: Fully versioned dependency in subpackages if applicable. Note: No Requires: %{name}%{?_isa} = %{version}-%{release} in python3-pytest-regressions [x]: Package functions as described. [x]: Latest version is packaged. [x]: Package does not include license text files separate from upstream. [?]: 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. [-]: 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. [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: There are rpmlint messages (see attachment). [x]: Spec file according to URL is the same as in SRPM. Rpmlint ------- Checking: python3-pytest-regressions-2.2.0-1.fc35.noarch.rpm python-pytest-regressions-doc-2.2.0-1.fc35.noarch.rpm python-pytest-regressions-2.2.0-1.fc35.src.rpm python3-pytest-regressions.noarch: W: spelling-error %description -l en_US datadir -> irradiate python-pytest-regressions-doc.noarch: W: wrong-file-end-of-line-encoding /usr/share/doc/python-pytest-regressions-doc/html/objects.inv python-pytest-regressions-doc.noarch: W: file-not-utf8 /usr/share/doc/python-pytest-regressions-doc/html/objects.inv python-pytest-regressions.src: W: spelling-error %description -l en_US datadir -> irradiate 3 packages and 0 specfiles checked; 0 errors, 4 warnings. Requires -------- python3-pytest-regressions (rpmlib, GLIBC filtered): python(abi) python3.10dist(pytest) python3.10dist(pytest-datadir) python3.10dist(pyyaml) python-pytest-regressions-doc (rpmlib, GLIBC filtered): Provides -------- python3-pytest-regressions: python-pytest-regressions python3-pytest-regressions python3.10-pytest-regressions python3.10dist(pytest-regressions) python3dist(pytest-regressions) python-pytest-regressions-doc: python-pytest-regressions-doc
(In reply to Karolina Surma from comment #1) > package is APPROVED. See detailed results below. Thank you! > Just a nitpick: the patch is justified, which is great, and it could be > mentioned that the changes are present also in upstream, so that it's clear > it's not a downstream-only patch forever. Okay, I have added a comment in my copy of the spec file. > As with the pytest-datadir, I had a prepared specfile using the new > pyproject macros. During my run there are three tests that fail in %check. > Funnily enough, someone has already reported the same failing tests in the > upstream issue: https://github.com/ESSS/pytest-regressions/issues/61 > (specifically those in file `test_dataframe_regression.py`). > When looking at the results, the problem is that regex doesn't match the > expected output. When you look at the test code, you see there are two space > characters at the beginning of the expected output, that are not present in > the actual project code. So it seems the tests actually should fail - but in > your build they all repeatedly pass. > I was trying to find out why two set of macros produce different results, > but failed in this quest. Do you happen to have any idea what could've > happened here? Huh, that's odd. I don't know why that would happen, but I will dig into it and see if I can figure it out.
(fedscm-admin): The Pagure repository was created at https://src.fedoraproject.org/rpms/python-pytest-regressions
FEDORA-2021-6008123538 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-6008123538
FEDORA-2021-6008123538 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-6008123538 \*` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-6008123538 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-6008123538 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.