On 12 Nov 2012, at 1:42 PM, weasel wrote: > Thanks for the rapid response, but I managed to figure it out. I added some > extra tracing to the syncdb.py file to print out the actual SQL statements. > I then copied and pasted these into a mysql session and got the same error, > so the problem was with MySQL. It turns out that when I removed the > original mysql-server package, the data-files for the baruwa database were > kept, so I removed the package once more, then removed all the mysql data > files from /var/lib/mysql and reinstalled the mysql-server package.
Hmm. > "baruwa-admin syncdb --noinput" now worked but the migrate produced lots of > errors about tables already existing. I wasn't too sure whether this was > expected or not, but I decided to press on regardless. To my surprise, it > looked like it was working (after re-editing the apache stuff) For version 1.1.1 you need to run a fake migration[1] first before you run the actual migration, thats where your errors come from but it should be file. > So I am happily running v1.1.1 and am v impressed so far. Unless there are > pressing reasons, I will not upgrade to 1.1.2, although I could always build > a new VMware image and build a new MailScanner setup side by side, only > swapping over when I am happy things are working There is no pressing reasons[2], 1.1.2 just fixes a few non critical bugs and adds experimental active directory support thats all. [1] http://www.baruwa.org/docs/upgrade.html#id2 [2] http://www.baruwa.org/blog/2012/11/01/baruwa-1.1.2-released/ - Andrew -- www.baruwa.org _______________________________________________ Keep Baruwa FREE - http://pledgie.com/campaigns/12056
