Package Details: tahoe-lafs 1.19.0-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: None
Last Packager: micwoj92
Votes: 36
Popularity: 0.000000
First Submitted: 2010-07-23 19:52 (UTC)
Last Updated: 2024-06-02 03:57 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

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.

<deleted-account> 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

<deleted-account> 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.

« First ‹ Previous 1 2 3 4 5 6 Next › Last »