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]
google code svn repository enlistment
I can't seem to add an enlistment for my subversion repository, hosted with google code. I've tried both of these URLs:
http://franklinmath.googlecode.com/svn/trunk/
http://franklinmath.googlecode.com/svn/trunk/Franklin%20Math/
Both of these work fine with the svn -ls command, but everytime I submit them on Ohloh, I get either a blank screen or the message The server did not respond to a 'svn info' command.
Hi bobasaurus,
The explanation is rather complicated, but it boils down to the space in the URL.
A space is a legal Subversion URL character, but 99.9% of the time on Ohloh it's a mistake (people often cut and paste the Subversion checkout command into our form), so Ohloh does not allow spaces in the URL.
What makes this particular case so mysterious is that even though the base URL you provided to Ohloh (/trunk) does not include a space, Ohloh does some manipulation of the URL after you give it to us. We proceed once level deeper into the /trunk/Franklin Math directory, and this does not validate.
That's a long story to explain what is basically a bug in our system. For now, I've worked around it and manually enlisted the URL for your project.
The download is running now, and the report should be ready soon. I'll keep an eye on it.
Thanks,
Robin
Thanks alot. I should start avoiding spaces in paths and filenames in the future, but typing underscores seems like so much effort :) .
I'm having the same exact issue.
Is there any plans to solve this properly in the future? :)
Stian:
I've entered a bug about this on our side.
We are busy migrating servers right now and for the next few weeks. Once that is complete we will be going through our list of bugs and work on getting them fixed.
I'll respond here once I know more :)
