Debian Testing package broken

Brian Warner warner at lothar.com
Sun Dec 25 23:46:50 UTC 2016


On 12/25/16 3:17 PM, Yui Hirasawa wrote:

>    tahoe-lafs: 1.11.0 [master: 04a3e7993f70ac87c208d61f4387a59f5f419367]
>    foolscap: 0.12.0

Ok, cool, those are the versions currently in debian/testing (aka
"Stretch"). When Ramki finishes with the packaging efforts, we should
see those be updated to 1.12.0 and 0.12.5.

>    cryptography: 1.5.3
>    cffi: None [(<type 'exceptions.ImportError'>, 'No module named cffi', ('/usr/lib/python2.7/dist-packages/allmydata/__init__.py', 239, 'get_package_versions_and_locations', '__import__(modulename)'))]
>    six: 1.10.0
>    enum34: 1.1.6
>    pycparser: None [(<type 'exceptions.ImportError'>, 'No module named pycparser', ('/usr/lib/python2.7/dist-packages/allmydata/__init__.py', 239, 'get_package_versions_and_locations', '__import__(modulename)'))]
>    setuptools: 28.7.1
>    idna: 2.1 [according to pkg_resources]

These are the actual errors: cffi and pycparser are missing.

>    Warning: dependency 'cryptography' (version '1.5.3' imported from '/usr/lib/python2.7/dist-packages') was not found by pkg_resources.
>    Warning: dependency 'cffi' (version None imported from None) was not found by pkg_resources.
>    Warning: dependency 'six' (version '1.10.0' imported from '/usr/lib/python2.7') was not found by pkg_resources.
>    Warning: dependency 'enum34' (version '1.1.6' imported from '/usr/lib/python2.7/dist-packages') was not found by pkg_resources.
>    Warning: dependency 'pycparser' (version None imported from None) was not found by pkg_resources.

Those warning messages are misleading: it was actually able to import
cryptography (version 1.5.3) and six (version 1.10.0) and enum34 (1.1.6)
just fine, it's just they weren't installed in a way that lets the
pkg_resources system learn their versions. (I've argued that we should
remove these warnings, because historically they seem to obscure the
actual errors)

The warnings about cffi and pycparser are accurate: it wasn't able to
import them at all.

Debian/testing (Stretch) has "python-cffi" (version 1.7.0) and
"python-pycparser" (version 2.17). So I think the following might make
tahoe start to work for you:

 apt install python-cffi python-pycparser

I think the root problem is that the current tahoe package in Stretch
does not declare a dependency upon python-cffi or python-pycparser. I'm
sure Ramki's current packaging work will fix that when it lands in
unstable (and then eventually gets promoted to testing).

thanks,
 -Brian



More information about the tahoe-dev mailing list