python/Makefile | 5 ++--- python/setup.py | 4 ---- python/tests/minreqs.txt | 10 +++++----- tests/Makefile.include | 2 +- 4 files changed, 8 insertions(+), 13 deletions(-)
GitLab CI: https://gitlab.com/jsnow/qemu/-/pipelines/2320293005 The tox test is still broken because our use of avocado uses pkg_resources, it will have to be removed but in a separate series. Let's get the core tests green first and then worry about deeper surgeries later. John Snow (2): python: fix minreqs test under newest pip/setuptools python: drop uses of pkg_resources python/Makefile | 5 ++--- python/setup.py | 4 ---- python/tests/minreqs.txt | 10 +++++----- tests/Makefile.include | 2 +- 4 files changed, 8 insertions(+), 13 deletions(-) -- 2.53.0
On Wed, 11 Feb 2026 at 19:59, John Snow <jsnow@redhat.com> wrote:
>
> GitLab CI: https://gitlab.com/jsnow/qemu/-/pipelines/2320293005
>
> The tox test is still broken because our use of avocado uses
> pkg_resources, it will have to be removed but in a separate
> series. Let's get the core tests green first and then worry about deeper
> surgeries later.
>
> John Snow (2):
> python: fix minreqs test under newest pip/setuptools
> python: drop uses of pkg_resources
>
> python/Makefile | 5 ++---
> python/setup.py | 4 ----
> python/tests/minreqs.txt | 10 +++++-----
> tests/Makefile.include | 2 +-
> 4 files changed, 8 insertions(+), 13 deletions(-)
Applying this series locally fixes the "No module named 'pkg_resources'"
error, but instead I get:
lanath:noble:qemu$ make -C build/clang/ check-functional
make: Entering directory '/home/pm215/qemu/build/clang'
VENVPIP install --no-build-isolation -e /home/pm215/qemu/python/
error: subprocess-exited-with-error
× Preparing editable metadata (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [13 lines of output]
running dist_info
creating /tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info
writing /tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info/PKG-INFO
writing dependency_links to
/tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info/dependency_links.txt
writing entry points to
/tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info/entry_points.txt
writing requirements to
/tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info/requires.txt
writing top-level names to
/tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info/top_level.txt
writing manifest file
'/tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info/SOURCES.txt'
reading manifest file
'/tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file
'/tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info/SOURCES.txt'
creating '/tmp/pip-modern-metadata-bj38p2z_/qemu-0.6.1.0a1.dist-info'
error: invalid command 'bdist_wheel'
[end of output]
note: This error originates from a subprocess, and is likely not a
problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
make: *** [/home/pm215/qemu/tests/Makefile.include:109:
/home/pm215/qemu/build/clang/pyvenv/tests.group] Error 1
make: Leaving directory '/home/pm215/qemu/build/clang'
Applying only patch 2 and not patch 1 avoids this and allows
check-functional to work.
thanks
-- PMM
On Thu, Feb 12, 2026 at 6:31 AM Peter Maydell <peter.maydell@linaro.org> wrote: > > On Wed, 11 Feb 2026 at 19:59, John Snow <jsnow@redhat.com> wrote: > > > > GitLab CI: https://gitlab.com/jsnow/qemu/-/pipelines/2320293005 > > > > The tox test is still broken because our use of avocado uses > > pkg_resources, it will have to be removed but in a separate > > series. Let's get the core tests green first and then worry about deeper > > surgeries later. > > > > John Snow (2): > > python: fix minreqs test under newest pip/setuptools > > python: drop uses of pkg_resources > > > > python/Makefile | 5 ++--- > > python/setup.py | 4 ---- > > python/tests/minreqs.txt | 10 +++++----- > > tests/Makefile.include | 2 +- > > 4 files changed, 8 insertions(+), 13 deletions(-) > > Applying this series locally fixes the "No module named 'pkg_resources'" > error, but instead I get: > > lanath:noble:qemu$ make -C build/clang/ check-functional > make: Entering directory '/home/pm215/qemu/build/clang' > VENVPIP install --no-build-isolation -e /home/pm215/qemu/python/ > error: subprocess-exited-with-error > > × Preparing editable metadata (pyproject.toml) did not run successfully. > │ exit code: 1 > ╰─> [13 lines of output] > running dist_info > creating /tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info > writing /tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info/PKG-INFO > writing dependency_links to > /tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info/dependency_links.txt > writing entry points to > /tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info/entry_points.txt > writing requirements to > /tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info/requires.txt > writing top-level names to > /tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info/top_level.txt > writing manifest file > '/tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info/SOURCES.txt' > reading manifest file > '/tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > writing manifest file > '/tmp/pip-modern-metadata-bj38p2z_/qemu.egg-info/SOURCES.txt' > creating '/tmp/pip-modern-metadata-bj38p2z_/qemu-0.6.1.0a1.dist-info' > error: invalid command 'bdist_wheel' > [end of output] > > note: This error originates from a subprocess, and is likely not a > problem with pip. > error: metadata-generation-failed > > × Encountered error while generating package metadata. > ╰─> See above for output. > > note: This is an issue with the package mentioned above, not pip. > hint: See above for details. > make: *** [/home/pm215/qemu/tests/Makefile.include:109: > /home/pm215/qemu/build/clang/pyvenv/tests.group] Error 1 > make: Leaving directory '/home/pm215/qemu/build/clang' > > Applying only patch 2 and not patch 1 avoids this and allows > check-functional to work. > > thanks > -- PMM Tch, I see what happened. Happened to not run into it in local testing because I have more packages than you! Thanks, apologies for the fuss. --js
© 2016 - 2026 Red Hat, Inc.