tahoe-lafs should depend on more recent setuptools #2744

Closed
opened 2016-03-16 15:55:55 +00:00 by daira · 6 comments
daira commented 2016-03-16 15:55:55 +00:00
Owner
# virtualenv tahoe
# source tahoe/bin/activate
# pip install .
[...]
# tahoe --version-and-path
[...]
pkg_resources.VersionConflict: (setuptools 0.9.8 (/home/davidsarah/tahoe/git/trunk/tahoe/lib/python2.7/site-packages), Requirement.parse('setuptools>=1.0'))
``` # virtualenv tahoe # source tahoe/bin/activate # pip install . [...] # tahoe --version-and-path [...] pkg_resources.VersionConflict: (setuptools 0.9.8 (/home/davidsarah/tahoe/git/trunk/tahoe/lib/python2.7/site-packages), Requirement.parse('setuptools>=1.0')) ```
tahoe-lafs added the
packaging
normal
defect
1.10.2
labels 2016-03-16 15:55:55 +00:00
Brian Warner <warner@lothar.com> commented 2016-03-18 05:24:12 +00:00
Author
Owner

In 141ff17/trunk:

auto_deps: bump to setuptools>=20.3

20.3 is the current version as of today. I'm not really sure what
version we need, but this is better than the previous zetuptoolz "0.6c6"
requirement. Closes ticket:2744.
In [141ff17/trunk](/tahoe-lafs/trac-2024-07-25/commit/141ff17b9109ec886bc80360e5b8c91a636838ef): ``` auto_deps: bump to setuptools>=20.3 20.3 is the current version as of today. I'm not really sure what version we need, but this is better than the previous zetuptoolz "0.6c6" requirement. Closes ticket:2744. ```
tahoe-lafs added the
fixed
label 2016-03-18 05:24:12 +00:00
daira commented 2016-03-18 17:29:56 +00:00
Author
Owner

I think this should depend on a lower version of setuptools that is available as a Debian package.

I think this should depend on a lower version of setuptools that is available as a Debian package.
tahoe-lafs removed the
fixed
label 2016-03-18 17:29:56 +00:00
daira commented 2016-03-18 17:42:31 +00:00
Author
Owner

jessie-backports and stretch have 18.8. Trusty has 3.3, and Vivid has 12.2. cryptography requires >= 11.3. Therefore I think we should require 11.3, so that we can ignore bugs in earlier versions.

(>= 1.0 is sufficient to solve the original problem. I should have included more of the error message so that we would be able to see exactly what depended on 1.0.)

[jessie-backports and stretch have 18.8.](https://packages.debian.org/search?keywords=python-setuptools) [Trusty has 3.3, and Vivid has 12.2.](http://packages.ubuntu.com/search?keywords=setuptools&searchon=names&suite=all&section=all) cryptography requires >= 11.3. Therefore I think we should require 11.3, so that we can ignore bugs in earlier versions. (>= 1.0 is sufficient to solve the original problem. I should have included more of the error message so that we would be able to see exactly what depended on 1.0.)
Brian Warner <warner@lothar.com> commented 2016-03-18 18:31:27 +00:00
Author
Owner

In b8ad8878/trunk:

Reduce setuptools dep to >=11.3

We don't necessarily need this ourselves (__init__.py's version-checking
code is the only thing in tahoe per se that uses setuptools, and our
setup.py's use of setuptools isn't something that install_requires= can
say anything about). But at least one old environment failed because a
sub-dependency needed a newer version than Tahoe asked for. I'm not sure
if this ought to be here, but it may help for a transitional period
until these ancient environments get updated.

closes ticket:2744
In [b8ad8878/trunk](/tahoe-lafs/trac-2024-07-25/commit/b8ad887823f8e0686380efcc41fe4d95ecf2230c): ``` Reduce setuptools dep to >=11.3 We don't necessarily need this ourselves (__init__.py's version-checking code is the only thing in tahoe per se that uses setuptools, and our setup.py's use of setuptools isn't something that install_requires= can say anything about). But at least one old environment failed because a sub-dependency needed a newer version than Tahoe asked for. I'm not sure if this ought to be here, but it may help for a transitional period until these ancient environments get updated. closes ticket:2744 ```
tahoe-lafs added the
fixed
label 2016-03-18 18:31:27 +00:00
daira commented 2016-03-18 19:08:33 +00:00
Author
Owner

LGTM.

LGTM.

Milestone renamed

Milestone renamed
warner added this to the 1.11.0 milestone 2016-03-22 05:03:36 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#2744
No description provided.