Code::Blocks Forums
User forums => General (but related to Code::Blocks) => Topic started by: stahta01 on February 29, 2012, 06:11:27 pm
-
http://monitor.berlios.de/berlios-status/ (http://monitor.berlios.de/berlios-status/)
I am not able to get the SVN update to work using http protocol.
Tim S.
-
We had the same some days ago, I don't know for how long.
-
berlios those days is very broken, I even can't access the svn by webSVN. :(
-
berlios those days is very broken, I even can't access the svn by webSVN. :(
webSVN works sometimes and sometimes not.
If it does not work, svn-access via https is also broken.
It looks like they work on their servers.
-
berlios those days is very broken, I even can't access the svn by webSVN. :(
webSVN works sometimes and sometimes not.
If it does not work, svn-access via https is also broken.
It looks like they work on their servers.
What does "they" mean? The berlios administrators?
-
I wish there were an easy way to sync SVN repos between BerliOS and SourceForge. :-(
-
I wish there were an easy way to sync SVN repos between BerliOS and SourceForge. :-(
We can setup one read-only backup subversion server which keeps itself in sync with Berlios just like the git server I'm hosting. That would be handy when Berlios is unstable. :)
-
seems to be working today...
-
I wish there were an easy way to sync SVN repos between BerliOS and SourceForge. :-(
It seems there is a way. As per the following url (pre-revprop-change section) -
http://sourceforge.net/apps/trac/sourceforge/wiki/Subversion
We can use svnsync to sync repos. Do note that I didn't try it.
-
Well, if it continues being too disrupting, there is still the possibility to move the repository to codeblocks.org. This should not be any considerable burden to the server, nor take more than a few mins.
The publicly accessible repo could stay at BerliOS and be synced with the original.
This will of course not solve the issue for a non-developer trying to check out or update, but alas... that's just bad luck. It will solve the issue for the development team, however (... and those are who really need to be able to access the repository daily).
-
(... and those are who really need to be able to access the repository daily).
...as our religion demands us to do... ;D ;D ;D
-
Wouldn't this be a good opportunity to think (yet) again about the use of Berlios, and about moving to a DVCS?
-
The publicly accessible repo could stay at BerliOS and be synced with the original.
Does Berlios allow to use custom pre-revprop-change hook? svnsync won't work without it. Although there are work around to it.
-
Wouldn't this be a good opportunity to think (yet) again about the use of Berlios, and about moving to a DVCS?
Flame war, flame war, flame war attentionnnnnnnnnnnnnnn ...............
-
Does Berlios allow to use custom pre-revprop-change hook? svnsync won't work without it. Although there are work around to it.
Yes, it does and I even asked Yiannis about installing (another) one. But only Yiannis can do it.
-
Does Berlios allow to use custom pre-revprop-change hook? svnsync won't work without it. Although there are work around to it.
Yes, it does and I even asked Yiannis about installing (another) one. But only Yiannis can do it.
Ok. Great. :)