Fedora Account System
Red Hat Associate
Red Hat Customer
I'm testing an update to pytest 7.2.0 and I've discovered a problem with this package. This package needs python3-setuptools to build but this dependency is not specified as a BuildRequires in its specfile. This fact didn't cause any trouble before because python3-pytest <7.2 depends on python3-setuptools so setuptools have been installed as a transitive dependency. pytest uses a different build backend now which means that when we update it to the latest version, this package will fail to build. The plan is to update pytest in ~2 weeks. If you want to, you can find the failed build in https://copr.fedorainfracloud.org/coprs/lbalhar/pytest/
I'll add this to BuildRequires in all branches, interesting that the pyproject_buildrequires macro doesn't handle this case :)
%pyproject_buildrequires should handle this if the dependency is specified in upstream metadata. I see that upstream code uses setuptools in tests and I also see setuptools in the pdm.lock but I have no idea whether this is an optional dependency just for tests. The problem might be there, not in the specfile. Strange is that setuptools is in pdm.lock but not in pyproject.toml. Do you understand pdm well enough to check it and possibly report an issue there?
Not really no, for now I've added a BuildRequires for python3-setuptools and triggered builds for all branches: https://koji.fedoraproject.org/koji/packageinfo?packageID=36139 so that the immediate concern is gone. I'll have this ticket be closed by bodhi after I submit updates and might take a deeper look into the rest of it if I get to it.
FEDORA-2022-b8392d0f6b has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b8392d0f6b
FEDORA-2022-ef631ada81 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ef631ada81
FEDORA-EPEL-2022-b6bab7dc81 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-b6bab7dc81
FEDORA-EPEL-2022-b6bab7dc81 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-2022-b6bab7dc81 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-ef631ada81 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-ef631ada81` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ef631ada81 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-b8392d0f6b has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-b8392d0f6b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b8392d0f6b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I fixed the problem upstream: https://github.com/pdm-project/pdm-pep517/pull/131
FEDORA-2022-ef631ada81 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-b8392d0f6b has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-b6bab7dc81 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.