apparent serious integrity problem in build system - setuptools bug?

jg71 jg71 at p8d.org
Fri Mar 21 19:16:05 UTC 2014


* jg71 <jg71 at p8d.org> wrote:

> Best case would be (and let's be optimistic here) that tahoe just
> works with pyOpenSSL 0.14, including the new deps on six and
> cryptography.
> 
> Anyway, I'll get back to you after having run some tests.

After having dealt with the new pyOpenSSL situation, running

  tahoe -V

gave this:

allmydata-tahoe: 1.10.0
foolscap: 0.6.4
pycryptopp: 0.6.0.1206569328141510525648634803928199668821045408958
zfec: 1.4.24
Twisted: 13.0.0
Nevow: 0.10.0
zope.interface: unknown
python: 2.7.5
platform: Linux-slackware_14.1-x86_64-64bit_ELF
pyOpenSSL: 0.14
simplejson: 3.3.0
pycrypto: 2.6
pyasn1: 0.1.7
mock: 1.0.1
setuptools: 3.2

Warning: dependency 'cryptography' (version '0.2.2') found by pkg_resources not found by import.
Warning: dependency 'six' (version '1.5.2') found by pkg_resources not found by import.
Warning: dependency 'cffi' (version '0.8.2') found by pkg_resources not found by import.
Warning: dependency 'pycparser' (version '2.10') found by pkg_resources not found by import.

For debugging purposes, the PYTHONPATH was
  None
install_requires was
  ['setuptools >= 0.6c6', 'zfec >= 1.1.0', 'simplejson >= 1.4',
'zope.interface == 3.6.0, == 3.6.1, == 3.6.2, >= 3.6.5', 'Twisted >=
11.0.0', 'foolscap >= 0.6.3', 'pyOpenSSL', 'Nevow >= 0.6.0',
'pycrypto == 2.1.0, == 2.3, >= 2.4.1', 'pyasn1 >= 0.0.8a', 'mock >=
0.8.0', 'pycryptopp >= 0.6.0']
sys.path after importing pkg_resources was
  /usr/bin:
  /usr/lib64/python27.zip:
  /usr/lib64/python2.7:
  /usr/lib64/python2.7/plat-linux2:
  /usr/lib64/python2.7/lib-tk:
  /usr/lib64/python2.7/lib-old:
  /usr/lib64/python2.7/lib-dynload:
  /usr/lib64/python2.7/site-packages:
  /usr/lib64/python2.7/site-packages/PIL:
  /usr/lib64/python2.7/site-packages/gtk-2.0


So I ran 

  python -c "import pkg_resources;print ',\n'.join([d.project_name+': '+d.version for d in set(pkg_resources.require('allmydata-tahoe'))])"

with this output:

Nevow: 0.10.0,
Twisted: 13.0.0,
zbase32: 1.1.5,
pyOpenSSL: 0.14,
pycparser: 2.10,
zope.interface: 4.0.5,
cryptography: 0.2.2,
cffi: 0.8.2,
simplejson: 3.3.0,
pyasn1: 0.1.7,
foolscap: 0.6.4,
pycryptopp: 0.6.0.1206569328141510525648634803928199668821045408958,
pyutil: 1.9.4,
setuptools: 3.2,
mock: 1.0.1,
pycrypto: 2.6,
six: 1.5.2,
allmydata-tahoe: 1.10.0,
zfec: 1.4.24

which looked OK to me so I decided to run

  tahoe debug trial

which passed except these 2 failures:

  [...]

[FAIL]
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/allmydata/test/test_runner.py", line 136, in _cb
    self._check_right_code(lines[1])
  File "/usr/lib64/python2.7/site-packages/allmydata/test/test_runner.py", line 123, in _check_right_code
    self.fail(msg)
twisted.trial.unittest.FailTest: We seem to be testing the code at '/usr',
(according to the source filename '/usr/lib64/python2.7/site-packages/allmydata/__init__.pyc'),
but expected to be testing the code at '/'.
Please run the tests from the root of the Tahoe-LAFS distribution.

allmydata.test.test_runner.BinTahoe.test_import_in_repl
===============================================================================
[FAIL]
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/allmydata/test/test_runner.py", line 126, in test_the_right_code
    self._check_right_code(srcfile)
  File "/usr/lib64/python2.7/site-packages/allmydata/test/test_runner.py", line 123, in _check_right_code
    self.fail(msg)
twisted.trial.unittest.FailTest: We seem to be testing the code at '/usr',
(according to the source filename '/usr/lib64/python2.7/site-packages/allmydata/__init__.pyc'),
but expected to be testing the code at '/'.
Please run the tests from the root of the Tahoe-LAFS distribution.

allmydata.test.test_runner.BinTahoe.test_the_right_code
-------------------------------------------------------------------------------
Ran 1134 tests in 2113.092s

FAILED (skips=5, expectedFailures=3, failures=2, successes=1124)

So, apart from the initial heart-stopping moment, I think we are
still good-to-go despite the fancy stunt by pyOpenSSL devs.

-- 
Feel the magic of Tahoe-LAFS.



More information about the tahoe-dev mailing list