-
Notifications
You must be signed in to change notification settings - Fork 6
/
Copy pathUPDATING
45 lines (29 loc) · 1.33 KB
/
UPDATING
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
This file describes special operations that must be performed for an
upgrade between GNUnet versions. You can obtain version of GNUnet
that you have installed by running
$ gnunetd --version
If no migration procedure is listed for your version, a
data-preserving migration may not be possible. For SVN versions,
you're on your own.
0.8.0a to 0.8.0b
================
Republication of content is recommend (but not strictly required).
0.8.0 to 0.8.0a
===============
Just run gnunet-update. This may take a while.
0.8.0pre0 and 0.8.0pre1 to 0.8.0
================================
Just run gnunet-update.
0.7.3 (and earlier) to 0.8.0pre0
================================
Migration of your datastore maybe possible but the required code has
not been written (we had bigger fish to fry). In order to update, run
gnunet-update as usual. Drop the tables in your old datastore(s) and
delete "$GNUNETD_HOME/data/fs/" and "$GNUNETD_HOME/data/shared/" and
"$GNUNETD_HOME/data/hosts/".
Note that due to the various breaks in backwards-compatibility, peers
running the new version will not connect to peers running 0.7.3 and
older. Check that the hostlists that you are using in your
configuration file are for peers running HEAD.
You may also want to read up on the new gnunet-auto-share tool and
study the namespaces tutorial on the GNUnet webpage.