Description of problem: It seems that `%pyproject_wheel` does not support other build systems like flit and requires pip to build a wheel. Version-Release number of selected component (if applicable): pyproject-rpm-macros-0-28.fc34 How reproducible: Always Steps to Reproduce: 1. Build python-pep517 from source Actual results: Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.svaSAx + umask 022 + cd /builddir/build/BUILD + cd pep517-0.7.0 + export TMPDIR=/builddir/build/BUILD/pep517-0.7.0/.pyproject-builddir + TMPDIR=/builddir/build/BUILD/pep517-0.7.0/.pyproject-builddir + mkdir -p /builddir/build/BUILD/pep517-0.7.0/.pyproject-builddir + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld ' + /usr/bin/python3 -m pip wheel --wheel-dir pyproject-wheeldir --no-deps --use-pep517 --no-build-isolation --disable-pip-version-check --no-clean --progress-bar off --verbose . /usr/bin/python3: No module named pip Expected results: Sucessful build
Pyproject macros support various build backends (such as setuptools, flit) but they use pip as the build frontend. Is this an issue for you and if so, why? Currently, %pyproject_wheel is only supported with %pyproject_buildrequires. %pyproject_buildrequires generates a dependency on pip, sot the error you see is most likely caused by not using %pyproject_buildrequires. Note that even if %pyproject_wheel somehow builds the wheel without pip, the %pyproject_install macro is a wrapper around pip to install it as well. python-pep517 source was created when pip was a runtime dependency of pyproject-rpm-macros. I would have fixed the spec file if it was tracked by Kochei, but it wasn't :( Similar fix in python-tox-current-env: https://src.fedoraproject.org/rpms/python-tox-current-env/c/3e7fdc2f
Here's a fix for pep517: https://src.fedoraproject.org/rpms/python-pep517/pull-request/3
FEDORA-2020-18c162c68b has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-4461cf5515 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-4461cf5515
A quick grep reveals that python-pep517 was the only remaining package w/out %pyproject_buildrequires.
FEDORA-2020-4461cf5515 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-4461cf5515` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-4461cf5515 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-5bace8535f has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-5bace8535f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-5bace8535f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-5bace8535f has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-4461cf5515 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.