Package: src:vmdb2
Version: 0.28-1
Severity: serious
Tags: sid trixie ftbfs
User: debian-python@lists.debian.org
Usertags: python3.12

With python3-defaults from experimental, the package fails to build:

[...]
dh_auto_build
I: pybuild base:305: /usr/bin/python3.11 setup.py build
I: pybuild base:305: /usr/bin/python3 setup.py build
bash format.sh
[WARNING] Deprecated: --self-contained. use --embed-resources --standalone make[1]: Leaving directory '/<<PKGBUILDDIR>>'
debian/rules override_dh_auto_test
make[1]: Entering directory '/<<PKGBUILDDIR>>'
./check
Running unit tests ============================================
Traceback (most recent call last):
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "/usr/lib/python3/dist-packages/CoverageTestRunner.py", line 22,
in <module>
import imp
ModuleNotFoundError: No module named 'imp'
make[1]: *** [debian/rules:16: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit
status 2 --------------------------------------------------------------------------------
Build finished at 2024-01-29T10:47:03Z

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Processing control commands:

tags -1 help

Bug #1061765 [src:vmdb2] vmdb2 ftbfs with Python 3.12 as default
Added tag(s) help.

--
1061765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061765
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Fri, 23 Feb 2024 16:20:47 +0000
with message-id <E1rdYI3-00G3jB-3X@fasolo.debian.org>
and subject line Bug#1061765: fixed in vmdb2 0.28-2
has caused the Debian Bug report #1061765,
regarding vmdb2 ftbfs with Python 3.12 as default
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 owner@bugs.debian.org
immediately.)


--
1061765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061765
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Received: (at submit) by bugs.debian.org; 29 Jan 2024 12:56:37 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-11.1 required=4.0 tests=BAYES_00,
BODY_INCLUDES_PACKAGE,FORGED_SPF_HELO,FROMDEVELOPER,HAS_PACKAGE,
RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,
SPF_NONE,T_SCC_BODY_TEXT_LINE,URIBL_BLACK autolearn=ham
autolearn_force=no version=3.4.6-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 20; hammy, 150; neutral, 59; spammy,
0. spammytokens: hammytokens:0.000-+--python3, 0.000-+--pkgbuilddir,
0.000-+--PKGBUILDDIR, 0.000-+--H*F:U*doko, 0.000-+--trixie
Return-path: <doko@debian.org>
Received: from einhorn.in-berlin.de ([192.109.42.8]:47545 helo=einhorn-mail-out.in-berlin.de)
by buxtehude.debian.org