I’ve switched from bzr to darcs for all my version management needs. I’ve decided to also move my already existing projects to darcs. First out is epilicious. From now on the following should be used to get the release and development branches respectively:
% darcs get http://therning.org/magnus_darcs/epilicious
% darcs get http://therning.org/magnus_darcs/epilicious.dev
I decided not to take any history with me, I could have used tailor but decided not to, after all this is a very small project. Also, I’m keeping the old history for the time being, it’s in the old place:
% bzr get http://www.therning.org/magnus_bzr/epilicious/
% bzr get http://www.therning.org/magnus_bzr/epilicious.dev/
I just noticed that BZR 0.8 has been uploaded to Debian Sid. I’ve switched my repos to use that version’s default storage format. This means that you might have problems using my repos with earlier versions… You have been warned.
I had some problems hosting
therning.org. I gave up on getting the development version to push via FTP and settled for missoring using
lftp instead. However, branching from the published mirror failed. I got the following from
bar (version 0.6.2):
% bzr branch http://therning.org/magnus_bzr/epilicious
bzr: ERROR: HTTP Error 406: Not Acceptable
command: '/home/magnus/bin/bzr' 'branch' 'http://therning.org/magnus_bzr/epilicious'
at /usr/lib/python2.4/urllib2.py line 480, in http_error_default()
see ~/.bzr.log for debug information
The file wouldn’t even be handed out to a web browser. I managed to track down the problem, a percent sign ‘%’, in the file name. It turned out the Apache server is using
.htaccess file with the following contents in the a directory turns it off for the directory and all sub-directories:
The made my
bzr mirrors work just fine.