Gource cannot recognize cvs2cl logs

[GoogleCodeExporter]

- What's happening?

Using cvs2cl to create new xml log file, as per instructions:
cd <directory>
cvs2cl --chrono --stdout --xml -g-q > proj.xml

(possible complication here, have tried file in default way and also unix2dos 
to no avail)
Copying file to windows machine, running:

gource proj.xml

Output: 

gource: unsupported log format (you may need to regenerate your log file)

It doesn't seem to matter what settings I add...I get the same result.

- What version of the product are you using? On what operating system?

Solaris 5.10 SPARC
CVS v1.11.23
cvs2cl 2.72
Gource 0.37 (Windows)

Any ideas? Example XML output looks like this:

<?xml version="1.0"?>

<changelog xmlns="http://www.red-bean.com/xmlns/cvs2cl/">

<entry>
<date>2008-01-02</date>
<weekday>Wednesday</weekday>
<time>09:52</time>
<isoDate>2008-01-02T14:52:35Z</isoDate>
<author>personname</author>
<file>
<name>folder1/file1</name>
<cvsstate>Exp</cvsstate>
<revision>10.81</revision>
</file>
<msg>message entered here</msg>
</entry>

Thanks all.

Original issue reported on code.google.com by flippe...@gmail.com on 3 Nov 2011 at 8:12

[GoogleCodeExporter]

Hmm. It was able to parse your example above (not on Windows right now but that 
is unlikely to be a factor).

Guessing there is something about the first 'entry' in your actual log file it 
doesn't like.

Original comment by acaudw...@gmail.com on 4 Nov 2011 at 1:01

[GoogleCodeExporter]

Is there actually a new line before the start of the xml tag? It could be that.

Original comment by acaudw...@gmail.com on 4 Nov 2011 at 1:09

[GoogleCodeExporter]

Thanks for taking a look - there's no newline before the <?, I just put that 
for display reasons.

I didn't change anything in the output besides the privacy redactions, so the 
format is the same. I also noticed that I see these things randomly inserted 
throughout the file - is this field standard?

<tagdate>
<tagisodate>2008-01-02T15:10:36Z</tagisodate>
<tagdatetag>THING_20080215</tagdatetag>
</tagdate>

Original comment by flippe...@gmail.com on 4 Nov 2011 at 4:07

[GoogleCodeExporter]

I think so. Gource just ignores them.

Maybe you could email me the start of your actual log file that's not working 
since this example doesn't seem to capture the issue.

Cheers

Andrew

Original comment by acaudw...@gmail.com on 6 Nov 2011 at 1:56

[GoogleCodeExporter]

Update:

So I catted a few lines into a new file. Gource worked. I catted the whole 
thing, and gource worked. I did a diff, and the files were classified to be 
identical. But gource STILL didn't work on the one file, which makes no sense 
at all. They have the same md5sum as well.

So I moved it to a different directory, and it worked. I made a directory with 
a space in the name, and it worked. I then realized that on windows cygwin, 
cygdrive is basically a symlink, so I made one to the aforementioned dir, and 
voila, it failed.

Thus, I conclude that windows gource does not properly handle symlinks, at 
least related to cygwin.

Original comment by flippe...@gmail.com on 17 Nov 2011 at 6:42

[GoogleCodeExporter]

Thanks for working out the issue.

I don't think there is an issue with symlinks, rather the /cygdrive/c/... path 
needs to be converted to a normal windows path (c:\..) to use it with Gource.

I expect you'll find any other non-cygwin specific windows command line tool 
will have the same issue.

Original comment by acaudw...@gmail.com on 18 Nov 2011 at 4:56

[GoogleCodeExporter]

Original comment by acaudw...@gmail.com on 21 Apr 2012 at 8:37

• Changed state: Done