Bay 12 Games Forum

Please login or register.

Login with username, password and session length
Advanced search  

Author Topic: New SVN Repository  (Read 1164 times)

Jonathan S. Fox

  • Bay Watcher
    • View Profile
    • http://www.jonathansfox.com/
New SVN Repository
« on: December 07, 2012, 01:58:45 pm »

So, those who are involved in the Liberal Crime Squad Sourceforge project may have been getting strange emails, possibly including notifications about a series of commits I did to an SVN repository. But this news is relevant to anyone who uses SVN to checkout the LCS source code, whether you commit code back or not. Sourceforge has been upgrading their technology and redesigning aspects of their site, and is slowly migrating projects over to their new codebase. I've gone ahead and submitted the LCS project to be updated to the new technology. As part of this process, they cloned the SVN repository, and we're supposed to use the new one now.

Long story short, there's a new repository with a new URL.

Old And Busted:
http://lcsgame.svn.sourceforge.net/svnroot/lcsgame/trunk

New Hotness:
http://svn.code.sf.net/p/lcsgame/code/trunk

But wait, there's more. If you're a code contributor, they won't let you commit using the url I gave above. Previously, you could use an https url to checkout without logging in; now they demand a login just to checkout if you try to connect securely. Pain in the butt for providing a single URL. Anyway, for contributors needing read/write access, either go here and copy their convoluted-ass svn+ssh unique checkout command for your read/write access, or just substitute https:// for http:// to go secure and login with your Sourceforge username and password. For TortoiseSVN, I get harangued with demands for my password every time I do anything if I use the svn+ssh, so I was an old grump and stuck to the https version. Easy version below.

New Hotness, Read/Write Edition:
https://svn.code.sf.net/p/lcsgame/code/trunk

Sourceforge's admins recommend a fresh checkout of the new repository, though I suspect merely relocating and pointing your existing codebase to the new repository will be fine. I haven't tested it. I suggest a fresh checkout unless you're feeling rebellious.

If anyone is having trouble with the changes, please let me know. I'm not any sort of expert on these things, but I will certainly make an effort to get things straightened out if there are any wrinkles.
« Last Edit: December 07, 2012, 02:07:26 pm by Jonathan S. Fox »
Logged