Forums : Technical Issue Help

Hi,

the KalypsoBASE project update failed some time ago. Could you have a look please?

Kind regards
Gernot

Gernot Belger over 13 years ago

Gernot,

I have run a re-fetch on the enlistment which failed due to the following error: Cannot accept 'svn:log' property because it is not encoded in UTF-8 We have had this problem a few times before and I'll do some research and let you know here what I find.

Thanks!

ssnow-blackduck over 13 years ago

Gernot,

Here's a start for this:

https://www.ohloh.net/forums/10/topics/6628

At the end of the topic Marc gives a reference for how to fix the particular log entry that is hosed. I'm not sure now how to locate it in the first place but that may be all part of the discussion. If you have any trouble with this I can do additional research.

Thanks!

ssnow-blackduck over 13 years ago

Hi,

thanks for the help so far! As this is quite an big, old repository, it might be not so easy to find the exact offending revision(s). Is there any hint by chance in some of you log files?

Actually, the sourceforge repo is a mirror of our true working repository (sourceforge's svn is sadly just too slow to use it directly).

So before trying anything else, i would like to change the enlistment to the true server, and check if we still have the same problems. Would that that a problem for ohloh?

Thanks!

Gernot Belger over 13 years ago

Gernot,

I don't see why you couldn't try the working server to see if it performs better. I have just become aware of a problem with using e-mail addresses as a password so if you require that for access, then it probably won't work that way. Maybe you can establish a throw-away read-only login just for this use and then delete it if it doesn't work out...

Is the working repo also a subversion or do you do a conversion when you sync the two? Might be interesting.

Thanks!

ssnow-blackduck over 13 years ago

Hi,

ok, i will switch the enlistment now. Both repositories are svn, we just dump/import on a regular basis (we didn't get to work svnsync with sourceforge). so naturally we should have the same problem with the other repo, but who knows...

We have anonymous access, so this shouldn't be a problem.

I will observe the update status and will complain again if we still encounter problems.

Cheers
Gernot

Gernot Belger over 13 years ago

Hi again,

strange enough the new enlistment did work, so this actually seems to be a problem with how we replicate the repositories. We will have a look into this one of these days.

By the ways, big Kudos for this fast support, thanks!

Gernot

Gernot Belger over 13 years ago

Gernot,

I would wait for a while before being too enthusiastic. The jobs are still running and could still fail from the same old error. It is certainly true, though, that the error could be introduced in the replication or revealed by it. So much depends on the exact version of subversion that is running on each server. (I've been doing some reading up on it, you see...)

Thanks!

ssnow-blackduck over 13 years ago

Gernot,

The fetch of the new enlistment did work OK. In addition, we have had 3 days of updates with no errors and each day added new commits. Analysis page is at Sep 05 2011 and last commit is at 2011-09-04.

Let me know here if there are additional problems.

Thanks!

ssnow-blackduck over 13 years ago