new SVN repository location

[Tobi]

> Hi,
>
> For your information, the berlios svn server is full, ie. no one can commit
> currently. I've sent an e-mail to berlios staff already, so no need to do
> that again.
>
> Hopefully they install a new disk soon.

They still didn't install a new disk and didn't even react to e-mail or bug
reports. Hence we looked for another (temporary) solution.

Fnordia was so kind to set up a SVN server on taspring.clan-sy.com, so that's where primary development will happen until further notice.

Repository URL: https://taspring.clan-sy.com/svn/spring

Only https authentication, even for anonymous checkouts.

If you're a developer, had commit access at berlios and want commit access at this repository too, give me (by private e-mail, forum PM or /msg on IRC) your username (identical to your berlios one to prevent later confusion) and password and I'll restore your access as soon as possible.

The commit mailing list & buildbot hooks are migrated too; they continue to function as before.

One more thing: to switch your local checkout to the new repository you can use 'svn switch --relocate' (for commandline SVN) or the feature with equal functionality on your favorite GUI client.

cheers

Tobi Vollebregt

[Buggi]

"Relocate can only change the repository part of an URL"

That's the error I get when trying to relocate.

[trepan]

This is the line that worked for me:

Code: Select all

 svn switch --relocate "http://svn.berlios.de/svnroot/repos/taspring-linux/" "https://tasprin.clan-sy.com/svn/spring/"

[jcnossen]

buggi, you probably should add /trunk to your relocation address, because the directory you're trying to relocate is also trunk. I had the same problem at first.

[Fnordia]

WebSVN: https://taspring.clan-sy.com/wsvn/listi ... h=%2F&sc=0

[Buggi]

Adding Trunk worked. :D

[Caydr]

Here's another handy one, the Changelog TXT:

https://taspring.clan-sy.com/wsvn/filed ... rev=0&sc=0

[Tobi]

Thanks, added to development links

[Argh]

I looked into crosscompilation today, ie. compiling for a different platform, and it was all pretty easy, so I set up some 'leet' infrastructure.

Spring's buildbot (second column) now crosscompiles spring.exe using mingw after every commit, and uploads the result.

Very handy, methinks, for all testers, tweakers, and coders wanting to verify the builds

[Tobi]

hmm third column now, I modified it a bit (which will probably happen more ). Just look at the column which lists "mingw32" in it's name, or just look in the upload directory...