#1063412 virulencefinder fails autopkg tests with Python 3.12

#1063412#5
Date:
2024-02-07 20:13:52 UTC
From:
To:
[...]
692s autopkgtest [16:44:14]: test run-unit-test: [-----------------------
699s Traceback (most recent call last):
699s   File "/usr/bin/virulencefinder.py", line 7, in <module>
699s     from distutils.spawn import find_executable
699s ModuleNotFoundError: No module named 'distutils'
699s autopkgtest [16:44:21]: test run-unit-test: -----------------------]
700s autopkgtest [16:44:22]: test run-unit-test:  - - - - - - - - - -
results - - - - - - - - - -
700s run-unit-test        FAIL non-zero exit status 1
700s autopkgtest [16:44:22]: @@@@@@@@@@@@@@@@@@@@ summary
700s run-unit-test        FAIL non-zero exit status 1

#1063412#10
Date:
2024-02-08 09:46:17 UTC
From:
To:
Am Wed, Feb 07, 2024 at 09:13:52PM +0100 schrieb Matthias Klose:

I have

 $ dpkg -l virulencefinder | grep ^ii
 ii  virulencefinder 2.0.4-4      all          identify virulence genes in total or partial sequenced isolates of bacteria

This was fixed in 2.0.4-4 by closing bug #1061856.

$ grep distutils /usr/bin/virulencefinder.py

$ head -n8 /usr/bin/virulencefinder.py
#! /usr/bin/python3
from __future__ import division
from argparse import ArgumentParser
from tabulate import tabulate
from cgecore.blaster import Blaster
from cgecore.cgefinder import CGEFinder
import shutil
import sys

#1063412#17
Date:
2024-02-18 16:50:58 UTC
From:
To:
Version: 2.0.4-4

I reran a couple of tests on my end too and couldn't reproduce
the issue on my end on neither 2.0.4-4, nor the new upstream
version being uploaded as 2.0.5-1.  I think this can be closed.

Have a nice Sunday,  :)