tahoe .deb cannot be installed on hardy: simplejson dependency is too new #555

Closed
opened 2008-12-07 21:28:06 +00:00 by warner · 3 comments

Also, our tahoe .deb can't be installed on gutsy, because the python-setuptools dependency is too new.

Current trunk (source:_auto_deps.py) specifies that tahoe requires setuptools >0.6c7, while gutsy has 0.6c6 (and hardy has 0.6c8). It also specifies that tahoe requires simplejson-1.8.1 (because of ticket #543), but gutsy has 1.7.1 and hardy has 1.7.3 .

We need to be able to install tahoe on debian systems. We can drop support for older releases if necessary, but it must at least install on the most recent LTS release (which is currently hardy). That means we must either refrain from depending upon packages that are newer than the ones provided by hardy, or we have to build hardy-compatible newer versions of their .debs and host them on the same APT repository as our tahoe .debs

Also, our tahoe .deb can't be installed on gutsy, because the python-setuptools dependency is too new. Current trunk (source:_auto_deps.py) specifies that tahoe requires setuptools >0.6c7, while gutsy has 0.6c6 (and hardy has 0.6c8). It also specifies that tahoe requires simplejson-1.8.1 (because of ticket #543), but gutsy has 1.7.1 and hardy has 1.7.3 . We need to be able to install tahoe on debian systems. We can drop support for older releases if necessary, but it must at least install on the most recent LTS release (which is currently hardy). That means we must either refrain from depending upon packages that are newer than the ones provided by hardy, or we have to build hardy-compatible newer versions of their .debs and host them on the same APT repository as our tahoe .debs
warner added the
packaging
critical
defect
1.2.0
labels 2008-12-07 21:28:06 +00:00
warner added this to the 1.3.0 milestone 2008-12-07 21:28:06 +00:00

Here is the history of changes to our install_requires on setuptools. (Note that this is different from our setup_requires.)

changeset:83b5f5ad520ed28d -- 2008-11-21: >= 0.6c7

changeset:68f38f241b64176e -- 2008-11-20: >= 0.6c8 because 0.6a9 can't parse requirements with dots in them like zope.interface

changeset:0c39ab90fa3ce28e -- 2008-04-10: >= 0.6a9, because we realized that we require >= 0.6c8 to build, but only >= 0.6a9 to run

changeset:85602d190d401a4f -- 2008-04-10: add the requirement on setuptools at run-time, with >= 0.6c8, presumably just because that's what I used at the time

So we definitly need some version which is > 0.6a9, since 0.6a9 can't parse zope.interface. I will try 0.6c6 next.

Here is the history of changes to our `install_requires` on `setuptools`. (Note that this is different from our `setup_requires`.) changeset:83b5f5ad520ed28d -- 2008-11-21: `>= 0.6c7` changeset:68f38f241b64176e -- 2008-11-20: `>= 0.6c8` because `0.6a9` can't parse requirements with dots in them like `zope.interface` changeset:0c39ab90fa3ce28e -- 2008-04-10: `>= 0.6a9`, because we realized that we require `>= 0.6c8` to build, but only `>= 0.6a9` to run changeset:85602d190d401a4f -- 2008-04-10: add the requirement on `setuptools` at run-time, with `>= 0.6c8`, presumably just because that's what I used at the time So we definitly need some version which is `> 0.6a9`, since `0.6a9` can't parse `zope.interface`. I will try `0.6c6` next.

changeset:9fba0288928e034e -- install_require setuptools >= 0.6c6

changeset:9fba0288928e034e -- install_require `setuptools >= 0.6c6`

Okay I believe this ticket is fixed by changeset:9fba0288928e034e and changeset:8e22556e66a6d948. This breaks the dapper buildslave, but that's a different ticket (#534).

Okay I believe this ticket is fixed by changeset:9fba0288928e034e and changeset:8e22556e66a6d948. This breaks the dapper buildslave, but that's a different ticket (#534).
zooko added the
fixed
label 2008-12-09 14:03:41 +00:00
zooko closed this issue 2008-12-09 14:03:41 +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#555
No description provided.