ANN: Tahoe-LAFS 1.10.2 released

Paul Rabahy prabahy at
Fri Jul 31 03:44:43 UTC 2015

Hash: SHA256

I just synced to the allmydata-tahoe-1.10.2 tag (commit =
befa4babea7f92609654207c164b6d07f3baf92b) and verified that it was
signed properly (key =  E34E 62D0 6D0E 69CF CA41  79FF BDE0 D31D 6866
6A7A). I was able to build successfully and encountered 1 error while
running "python trial".

Traceback (most recent call last):
  File "c:\users\prabahy\documents\github\tahoe-lafs\src\allmydata\test\",
line 171, in _cb
    norm_ver = normalized_version(ver)
  File "c:\users\prabahy\documents\github\tahoe-lafs\src\allmydata\",
line 149, in normalized_version
    return verlib.NormalizedVersion(verlib.suggest_normalized_version(verstr))
  File "c:\users\prabahy\documents\github\tahoe-lafs\src\allmydata\util\",
line 86, in __init__
    self._parse(s, error_on_huge_major_num)
  File "c:\users\prabahy\documents\github\tahoe-lafs\src\allmydata\util\",
line 95, in _parse
    match =
allmydata.PackagingError: could not parse '1.10.2.postdirty.dev0' due
to TypeError: expected string or buffer

- -------------------------------------------------------------------------------
Ran 1182 tests in 680.622s

FAILED (skips=14, expectedFailures=3, errors=1, successes=1164)

Doesn't look like a big deal to me, so overall I'll call it a success!

Version: Mailvelope v0.13.1


On Thu, Jul 30, 2015 at 10:57 PM, Brian Warner <warner at> wrote:

> ANNOUNCING Tahoe, the Least-Authority File System, v1.10.2
> The Tahoe-LAFS team is pleased to announce version 1.10.2 of
> Tahoe-LAFS, an extremely reliable distributed storage system.
> Get it here:
> in the following file (among others):
>  allmydata-tahoe-1.10.2.tar.bz2
> (SHA256=fed5d719c966d9528a45e8ad66e6c8ff3dcb3c06db94775194c7c75566047be7)
> There are also -SUMO variants (which include all necessary
> dependencies). All files are signed by the Tahoe-LAFS Release-Signing
> Key, fingerprint E34E 62D0 6D0E 69CF CA41 79FF BDE0 D31D 6866 6A7A (look
> for detached .asc files next to the tarballs in the directory above).
> This is git revision befa4babea7f92609654207c164b6d07f3baf92b on
> , which is tagged as
> "allmydata-tahoe-1.10.2" (with a GPG-signed tag, using the same
> Release-Signing Key as above).
> Instructions for download and installation are in:
> 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:
> The previous stable release of Tahoe-LAFS was v1.10.1, released
> on June 15, 2015.
> v1.10.2 is a small bugfix release, which fixes a critical
> packaging error that prevented v1.10.1 from building against the
> latest version of the upstream "mock" library. A few small bugs
> were fixed too. See the NEWS file [1] for details.
> With Tahoe-LAFS, you distribute your filesystem across
> multiple servers, and even if some of the servers fail or are
> taken over by an attacker, the entire filesystem continues to
> work correctly, and continues to preserve your privacy and
> security. You can easily share specific files and directories
> with other people.
> In addition to the core storage system itself, volunteers
> have built other projects on top of Tahoe-LAFS and have
> integrated Tahoe-LAFS with existing systems, including
> Windows, JavaScript, iPhone, Android, Hadoop, Flume, Django,
> Puppet, bzr, mercurial, perforce, duplicity, TiddlyWiki, and
> more. See the Related Projects page on the wiki [3].
> We believe that strong cryptography, Free and Open Source
> Software, erasure coding, and principled engineering practices
> make Tahoe-LAFS safer than RAID, removable drive, tape,
> on-line backup or cloud storage.
> This software is developed under test-driven development, and
> there are no known bugs or security flaws which would
> compromise confidentiality or data integrity under recommended
> use. (For all important issues that we are currently aware of
> please see the known_issues.rst file [2].)
> This release should be compatible with the version 1 series of
> Tahoe-LAFS. Clients from this release can write files and
> directories in the format used by clients of all versions back
> to v1.0 (which was released March 25, 2008). Clients from this
> release can read files and directories produced by clients of
> all versions since v1.0. Servers from this release can serve
> clients of all versions back to v1.0 and clients from this
> release can use servers of all versions back to v1.0.
> Except for the new optional MDMF format, we have not made any
> intentional compatibility changes. However we do not yet have
> the test infrastructure to continuously verify that all new
> versions are interoperable with previous versions. We intend
> to build such an infrastructure in the future.
> The new Introducer protocol added in v1.10 is backwards
> compatible with older clients and introducer servers, however
> some features will be unavailable when an older node is
> involved. Please see docs/nodekeys.rst [14] for details.
> This is the nineteenth release in the version 1 series. This
> series of Tahoe-LAFS will be actively supported and maintained
> for the foreseeable future, and future versions of Tahoe-LAFS
> will retain the ability to read and write files compatible
> with this series.
> You may use this package under the GNU General Public License,
> version 2 or, at your option, any later version. See the file
> "COPYING.GPL" [4] for the terms of the GNU General Public
> License, version 2.
> You may use this package under the Transitive Grace Period
> Public Licence, version 1 or, at your option, any later
> version. (The Transitive Grace Period Public Licence has
> requirements similar to the GPL except that it allows you to
> delay for up to twelve months after you redistribute a derived
> work before releasing the source code of your derived work.)
> See the file "COPYING.TGPPL.rst" [5] for the terms of the
> Transitive Grace Period Public Licence, version 1.
> (You may choose to use this package under the terms of either
> licence, at your option.)
> Tahoe-LAFS works on Linux, Mac OS X, Windows, Solaris, *BSD,
> and probably most other systems. Start with
> "docs/quickstart.rst" [6].
> Please join us on the mailing list [7]. Patches are gratefully
> accepted -- the RoadMap page [8] shows the next improvements
> that we plan to make and CREDITS [9] lists the names of people
> who've contributed to the project. The Dev page [10] contains
> resources for hackers.
> Atlas Networks has contributed several hosted servers for
> performance testing. Thank you to Atlas Networks [11] for
> their generous and public-spirited support.
> And a special thanks to Least Authority Enterprises [12],
> which employs several Tahoe-LAFS developers, for their
> continued support.
> If you can find a security flaw in Tahoe-LAFS which is serious
> enough that we feel compelled to warn our users and issue a fix,
> then we will award you with a customized t-shirt with your
> exploit printed on it and add you to the "Hack Tahoe-LAFS Hall
> Of Fame" [13].
> This is the fourteenth release of Tahoe-LAFS to be created
> solely as a labor of love by volunteers. Thank you very much
> to the team of "hackers in the public interest" who make
> Tahoe-LAFS possible.
> Brian Warner
> on behalf of the Tahoe-LAFS team
> July 30, 2015
> San Francisco, California, USA
> [1]
> [2]
> [3]
> [4]
> [5]
> [6]
> [7]
> [8]
> [9]
> [10]
> [11]
> [12]
> [13]
> [14]
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the tahoe-dev mailing list