Package: python3-filelock Version: 3.4.2-1 Severity: normal Dear Maintainer,
while the version is 3.4.2 $ python3.10 -c "import filelock;print(filelock.__version__)" 3.4.2 the packaging makes it look like it is version 0.0.0. We have the path /usr/lib/python3/dist-packages/filelock-0.0.0.egg-info, the file PKG-INFO says "Version: 0.0.0", etc. One consequence is $ python3.10 -m pip check virtualenv 20.13.0+ds has requirement filelock<4,>=3.2, but you have filelock 0.0.0. and I think any tool based on pkg_resources will be similarly confused. (I have no local packages for python3.10, only the current debian testing system packages) -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'testing'), (500, 'stable'), (50, 'unstable-debug'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-3-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-filelock depends on: ii python3 3.9.7-1 python3-filelock recommends no packages. python3-filelock suggests no packages. -- no debconf information
