Correctly recreate the database directory during tracker re-initialise The database directory value was being fetched from the tracker config and being appended to the tracker home directory, but the database directory value in the config already has the tracker home prepended which resulted in the database directory being recreated in a nonsensical location. This fix is a bit of a hack, but the relevant code is likely to be removed in v1.6, so it shouldn't be too bad in the short term.

--- a/CHANGES.txt	Fri Jul 04 15:43:22 2014 +0200
+++ b/CHANGES.txt	Sat Jul 12 00:03:05 2014 +1000
@@ -121,6 +121,8 @@
   application/octet-stream whenever 'html' is contained in the string
   (case insensitive). Thanks to Kay Hayen for reporting and helping
   debug this. (Ralf Schlatterbeck)
+- Correctly recreate the database directory when re-initialising a tracker
+  instance. (John Kristensen)
 
 Minor:
 - demo.py usage message improved: explains "nuke" now. (Bernhard Reiter)