Forums : Technical Issue Help

Hi there!
Our project stopped updating, about a month ago.
I checked the enlistment and it shows that it failed about a month ago while counting the lines.
Please take a look and fix it if possible!

Thanks in advance!

dfighter

dfighter almost 15 years ago

dfighter,

Apologies for not responding sooner...

The failure is due to a Inconsistent line ending style error in r2128 of the repo in the file Makefile.am. Might be able to get past that error if we could enter an ignore entry into the enlistment, but can't enter such an entry until the update finishes successfully. Catch-22! I will see what we can think of here to solve the problem and report back.

Thanks!

ssnow-blackduck almost 15 years ago

Hi there!
Thanks for taking a look, however I wonder how did this not cause a problem before? That revision was commited over 2 years ago.
Anyhow we are grateful for all your efforts. :)

dfighter almost 15 years ago

dfighter,

I thought that was strange too. Could have been any number of changes in the environment here at ohloh, particularly in the ohcount code. At the moment, I'm re-fetching the enlistment to see if that makes any difference. I have put in an ignore order which hasn't been accepted yet. We'll see what will happen...

Thanks!

ssnow-blackduck almost 15 years ago

dfighter,

Sad news - the re-fetch did not produce different results and the ignore order still hasn't been accepted. Will probably need to refer this problem to a more senior programmer for assistance.

I can confirm, however that the referenced file does have inconsistent line endings with the first 5 being DOS-style line endings (0d 0a) and the next 2 being linux-style line endings (0a) followed by more DOS-style line endings. Still, I don't know why it cares anyway...

Will keep at it.

Thanks!

ssnow-blackduck almost 15 years ago

Alright, thanks for the update!

dfighter almost 15 years ago

Hi there, any further updates regarding this?
Thanks in advance :)

dfighter almost 15 years ago

dfighter,

I will attempt to see if I can get the ignore order to take some sneaky way without performing a successful update (as is ordinarily required...) Summer vacations are running now with the staff stretched thinner than usual so I need to wait my turn at the staffers that are available...

Thanks!

ssnow-blackduck almost 15 years ago

dfighter,

The response I received was not reassuring. I am told we will need to finish one successful fetch before the ignore order can be entered. Looks like a catch-22! Will think some more about this.

Thanks!

ssnow-blackduck over 14 years ago

Ok, so I guess ( seeing how now 4 months passed since the last successful enlistment update ), nothing really worked out that you tried, but I thank all your efforts so far anyways.
I will dive into the svn manual when I wake up and see if and how I can mess with files in older revisions.

dfighter over 14 years ago

dfighter,

Sorry I haven't responded sooner. I have seen at least one other project with this same problem and there are tools around which will allow you to edit the troublesome file to make the line endings fully consistent. This is a problem for some later versions of subversion and not so much for others. I will try to do the research again and find a reference for you but please continue with your explorations and see if you come up with a fix independently. Let me know here once you are ready to try something and I'll be happy to help.

Thanks!

ssnow-blackduck over 14 years ago

dfighter,

I do remember that the solution was some kind of subversion administrator's tool that allows retroactive edits to old commits since a conventional checkout/commit wouldn't change the old commit but just layer a new one on. I'll keep looking.

Thanks!

ssnow-blackduck over 14 years ago

Ok, so today I messed around with this, trying to catch those EOL inconsistencies you mentioned, but couldn't find it. Then suddenly I had the idea of checking the text-base copy of the file in the svn folder and that does have the problem.
I hadn't been able to find it because the file ( like others ) have the SVN eol-style property set to native so when checking out it removes those inconsistencies.
So it would seem that the ohloh SVN client ignores these properties, any chance you can change that?

( In the mean time I am doing an open heart surgery with our repo fixing the inconsistency )

thanks in advance

dfighter over 14 years ago

I've changed the revision in question, removing that line ending inconsistency. Please reschedule our project for update.

Thanks a bunch.

dfighter over 14 years ago

dfighter,

Re-fetch and all following jobs finished OK. Analysis page is at Oct 31 2011 and last commit is at 2011-10-30.

Thanks for all the work!

ssnow-blackduck over 14 years ago