ANN: Tahoe-LAFS 1.10.2 released

Fri Jul 31 03:44:43 UTC 2015

-----BEGIN PGP SIGNED MESSAGE-----
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 setup.py trial".

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

allmydata.test.test_runner.BinTahoe.test_path
- -------------------------------------------------------------------------------
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!

-----BEGIN PGP SIGNATURE-----
Version: Mailvelope v0.13.1
Comment: https://www.mailvelope.com

wsFcBAEBCAAQBQJVuu8XCRDRy6KiG82I9gAAKa0QAMt4I0jKoQKt1MjLZE/P
ehUpdAs4iLJjwY5ic7xUE1WOiK29M3taRj4LB9jgGxgrHnGcSus/GzrbBS4q
Difd2hnoA5c6CjxZSAQEvHDQmkFgbrQ5BYyAvSAhhcOvf9YgrMJAxWIqNew0
SdeYbM1qKcWHjGrlnbTea/LMbfC2eRSb4Qri/7Zq1vWTF03Hi5NRbdv0mvd5
SWaJCqQ/SXN+RmC0wd3MnX5e6rhAQV1YWMa3e6HVmaJ5lrxNXHrObsFNB8DY
DSLWE9ebFV78D9yDffhbeSeSvZvfQf9f1+drGfKFnTABUYPoFCr/GRW97Fpd
bYEVcJQByuOwLVKb94TJHN8g4I3oPZyHmoXB0izmv0FvebEjj1NHD1clCR4Q
oh5MuFfMaKvKne5SY65FHB1GKQyOK3alu1LaGWsXIPqJ/Axl/W9RrD31oCoS
dU5M7tEKbgjoDbZPsg2CrOcB0ZU/ed/jrS/A0C4YhbyMJoJRVN9RkMlk1q6k
ubFC1bI80lwiYuOYZjoADel0ZjnhmyrLvaNKBASW4J78iDVKTbme+bYYhJft
FImaSQJFGf8yw1VvvKAPWbjgWpFbEk45BTrqrutJHn7BViXSuo2MVoyr4GJe
g8u16/SGXtf1M76f/PvDCqNxMj6R9O+++gS/++BIuIEdK75jEXo20woTCvqf
nfew
=+ydp
-----END PGP SIGNATURE-----

On Thu, Jul 30, 2015 at 10:57 PM, Brian Warner <warner at lothar.com> 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:
>
>  https://tahoe-lafs.org/source/tahoe-lafs/releases/
>
> 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
> https://github.com/tahoe-lafs/tahoe-lafs.git , 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:
>
>  https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/quickstart.rst
>
> 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:
>
> https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/about.rst
>
> 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.
>
>
> WHAT IS IT GOOD FOR?
>
> 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].)
>
>
> COMPATIBILITY
>
> 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.
>
>
> LICENCE
>
> 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.)
>
>
> INSTALLATION
>
> Tahoe-LAFS works on Linux, Mac OS X, Windows, Solaris, *BSD,
> and probably most other systems. Start with
> "docs/quickstart.rst" [6].
>
>
> HACKING AND COMMUNITY
>
> 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.
>
>
> SPONSORSHIP
>
> 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.
>
> HACK TAHOE-LAFS!
>
> 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].
>
>
> ACKNOWLEDGEMENTS
>
> 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] https://tahoe-lafs.org/trac/tahoe-lafs/browser/NEWS.rst
> [2] https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/known_issues.rst
> [3] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/RelatedProjects
> [4] https://tahoe-lafs.org/trac/tahoe-lafs/browser/COPYING.GPL
> [5] https://tahoe-lafs.org/trac/tahoe-lafs/browser/COPYING.TGPPL.rst
> [6] https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/quickstart.rst
> [7] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
> [8] https://tahoe-lafs.org/trac/tahoe-lafs/roadmap
> [9] https://tahoe-lafs.org/trac/tahoe-lafs/browser/CREDITS
> [10] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Dev
> [11] http://atlasnetworks.us/
> [12] https://leastauthority.com/
> [13] https://tahoe-lafs.org/hacktahoelafs/
> [14] https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/nodekeys.rst
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20150730/5e52caeb/attachment-0001.html>