diff --git a/DownloadDebianPackages.md b/DownloadDebianPackages.md index a674f5e..012513a 100644 --- a/DownloadDebianPackages.md +++ b/DownloadDebianPackages.md @@ -1,7 +1,7 @@ # Debian Packages -Tahoe is compatible with various releases of Debian/Ubuntu. There are two +Tahoe-LAFS is compatible with various releases of !Debian/Ubuntu. There are two forms of compatibility: "apt-get installable" and "runs-from-source". Both are pretty easy. If you just want to download a binary package and install it, you'll need the "apt-get installable" kind of compability. @@ -12,8 +12,8 @@ it, you'll need the "apt-get installable" kind of compability. | | | | | | | | | |---|---|---|---|---|---|---|---| -|platform|apt-get installable|deb buildable|tahoe deb available|support debs available|runs-from-source|included in distribution|priority| -|Debian 3.1 "sarge"|no|no|no|no|?| | | +|platform|apt-get installable|deb buildable|tahoe-lafs deb available|dependency debs available|runs-from-source|included in distribution|priority| +|Debian 3.1 "sarge"|no|no|no|no||?|no| | |Debian 4.0 "etch" i386|no|yes|yes|no (missing pycryptopp)|[yes](http://allmydata.org/buildbot/waterfall?show_events=false&builder=etch)| | | |Debian 5.0 "lenny" i386|yes?|yes|yes (use etch)|yes (use etch for zfec/foolscap)|yes?| |*| |Debian 5.0 "lenny" amd64|yes|[yes](http://allmydata.org/buildbot/waterfall?builder=deb-lenny-soultcer&builder=deb-lenny-amd64-eugen)|[yes](http://allmydata.org/debian/dists/lenny/tahoe/binary-all/)|[yes](http://allmydata.org/debian/dists/lenny/main/binary-amd64/)|[yes](http://allmydata.org/buildbot/waterfall?show_events=false&builder=Eugen+lenny-amd64&builder=Soultcer+lenny-amd64)|no| | @@ -35,29 +35,29 @@ it, you'll need the "apt-get installable" kind of compability. |Ubuntu 10.04 "lucid" i386| ? | ? | ? | ? | ? |Tahoe-LAFS v1.6.1|*| |Ubuntu 10.04 "lucid" amd64| ? | ? | ? | ? | ? |Tahoe-LAFS v1.6.1|*| -"apt-get installable" means that it is possible to download a pre-built Tahoe +"apt-get installable" means that it is possible to download a pre-built Tahoe-LAFS binary package from the APT repository on allmydata.org (as well as packages -for any dependencies that are not otherwise available in the Debian/Ubuntu +for any dependencies that are not otherwise available in the !Debian/Ubuntu release), and then run /usr/bin/tahoe to use that installation. Follow the instructions below to edit your /etc/apt/sources.list file. "apt-get -installable" = ("tahoe deb available" AND "support debs available"). +installable" = ("tahoe-lafs deb available" AND "dependency debs available"). -"deb buildable" means that a tahoe .deb package can be built from a source -tree. "tahoe deb available" means the allmydata.org buildbot does this +"deb buildable" means that a tahoe-lafs .deb package can be built from a source +tree. "tahoe-lafs deb available" means the allmydata.org buildbot does this automatically, to populate the APT repository. We do not have automatic builders for all platforms, so there are holes in this table. -"support debs available" means that the allmydata.org APT repository has -debian packages available for everything that Tahoe needs (those which are +"dependency debs available" means that the allmydata.org APT repository has +debian packages available for everything that Tahoe-LAFS needs (those which are not already in that debian release: over time, many of the packages are being added to debian proper, and no longer need to be hosted here). This is -required to make tahoe be "apt-get installable" on any given platform. +required to make Tahoe-LAFS be "apt-get installable" on any given platform. -"runs-from-source" means that it is possible to take a Tahoe source tree +"runs-from-source" means that it is possible to take a Tahoe-LAFS source tree (either from a downloaded tarball or from a darcs checkout) and run `python setup.py build` on it, then run `./bin/tahoe` to use it. This approach is described on the -[http://allmydata.org/source/tahoe/trunk/docs/install.html ""Install Tahoe""] +[http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/install.html ""Install Tahoe-LAFS""] page. The allmydata.org buildbot automatically tests run-from-source on most debian platforms. @@ -83,18 +83,18 @@ sudo apt-get install allmydata-tahoe apt-get will automatically acquire other dependency packages from the same repository (including `foolscap`, `zfec`, `pycryptopp`, and -others). The "tahoe" section contains the Tahoe debian packages, while the -"main" section contains the support libraries. +others). The "tahoe" section contains the Tahoe-LAFS debian packages, while the +"main" section contains the dependency libraries. Note that these `allmydata-tahoe` packages are generated each time the code is changed, and represent the most up-to-date (read "unstable") version available. The usual warnings about no guarantees apply: it might cause your computer to catch fire, might steal your dog, etc. In the future, we will add -a section to the repository that only contains released versions of Tahoe, +a section to the repository that only contains released versions of Tahoe-LAFS, probably called "tahoe-releases". The packages in this section should be more stable than the bleeding-edge packages in the "tahoe" section. -After installing see the [docs/running.html](http://allmydata.org/source/tahoe/trunk/docs/running.html) for how to use it. +After installing see the [docs/running.html](http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/running.html) for how to use it. There are no pre-built packages available for dapper or sarge, as these releases are too old to provide the necessary support packages @@ -124,7 +124,7 @@ Ubuntu Edgy (6.10) has a `python-pysqlite2` for Python 2.4 that has a It appears that the version of Nevow (0.7.0) which shipped with edgy is broken (ubuntu bug [https://bugs.launchpad.net/ubuntu/+source/nevow/+bug/61423 #61423]), -preventing the tahoe node's webserver from running. The symptom is an +preventing the Tahoe-LAFS node's webserver from running. The symptom is an exception at node startup that looks like this: ``` @@ -152,22 +152,22 @@ to pyopenssl-0.6, or refrain from running unit tests. ## Building From Source On Debian Systems If your platform is not listed as "apt-get installable" above, or if you -don't have root access, or simply want to run Tahoe without installing it, +don't have root access, or simply want to run Tahoe-LAFS without installing it, you can use the regular run-from-source procedure described in - . As long as you + . As long as you run this as a normal (non-root) user and don't use "sudo" at any time, this will not modify your system and will not interfere with the normal apt-get tools. Building from a source tree and then symlinking `~/bin/tahoe` to -the tree's `bin/tahoe` executable is a convenient way to use Tahoe +the tree's `bin/tahoe` executable is a convenient way to use Tahoe-LAFS without installing it to your `/usr` directory. -Many of Tahoe's build dependencies can be satisfied by first installing -certain debian packages, and the Tahoe build process will download and build +Many of Tahoe-LAFS's build dependencies can be satisfied by first installing +certain debian packages, and the Tahoe-LAFS build process will download and build many of the others. Please see source:docs/debian.txt for details about -building Tahoe on a debian-based system. The following text is a copy of +building Tahoe-LAFS on a debian-based system. The following text is a copy of source:docs/debian.txt . -The Tahoe build process will download and install many of its dependencies +The Tahoe-LAFS build process will download and install many of its dependencies when you run `make` or `setup.py build`. The base set of functionality that it cannot build on its own are provided by the following debian packages, so you must have these installed before you will be able to @@ -187,8 +187,8 @@ In addition, to use the "`make deb-PLATFORM-head`" target, you will also need the "debchange" utility from the "devscripts" package, and the "fakeroot" package. -To actually run a Tahoe node from a debian package, you will need the following -supporting libraries installed. (again, the authoritative list of packages +To actually run a Tahoe-LAFS node from a debian package, you will need the following +dependencies installed. (again, the authoritative list of packages is in the `Depends:` clause of [misc/sid/debian/control]source:misc/sid/debian/control) @@ -201,18 +201,18 @@ is in the `Depends:` clause of * python-zfec * python-pycryptopp -Even if you don't intend to create a Tahoe .deb package, you can install the +Even if you don't intend to create a Tahoe-LAFS .deb package, you can install the supporting libraries from debian packages to reduce the build-time -download-and-compile work. The Tahoe build process will use any pre-installed +download-and-compile work. The Tahoe-LAFS build process will use any pre-installed libraries it can find, and will download+build everything else. ## Building a Debian Package Please see source:docs/debian.txt for details about building your own debian -packages from a Tahoe source tree. You will need to install the packages +packages from a Tahoe-LAFS source tree. You will need to install the packages described above, including the "devscripts" and "fakeroot" packages, and you will use the `make deb-$PLATFORM-head` target. -Note that this is entirely optional. Tahoe will run just fine from a source +Note that this is entirely optional. Tahoe-LAFS will run just fine from a source tree: creating a debian package is merely a convenience for sysadmins to help -them manage large numbers of Tahoe nodes with established tools like apt-get. +them manage large numbers of Tahoe-LAFS nodes with established tools like apt-get.