Build Failure AttributeError 'module' has no 'version' #2470

New Issue

tahoe-lafs · 2015-07-16T20:51:19Z

BillChappell commented

2015-07-16 20:51:19 +00:00

Building Tahoe 1.10.1 from source on Ubuntu 12.04 LTS.
When I run "python setup.py build", I first see a warning while pyOpenSSL-0.13.1/setup.py is running that “no previously-included files matching ‘*.pyc’ found anywhere in distribution”. The build ends with message “AttributeError: ‘module’ object has no attribute ‘version’”.
I then run "python setup.py build" again and it finishes cleanly, creating a tahoe binary that uploads and downloads via the Web UI (have not tested all modes).

Building Tahoe 1.10.1 from source on Ubuntu 12.04 LTS. When I run "python setup.py build", I first see a warning while pyOpenSSL-0.13.1/setup.py is running that “no previously-included files matching ‘*.pyc’ found anywhere in distribution”. The build ends with message “AttributeError: ‘module’ object has no attribute ‘version’”. I then run "python setup.py build" again and it finishes cleanly, creating a tahoe binary that uploads and downloads via the Web UI (have not tested all modes).

tahoe-lafs added the

labels 2015-07-16 20:51:19 +00:00

tahoe-lafs added this to the undecided milestone 2015-07-16 20:51:19 +00:00

daira commented

2015-07-17 21:39:04 +00:00

“no previously-included files matching '*.pyc' found anywhere in distribution” is a harmless warning.

“AttributeError: 'module' object has no attribute 'version'” is a duplicate of #2465 (when mock 1.1.3 is used).

“no previously-included files matching '*.pyc' found anywhere in distribution” is a harmless warning. “AttributeError: 'module' object has no attribute 'version'” is a duplicate of #2465 (when mock 1.1.3 is used).

tahoe-lafs added

and removed

labels 2015-07-17 21:39:04 +00:00

tahoe-lafs modified the milestone from undecided to 1.10.2

2015-07-17 21:39:04 +00:00

tahoe-lafs closed this issue

2015-07-17 21:39:04 +00:00

BillChappell commented

2015-07-28 23:15:20 +00:00

I am wondering if it makes sense that immediately running "python setup.py build" a second time results in an apparently clean build, generating a tahoe executable in the bin directory which apparently works fine.

daira commented

2015-07-28 23:27:07 +00:00

Replying to BillChappell:

I am wondering if it makes sense that immediately running "python setup.py build" a second time results in an apparently clean build, generating a tahoe executable in the bin directory which apparently works fine.

That's because the version of mock that will be downloaded is (unfortunately) nondeterministic.

Replying to [BillChappell](/tahoe-lafs/trac-2024-07-25/issues/2470#issuecomment-97935): > I am wondering if it makes sense that immediately running "python setup.py build" a second time results in an apparently clean build, generating a tahoe executable in the bin directory which apparently works fine. That's because the version of `mock` that will be downloaded is (unfortunately) nondeterministic.

Sign in to join this conversation.