Package: solo-python
Version: 0.0.27-2
Severity: important
Tags: upstream
Dear Maintainer,
When running the solo command on an updated debian testing, e.g. with
``solo --help`` I get a python traceback:
$ solo --help
Traceback (most recent call last):
File "/usr/bin/solo", line 5, in <module>
from solo.cli import solo_cli
File "/usr/lib/python3/dist-packages/solo/cli/__init__.py", line 17, in
<module>
from solo.cli.key import key
File "/usr/lib/python3/dist-packages/solo/cli/key.py", line 24, in
<module>
import solo.fido2
File "/usr/lib/python3/dist-packages/solo/fido2/__init__.py", line 3, in
<module>
import fido2._pyu2f
ModuleNotFoundError: No module named 'fido2._pyu2f'
My version of python3-fido2 (as mentioned below) is 0.9.1-1 and I see
that upstream there is already an issue[1] for a failure with fido2 version
0.8.1, but I don't think this one has already been reported.
Thanks in advance
[1] https://github.com/solokeys/solo-python/issues/49
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'stable-updates'), (500,
'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-4-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages solo-python depends on:
ii python3 3.9.2-2
ii python3-click 7.1.2-1
ii python3-cryptography 3.3.2-1
ii python3-ecdsa 0.16.1-1
ii python3-fido2 0.9.1-1
ii python3-intelhex 2.1-2.2
ii python3-requests 2.25.1+dfsg-2
ii python3-serial 3.5~b0-1
ii python3-usb 1.0.2-2
solo-python recommends no packages.
solo-python suggests no packages.
-- no debconf information
