From: Brian Warner <warner@allmydata.com>
Date: Tue, 10 Feb 2009 22:00:25 +0000 (-0700)
Subject: NEWS: point out that 'tahoe backup' requires a 1.3.0-or-later client node
X-Git-Tag: allmydata-tahoe-1.3.0~42
X-Git-Url: https://git.rkrishnan.org/Site/Content/Exhibitors/install-details.html?a=commitdiff_plain;h=7bf7922ea197059313c4d1abd25f29f30f3f57b2;p=tahoe-lafs%2Ftahoe-lafs.git

NEWS: point out that 'tahoe backup' requires a 1.3.0-or-later client node
---

diff --git a/NEWS b/NEWS
index 6e1e405b..583373bf 100644
--- a/NEWS
+++ b/NEWS
@@ -63,6 +63,11 @@ been uploaded already, to avoid uploading them a second time. This
 drastically reduces the work needed to do a "null backup" (when nothing has
 changed locally), making "tahoe backup' suitable to run from a daily cronjob.
 
+Note that the "tahoe backup" CLI command must be used in conjunction with a
+1.3.0-or-newer Tahoe client node; there was a bug in the 1.2.0 webapi
+implementation that would prevent the last step (create $target/Latest) from
+working.
+
 ** Large Files
 
 The 12GiB (approximate) immutable-file-size limitation is lifted. This