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.synopsys.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]
Elmer project: Downloading source code history failed
Hi,
Elmer project on Ohloh has problem (https://www.ohloh.net/p/elmer/enlistments): Step 1 of 3: Downloading source code history (Failed 5 days ago.)
But repository is available without any troubles: https://elmerfem.svn.sourceforge.net/svnroot/elmerfem/trunk
Can the problem with downloading source code history be anyhow related with certificate verification? (HTTPS is used.) There is even special note on SourceForge wiki: http://sourceforge.net/apps/trac/sourceforge/wiki/Subversion#ServerCertificateVerificationFailed
Could you check it?
Thanks
Boris,
The error is: Cannot accept 'svn:log' property because it is not encoded in UTF-8
. Somewhere an accented character has crept into the subversion log and it is preventing us from continuing with the initial fetch. There are administrative tools that will allow you to amend the log entry and remove the problem character. I will try to find just where the problem is though it may exist in several places in the log and each one will need to be addressed separately.
Standby. I'll report back here with what I find...
Thanks!
This is bad news. Because I have no access to upstream svn repo. Also I know that developers will not change anything if we make a request. I added my git mirror in enlistment list. But this is not the solution. Just temporary step to see how it will be processed.
Regards,
Boris
Boris,
If you have administrative access to the git, then you may be able to fix it there. Then you only have to figure out a way to keep the git synchronized with the subversion. Also, the git processing may be more forgiving of minor issues like this. When it's possible, disable the subversion and see how it looks with the git only. That will tell the tale...
Thanks!
If you have administrative access to the git, then you may be able to fix it there.
Also, the git processing may be more forgiving of minor issues like this.
This mirror was made using git-svn. I didn't change locale settings and it should use UTF-8 by default.
Then you only have to figure out a way to keep the git synchronized with the subversion.
Unfortunately I have no access to any remote server now, and I can use only cron on my own laptop.
When it's possible, disable the subversion and see how it looks with the git only. That will tell the tale...
Svn repo was removed from enlistments. Let's see how git repo will be processed.
But I am still not sure that this is good idea to use unofficial mirror. Have you any pros for this?
Also other ideas how to solve the issue are welcome.
Regards,
Boris
Boris,
I'm just making a log from my local copy of the subversion. I can e-mail it to you and have two sets of eyes looking it over for weirdness. It will be a couple of days possibly until we are able to process the git, I fear. If we are lucky the equipment move may only take half a day in which case things may proceed more quickly.
I need to look who is managing the project (if anyone is) and decide how to proceed. If the mirror is closed generally then I'm not too worried about it being unofficial. But, of course, if it is wide open, anybody can scribble what they want there and be a distraction. We'll just have to see... The trick will be how to synch it. A free mirror can be had from github or a number of other sources and if you control it then you can close it to commits, I would think. Establishing a read-only login would be a good way for ohloh to be able to read it for processing. That login may become public but all they can use it for is to read the repository as well. Then you'll use a private write-enabled login to synch the repository to the subversion somehow. Lots of speculation there but I'm sure there's help out there for these questions.
Thanks!
Boris,
Just found (one?) problem revision: r1128 where the Log Message=Esko J�rvinen 24.05.2006
. This is the first sticking point I've found but it may not be the last. Production of the log just died at r1129 svn: REPORT of 'blahblahblah/trunk': 200 OK
and I guessed right that the next earlier revision held the problem.
Useful? Who knows.
Boris,
Also found problems at r446, r298, r117 and r116. So, this isn't a single burp, it's a habit. Two sad�
s and two dsa�
s found. Not sure what they mean but ???.
Now we know.
I need to look who is managing the project (if anyone is) and decide how to proceed. If the mirror is closed generally then I'm not too worried about it being unofficial. But, of course, if it is wide open, anybody can scribble what they want there and be a distraction.
Only I have write access to this git repo [1]. And I don't use master branch for own commits. I use temporary branches [2] to prepare patches for upstream. See [3] for example.
[1] https://github.com/tehnick/elmerfem
[2] https://github.com/tehnick/elmerfem/branches
[3] https://github.com/tehnick/elmerfem/commits/fix-spelling-errors
Regards,
Boris
Boris,
So far, so good. We'll take a look after we're patched back together and running again and see what it looks like then. I'll do some research into fixing the problem if that is even needed in the meantime.
Thanks!
Boris,
Ohloh update completed about 6 hours ago.
Initial fetch finished OK (5565 total commits). Analysis is now at October 11, 2012 on code collected on October 11, 2012 and last commit is at October 10, 2012 - about 16 hours ago.
Can't confirm the specific problem commit messages but I can't see any with odd characters so far. Looks like either the conversion filtered them out or the git processing is more forgiving. Now to deal with the challenge of keeping the git synced with the original subversion...
Thanks!
Hi,
Yesterday I added sync script into cron. Mirror is updated each 2 hours.
Regards,
Boris