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