Hi Sudip,
it seems I was to optimistic in fixing v-sim as quickly as expected so
I'm not sure whether it will hit the archive before the NMU. To avoid
changing the history in Git it would help if you would cancel the NMU.
Unfortunately I observed in Salsa CI that the autopkgtest is failing[1]
(in contrast to my test in local pbuilder). I have no clue how to fix:
autopkgtest [08:21:22]: test autodep8-python3: set -e ; for py in $(py3versions
-r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c
"import gi.overrides.v_sim; print(gi.overrides.v_sim)" ; done
autopkgtest [08:21:22]: test autodep8-python3: [-----------------------
Testing with python3.13:
Traceback (most recent call last):
File "<string>", line 1, in <module>
import gi.overrides.v_sim; print(gi.overrides.v_sim)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/gi/overrides/v_sim.py", line 48, in
<module>
v_sim = get_introspection_module('v_sim')
File "/usr/lib/python3/dist-packages/gi/module.py", line 267, in
get_introspection_module
module = IntrospectionModule(namespace, version)
File "/usr/lib/python3/dist-packages/gi/module.py", line 114, in __init__
repository.require(namespace, version)
~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
gi.RepositoryError: Typelib file for namespace 'xlib', version '2.0' not found
autopkgtest [08:21:22]: test autodep8-python3: -----------------------]
BTW, the autopkgtest was never run before, thought. So it would not be
a regression and thus not preventing testing migration. However, I
would prefer to document this issue and rather de-activate the test
providing some comment than just leaving it as is.
and I'm hereby asking for help in the Python team. Its perfectly
fine for me if you push a fix to Salsa and do some team upload -
no need to NMU.
Kind regards
Andreas.
[1] https://salsa.debian.org/science-team/v-sim/-/jobs/7166447
--
https://fam-tille.de
