+If you've been using Laconica 0.5 or lower, or if you've been tracking
+the "darcs" version of the software, you will probably want to upgrade
+and keep your existing data. There is no automated upgrade procedure
+in Laconica 0.6. Try these step-by-step instructions; read to the end
+first before trying them.
+
+0. Download Laconica and set up all the prerequisites as if you were
+ doing a new install.
+1. Make backups of both your database and your Web directory. UNDER NO
+ CIRCUMSTANCES should you try to do an upgrade without a known-good
+ backup. You have been warned.
+2. Shut down Web access to your site, either by turning off your Web
+ server or by redirecting all pages to a "sorry, under maintenance"
+ page.
+3. Shut down XMPP access to your site, typically by shutting down the
+ xmppdaemon.php process and all other daemons that you're running.
+ If you've got "monit" or "cron" automatically restarting your
+ daemons, make sure to turn that off, too.
+4. Shut down SMS and email access to your site. The easy way to do
+ this is to comment out the line piping incoming email to your
+ maildaemon.php file, and running something like "newaliases".
+5. Once all writing processes to your site are turned off, make a
+ final backup of the Web directory and database.
+6. Move your Laconica directory to a backup spot, like "mublog.bak".
+7. Unpack your Laconica 0.6 tarball and move it to "mublog" or
+ wherever your code used to be.
+8. Copy the config.php file and avatar directory from your old
+ directory to your new directory.
+9. Copy htaccess.sample to .htaccess in the new directory. Change the
+ RewriteBase to use the correct path.
+10. Rebuild the database. Go to your Laconica directory and run the
+ rebuilddb.sh script like this:
+
+ ./scripts/rebuilddb.sh rootuser rootpassword database db/laconica.sql
+
+ Here, rootuser and rootpassword are the username and password for a
+ user who can drop and create databases as well as tables; typically
+ that's _not_ the user Laconica runs as.
+11. Use mysql client to log into your database and make sure that the
+ notice, user, profile, subscription etc. tables are non-empty.
+12. Turn back on the Web server, and check that things still work.
+13. Turn back on XMPP bots and email maildaemon. Note that the XMPP
+ bots have changed since version 0.5; see above for details.
+
+If you're upgrading from very old versions, you may want to look at
+the fixup_* scripts in the scripts directories. These will store some
+precooked data in the DB.
+