On Thursday 15 March 2007 17:48, Malcolm Wallace wrote:
I have been trying all day today to persuade either tailor or cvs2darcs to do the conversion, and failed miserably. I believe there is some kind of character-encoding problem causing tailor to misinterpret the contents of the CVS repo, leading to only 16 patches of history, instead of 2393. Meanwhile cvs2darcs gives me a completely empty darcs repo (after a very long time, and lots of warning messages).
FYI: After patching tailor itself to make it run at all, I get 18 patches. :-( The patch was very trivial and has nothing to do with our problems, I guess: --- /home/panne/tailor/vcpx/repository/darcs/__init__.py.~1~ 2007-03-23 14:19:01.000000000 +0100 +++ /home/panne/tailor/vcpx/repository/darcs/__init__.py 2007-03-23 15:01:14.000000000 +0100 @@ -72,7 +72,7 @@ ignored.append('^%s$' % re.escape(sfrelname+'.old')) ignored.append('^%s$' % re.escape(sfrelname+'.journal')) - boring = open(boringname, 'wU') + boring = open(boringname, 'w') boring.write('\n'.join(ignored)) boring.write('\n') boring.close() -----------------------------------------------------------------------------
Does the Hugs CVS repo contain any strange encoding in commit messages? Neither ASCII nor UTF-8 seems to be accepted, whereas Latin-1 is accepted but gives incorrect results.
Hmmm, I can only see a single German umlaut coded in Latin-1... Cheers, S.