Package Details: tahoe-lafs 1.17.1-1

Git Clone URL: https://aur.archlinux.org/tahoe-lafs.git (read-only, click to copy)
Package Base: tahoe-lafs
Description: Secure, decentralized, and fault-tolerant storage system.
Upstream URL: https://tahoe-lafs.org/trac/tahoe-lafs
Keywords: distributed filesystem i2p
Licenses: GPL, custom
Submitter: None
Maintainer: fungible
Last Packager: fungible
Votes: 36
Popularity: 0.013767
First Submitted: 2010-07-23 19:52 (UTC)
Last Updated: 2022-03-23 10:20 (UTC)

Latest Comments

jomocu commented on 2020-01-23 22:58 (UTC) (edited on 2020-01-23 22:58 (UTC) by jomocu)

Manjaro :: failed to verify integrity or prepare python2-foolscap package :: failed to verify integrity or prepare tahoe-lafs package

GI_Jack commented on 2020-01-07 20:08 (UTC)

I am disowning this because python2

skydrome commented on 2019-11-16 02:38 (UTC)

you should be able to depend on python2-zfec now

GI_Jack commented on 2018-09-01 01:23 (UTC)

dependency replace python2-crypto with python2-pycryptodome

skydrome commented on 2018-08-09 20:16 (UTC)

for the 1.13.0 release im afraid packaging in some new dependencies is currently a nightmare. I recommend virtualenv and pip to install tahoe-lafs at the moment

blx32 commented on 2017-07-29 16:59 (UTC)

gpg --keyserver pgp.mit.edu --recv-keys BDE0D31D68666A7A

talentus commented on 2017-01-22 16:56 (UTC)

Version 1.12.1 seems to require python2-foolscap >= 0.12.6

elvetemedve commented on 2016-12-04 13:08 (UTC)

python2-crypto >=2.5 is required to run it. See below. $ tahoe create-client Traceback (most recent call last): File "/usr/bin/tahoe", line 6, in <module> from pkg_resources import load_entry_point File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3017, in <module> @_call_aside File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3003, in _call_aside f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3030, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 659, in _build_master ws.require(__requires__) File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 967, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 853, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'pycrypto!=2.2,!=2.4,>=2.1.0' distribution was not found and is required by tahoe-lafs

skydrome commented on 2015-08-17 15:12 (UTC)

added now

grawity commented on 2015-08-16 13:42 (UTC)

Curious why this package doesn't verify the tarballs' PGP signatures.

skydrome commented on 2015-07-31 18:00 (UTC)

python2-foolscap 0.8.0 - http://paste.debian.net/plain/287921

skydrome commented on 2015-07-29 01:18 (UTC)

https://tahoe-lafs.org/trac/tahoe-lafs/changeset/dc7297d0daf5d2a8928c4adb2decb1cbecb51c34

2bluesc commented on 2015-06-18 18:34 (UTC)

@skydome, I just want tahoe-lafs to have a maintainer, so I'm content to sit on the side lines. Thanks for taking ownerhsip. :)

skydrome commented on 2015-06-18 13:24 (UTC)

@2bluesc with aur4 we can add multiple persons for git push permissions if you still want

skydrome commented on 2015-06-18 13:23 (UTC)

ok all updated, youll notice the dep: python2-foolscap>=0.8.0 https://bugs.archlinux.org/task/45376 we'll have to wait for an Arch TU to update this or youll have to do it yourself manually.

fauno commented on 2015-06-18 12:15 (UTC)

ok i've disowned it :)

skydrome commented on 2015-06-17 20:05 (UTC)

I can do it if you want also

2bluesc commented on 2015-06-16 17:21 (UTC)

@fauno I can take it over until a more fitting maintainer surfaces, I may not be the best person long term.

fauno commented on 2015-06-16 14:16 (UTC)

@2bluesc do you want to maintain it? i never got the time to really use it

2bluesc commented on 2015-06-16 05:10 (UTC)

tahoe-1.10.1 was released @ https://tahoe-lafs.org/source/tahoe-lafs/releases/ From the release email: The previous stable release of Tahoe-LAFS was v1.10.0, released on May 1, 2013. v1.10.1 is mostly a bugfix release, but also improves the web-based user interface, adds public-key authentication to the SFTP frontend, improves the behavior of "tahoe cp -r", and offers more control over IP address autodetection. Preliminary (CLI-based) OS-X packages have been added. Over 75 bugs have been fixed. See the NEWS file [1] for details. [1] https://tahoe-lafs.org/trac/tahoe-lafs/browser/NEWS.rst

ammon commented on 2015-05-25 16:41 (UTC)

It should depend on python2-service-identity

daira commented on 2014-12-23 01:48 (UTC)

This will be fixed upstream in Tahoe-LAFS v1.11. (I don't recommend taking the upstream fix for Arch; it's complicated and needs more testing.) Also see https://bitbucket.org/pypa/setuptools/issue/310/document-the-backward-incompatible-pep-440 , which explains how to work around this problem for other applications.

skydrome commented on 2014-12-23 00:14 (UTC)

its not just tahoe-lafs getting affected, setuptools trac is also full of complaints of other software breakage, thus the daily minor version updates to setuptools to "fix" specific issues, but tahoe-lafs still affected. I think we can agree that tahoe-lafs shouldnt need to be changed here, but setuptools changed to allow old behavior.

daira commented on 2014-12-22 21:17 (UTC)

Here's the upstream ticket describing the setuptools breakage: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2354

daira commented on 2014-12-22 21:16 (UTC)

Well, apparently I'm wrong because there has been an incompatible change to setuptools that totally changes the semantics of requirements strings (from disjunctive to conjunctive!) That sucks; I don't know how we're going to work around the breakage it will cause. But the patch looks like the best workaround currently available. (PKGBUILD should probably still be specifying more precise minimum versions for dependencies other than python2-mock and python2-zope-interface.)

daira commented on 2014-12-22 17:50 (UTC)

Note that if "pip list | grep pycrypto" is showing version 2.6.1 but you're getting the "pkg_resources.DistributionNotFound: pycrypto==2.1.0,==2.3,>=2.4.1" error, that can only be because the imported Crypto module is not the same one found by pip. I am almost certain that changing _auto_deps.py to say "pycrypto >= 2.4.1" will not help; if it appears to do so then it's because something else changed as well. To debug which pycrypto is actually getting imported, do: tahoe --version-and-path

daira commented on 2014-12-22 17:44 (UTC)

These changes: - "zope.interface == 3.6.0, == 3.6.1, == 3.6.2, >= 3.6.5", + "zope.interface >= 3.6.5", [...] - "pycrypto == 2.1.0, == 2.3, >= 2.4.1", + "pycrypto >= 2.4.1", should not be necessary. The correct fix is to have 'python2-crypto>=2.4.1' in the depends field of PKGBUILD. Note that upstream master does allow a --nodaemon argument (this was added since Tahoe-LAFS v1.10), but it does not imply --umask=0077 . If you think that it should, please file an upstream bug at tahoe-lafs.org.

commented on 2014-12-22 16:06 (UTC)

Thank you, both!

fauno commented on 2014-12-22 12:39 (UTC)

done, thanks!

2bluesc commented on 2014-12-22 07:36 (UTC)

I ran in to the same problem as @archaurwiki. Posted an updated PKGBUILD that applies a patch that WFM(tm) @ https://gist.github.com/2390247e82e42d2b2ac1

commented on 2014-12-19 04:06 (UTC)

A new error prevents tahoe from starting. This also appears with the tahoe-lafs-i2p package: $ tahoe start Traceback (most recent call last): File "/usr/bin/tahoe", line 6, in <module> from pkg_resources import load_entry_point File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 2912, in <module> working_set = WorkingSet._build_master() File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 550, in _build_master return cls._build_from_requirements(__requires__) File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 563, in _build_from_requirements dists = ws.resolve(reqs, Environment()) File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 742, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: pycrypto==2.1.0,==2.3,>=2.4.1 This error is produced with both a previously running install and a fresh install on both the same and a different machine. I have tried the install/uninstall/reinstall process through the various recent python2-setuptools upgrades with hopes that the solution would be easy. Alas, there hasn't been one. $ pip/pip2 list | grep pycrypto both show version 2.6.1 installed.

thedod commented on 2014-08-11 20:49 (UTC)

From my experience, darcsver and setuptools_darcs are also dependencies

carstene1ns commented on 2014-01-19 18:24 (UTC)

The dependency 'python2-argparse' can be removed, argparse is part of python 2.7 already.

GI_Jack commented on 2013-12-28 22:13 (UTC)

Dependency `setuptools' of `tahoe-lafs' does not exist.

ericthefish commented on 2013-10-01 10:57 (UTC)

python2-setuptools should be a dependency

fauno commented on 2013-09-13 13:48 (UTC)

adopted and packaged for Parabola :)

krevedko commented on 2013-06-02 17:39 (UTC)

Sorry, i've forgot. Thanks for notification! Now everything updated.

StonedArchHead commented on 2013-06-02 10:34 (UTC)

I was just wondering, can anyone update this package? This package is still offering v1.9.2, but v1.10.0 has been out for exactly a month now! Yeah, I know I can just download the latest tahoe-lafs release and build it myself, but I like keeping everything up-to-date automatically through yaourt/pacman instead of remembering to manually re-build everything on my system. :P

Shardz commented on 2013-03-02 03:44 (UTC)

pythonmock dependency should be replaced with python2-mock

zoidberg_md commented on 2013-02-20 15:07 (UTC)

pycrypto dependency should be replaced by python2-crypto

lenzenmi commented on 2012-03-13 22:40 (UTC)

python2-distribute should be a dependency. Tahoe will not start without it.

dgbaley27 commented on 2012-02-22 22:03 (UTC)

Please replace the pyasn1 dependency with python-pyasn1 or python2-pyasn1 as appropriate.

jtang commented on 2012-01-09 10:14 (UTC)

as far as I know, foolscap needs updating to as twistd got upgraded to 11.1 which breaks foolscap 0.6.1

commented on 2012-01-05 21:49 (UTC)

The testsuite upon installation failed for me. I downgraded the package 'twisted' to 11.0.0-1 using http://arm.konnichi.com/2011/09/15/$repo/os/$arch/ and then the installation worked. This worked both for 32bit and 64bit. The failed tests are: test_failure, test_system, test_key_gen_service, failing with: SendBanana.sendFailed: [Failure instance: Traceback: <type 'exceptions.AttributeError'>: 'Broker' object has no attribute 'write' /usr/lib/python2.7/site-packages/foolscap/slicers/root.py:107:send ... more left out ...

npouillard commented on 2011-09-14 05:38 (UTC)

We advise people to quickly upgrade to this new version of Tahoe-LAFS 1.8.3. The official announce will be soon visible from Tahoe-LAFS homepage.

jtang commented on 2011-01-24 21:55 (UTC)

after updating foolscap (rolled my own package) to 0.6 some of the tests pass, but sadly twisted is too new for tahoe-lafs for now. but luckily tahoe-lafs 1.8.2 is due out in a week or two which i hope this incompatibility will be fixed.

jtang commented on 2011-01-24 21:36 (UTC)

I'm not 100% sure of this, but tahoe-lafs 1.8.1 needs foolscap 0.6 or newer, i think the current dependancy in the repos is 0.5, this causes the tests to fail on my freshly installed system. i will try and test with foolscap 0.6

strephil commented on 2010-12-07 17:18 (UTC)

v.1.8.1 was realesed Sun Nov 28

commented on 2010-09-24 10:11 (UTC)

ANNOUNCING Tahoe, the Least-Authority File System, v1.8.0 The Tahoe-LAFS team is pleased to announce the immediate availability of version 1.8.0 of Tahoe-LAFS, an extremely reliable distributed storage system. Get it here: http://tahoe-lafs.org/source/tahoe/trunk/docs/quickstart.html Tahoe-LAFS is the first distributed storage system to offer "provider-independent security" — meaning that not even the operators of your storage servers can read or alter your data without your consent. Here is the one-page explanation of its unique security and fault-tolerance properties: http://tahoe-lafs.org/source/tahoe/trunk/docs/about.html The previous stable release of Tahoe-LAFS was v1.7.1, which was released July 18, 2010 [1].