SVN RELOCATE: SourceForge moves Subversion URLS - Will the fun ever start?
I really don't like to "blog bile" but seriously, SourceForge may have jumped the shark for me. The website does have a certain Vegas billboard charm, circa 1997, but what is going on over there? The Site News is updated (barely) every few months, while important news is hidden on the Site Status Page.
UPDATED: Apparently I'm the only guy who didn't get the message on this.
Basically, a few days ago they upped and change the URLs for Subversion. Suddenly I started getting this uninformative error (Subversion's fault really, more than SF.NET):
Error: PROPFIND of '/svnroot/dasblogce/trunk': Could not resolve hostname `svn.sourceforge.net': The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. (https://svn.sourceforge.net)
John Forsythe figured out that they'd moved the URLs, adding the project name as a sub-sub-domain, providing what value I do not know.
The announcement of this change was buried here. Of course, why didn't I see that? Seems like it would have been better to email all the project owners, or put an announcement on each project page with the new URL.
Either way, you can fix it WITHOUT re-checking out your code by using the rarely used SVN Relocate command, as seen in the screenshot above. You'll get a very frightening warning from Subversion indicating that this is ever so rarely used and you may ruin everything. Say Yes. Crisis averted.
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
SourceForge.net Update: June 2007 Edition
1. Legacy Subversion Access Method Going Away
2. May Project of the Month (POTM): Scorched3D
It's doubly annoying since it means I have to have a custom setup for every project rather than sharing at least the root URL. Bleh.
Hey Scott! I'm from SF.net, and I'm sorry for your frustration. Our Site News and Site Status mechanisms could be more user friendly, for sure.
Thanks for posting a good procedure for moving your working copy, though!
Comments are closed.
Actually, I think they did.
As Co-Admin of Subtext I seem to recall getting at least one email from SourceForge letting us know about the upcoming move... and that was some time ago. Phil and I sent forwarded the announcements about the move to the Subtext team and I personally made the jump several months ago.
Perhaps the email was trapped by a spam filter? Or perhaps they figured there was only enough room for one .NET blog engine on SourceForge! I kid, I kid. :)