From 8fd0a6a1a9e41e172df6f979a621b05aa70c1938 Mon Sep 17 00:00:00 2001
From: leif <>
Date: Thu, 8 Aug 2013 20:17:36 +0000
Subject: [PATCH] move paragraph, clarify what is signed.

[Imported from Trac: page AdvancedInstall, version 62]
---
 AdvancedInstall.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/AdvancedInstall.md b/AdvancedInstall.md
index 7e28ad5..9878e16 100644
--- a/AdvancedInstall.md
+++ b/AdvancedInstall.md
@@ -116,12 +116,14 @@ from its `tahoe-deps/` directory instead of downloading them from the
 internet. You can also unpack tahoe-deps into the parent directory to share
 it between multiple trees.
 
+Unfortunately, setup.py will still try to connect to the internet even if the `tahoe-deps` directory exists, and if it succeeds and finds newer versions of any dependencies it will likely still download and run them (without any integrity checking). So, for a truly offline build, you currently must run setup.py in an environment where it cannot reach the internet. See #2055.
+
 Alternatively, if you are building from a tarball (either a release tarball
 from <https://tahoe-lafs.org/source/tahoe-lafs/releases/> , or a continually-generated
 current-trunk tarball from <https://tahoe-lafs.org/source/tahoe-lafs/tarballs/> ), you
 can simply download the -SUMO version of the tarball instead of the regular
 one. The "SUMO" tarball includes the current tahoe-deps bundle pre-unpacked
-in the source tree and is signed with the Tahoe-LAFS Release-Signing Key (`E34E 62D0 6D0E 69CF CA41 79FF BDE0 D31D 6866 6A7A`).
+in the source tree. The release versions are signed with the Tahoe-LAFS Release-Signing Key (`E34E 62D0 6D0E 69CF CA41 79FF BDE0 D31D 6866 6A7A`).
 
 The tahoe-deps bundle is updated every once in a while, as new versions of
 the dependent libraries are released, or as Tahoe becomes dependent upon new
@@ -131,8 +133,6 @@ latest. The tahoe-deps bundle contains a README that has a version number.
 
 Besides tahoe-deps, you'll also need a C++ compiler and Python headers. These requirements can be satisfied on a Debian system with "`apt-get install build-essential python-dev`".
 
-Unfortunately, setup.py will still try to connect to the internet even if the `tahoe-deps` directory exists, and if it succeeds and finds newer versions of any dependencies it will likely still download and run them (without any integrity checking). So, for a truly offline build, you currently must run setup.py in an environment where it cannot reach the internet. See #2055.
-
 <a name="point6"></a>
 ## Installing Outside The Source Tree