Your message dated Sun, 2 Jun 2024 20:23:35 +0100
with message-id <zlzgtz_9oooxg...@riva.ucam.org>
and subject line Fixed by python-invoke 2.0.0-1.2
has caused the Debian Bug report #1056503,
regarding python-semantic-release's autopkg tests fail with Python 3.12
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1056503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-semantic-release
Version: 7.32.2-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
python-semantic-release's autopkg tests fail with Python 3.12:
[...]
212s autopkgtest [19:08:58]: test run-tests: [-----------------------
212s ============================= test session starts
==============================
212s platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0 --
/usr/bin/python3.12
212s cachedir: .pytest_cache
212s rootdir: /tmp/autopkgtest.fltlFo/autopkgtest_tmp
212s plugins: mock-3.11.1
212s collecting ... collected 13 items / 1 error
212s
212s ==================================== ERRORS
====================================
212s ______________________ ERROR collecting tests/test_cli.py
______________________
212s ImportError while importing test module
'/tmp/autopkgtest.fltlFo/autopkgtest_tmp/tests/test_cli.py'.
212s Hint: make sure your test modules/packages have valid Python names.
212s Traceback:
212s /usr/lib/python3.12/importlib/__init__.py:90: in import_module
212s return _bootstrap._gcd_import(name[level:], package, level)
212s tests/test_cli.py:3: in <module>
212s from semantic_release.cli import changelog, main,
print_version, publish, version
212s /usr/lib/python3/dist-packages/semantic_release/cli.py:15: in <module>
212s from .dist import build_dists, remove_dists, should_build,
should_remove_dist
212s /usr/lib/python3/dist-packages/semantic_release/dist.py:6: in <module>
212s from invoke import run
212s /usr/lib/python3/dist-packages/invoke/__init__.py:23: in <module>
212s from .loader import FilesystemLoader # noqa
212s /usr/lib/python3/dist-packages/invoke/loader.py:3: in <module>
212s import imp
212s E ModuleNotFoundError: No module named 'imp'
212s =========================== short test summary info
============================
212s ERROR tests/test_cli.py
212s !!!!!!!!!!!!!!!!!!!!!!!!!! stopping after 1 failures
!!!!!!!!!!!!!!!!!!!!!!!!!!!
212s =============================== 1 error in 0.57s
===============================
--- End Message ---
--- Begin Message ---
These python-semantic-release test failures were actually bugs in
python-invoke rather than directly in python-semantic-release, and were
fixed there a while ago:
python-invoke (2.0.0-1.2) unstable; urgency=medium
* Team upload.
* Avoid FTBFS with Python3.12 by using python3-zombie-imp
-- Alexandre Detiste <tc...@debian.org> Tue, 02 Jan 2024 20:32:49 +0100
I've tested that python-semantic-release passes again now.
--
Colin Watson (he/him) [cjwat...@debian.org]
--- End Message ---
