Forums : Technical Issue Help
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
project tn5250j SVN repositories not crawled, failed since 29 days
Good morning, M.W.K.!
I will check now and report back here once I have an idea what may be going on...
Thanks!
M.W.K.
I have come up with an explanation (such as it is) for the failure, but it may not result in an immediate fix.
The error message is Cannot accept 'svn:log' property because it is not encoded in UTF-8
. It has been our working presumption that some element of the subversion log contains some accented character which is not among the limited character set UTF-8. Probably it is contained in a committer's ID or possibly in a comment. We have one other project which is experiencing this problem but have not as yet formulated a fix for it. We'll have further discussions around this problem and let you know once something is decided.
Thanks!
M.W.K.
Also note that this project is blessedly small and as such it may help isolate the problem. That, at least, is helpful.
Thanks!
M.W.K.
With an assist from one of our stalwart developers, I am being led in that same direction. He suggests that most of the improperly encoded repositories that exist today were converted from old CVS repositories using a tool. If the tool wasn't properly configured during conversion, then non-UTF-8 contents could end up in the log.
He also suggests that If project teams are really dedicated to getting on Ohloh, it is possible to use administrative tools to rewrite the Subversion history to remove the improperly encoded log messages. I don't know the details of how this is done, but a couple of people have done this in the past. It's probably a good thing to do anyway -- the problem isn't unique to Ohloh. Anyone who tries to query specific log entries will see the error.
I'll let you know when we can take action on a fix for this (which may depend on a future release of subversion...)
Thanks!
M.W.K.,
Please see https://www.ohloh.net/forums/10/topics/6628 for a discussion of the problem and one solution. Please let me know what you think here and particularly if you need assistance once the problem is solved.
Thanks!