> >> I guess this means that the BeOS/Zeta port has to be updated to > >> support the https scheme. It is currently not possible to commit > > > any > >> changes with the current svn client. Anyone on it yet ? Having an updated client would also means faster operation as it uses a different method with less small files. > > I am sorry, but I find this unacceptable. I use BeOS as my only > > operating system and have 4 machines with a total of 8 repositories > > (counting buildtools) using the svn+ssh method plus a few with > > anonymous svn. I have currently three commits ready but I am now > > just > > unable to commit them? Doing such a switch without prior warnings > > so > > that people needing updated binaries for their platform have at > > least a > > chance of continuing working is IMO just very bad practice. I > > usually > > liked the BerliOS hosting because it worked pretty well for me, but > > moves like this are just unacceptable and I have to vote for moving > > hosts ASAP. Especially for an institution hosting open source > > software > > and helping alternative operating systems I cannot believe the > > ignorance displayed by that. I sure hope that this is just another > > temporary thing that has been exceptionally badly communicated. +1. Maybe it's just temporary but if it's not it'd have been nice to be at least notified. > While we are on topic, I'd like to understand if everybody think that > staying with a centralized version control system instead of a > decentralized > like git or mercurial is still a good idea? There is nothing wrong with svn yet. I'm not sure what changing would bring, besides everyone committing to their own repos without anyone knowing what's happenning... OTH I got http://www.selenic.com/mercurial/wiki/ working in Zeta the other day (it's mostly a python script, though I think some tests failed). I need it for OpenSound and XEmacs. François.