RE: [ANNOUNCE] Apache Subversion 1.14.3 released

>Hosting providers such as github, are abandoning Subversion support. >It is really on its last legs: So it's a lot of old, boring technology too, but still used because it just works and it's battle-tested. I studied and deployed SVN for my team 8 years ago, after using it as an user a lot.

RE: Disable svn service temporarily

If you're positive the only way to access the repositories is through svn+ssh, so you have N users that can access, you can group them under a new group ie. "svnusers" and then use the directive "DenyGroups svnusers" under the file /etc/ssh/sshd_config (remember to restart sshd). That would

RE: Regarding details of SVN Cleanup command

Hello, > Can anyone please help me to understand how "SVN Cleanup" command exactly > works? [from TortoiseSVN] >>The image seems a dialog window of TortoiseSVN, but I don't know how it >>implements those options. So I can't answer your question directly. >>If you want to know what it exactly

RE: How to safely back up an svn repository on ubuntu?

If it helps, I use the following one-liner to "svnadmin hotcopy --incremental", so only new revisions are copied each time (the svn-hot-copies target path is a NFS mount, for example, in other box) # find /path/to/your/repos -maxdepth 1 -mindepth 1 -type d -printf "%f\0" | sort -z | xargs -0

RE: svnmucc fails to build from sources

Nevermind. Seeing that /usr/local/lib was included in the compile line as "rpath", I tried moving all existing libsvn_* files from /usr/local/lib to an "old_1.11" directory (they came from the 1.11 compilation) After that, "make" just went fine. Regards, Juanga

svnmucc fails to build from sources

Hello, Build box is an Ubuntu 18.04 where only standard system updates are applied. Built svn 1.11.0 from sources with no problems, now trying to build the latest 1.12.2 is throwing the following error. [...] cd subversion/svnmucc && /bin/bash "/usr/local/src/subversion-1.12.2/libtool"

Re: Removing data from subversion

You could svn export the desired revision to start with, and then make an initial commit to a new repo Regards, Juan Enviado desde BlueMail En 28 nov. 2018, en 12:44, Ahtesham Kazi mailto:ahtesham.k...@gmail.com>> escribió: Greetings, I have read that

RE: locks-test fail when building subversion-1.10.0 from sources under Linux (Ubuntu 16)

Ok, my mistake. >>> SUMMARY: All tests successful. I got “success” for all the tests from “make check” command after compiling svn from sources NOT using the root account. First I tried to ensure the build process was using the “apr” and “apr-util” compiled from the subversion-1.10 sources

RE: locks-test fail when building subversion-1.10.0 from sources under Linux (Ubuntu 16)

Thanks for your input. >> Extract from fails.log: >> [[[ >> svn_tests: E26: Expected error but got SVN_NO_ERROR >> FAIL: lt-locks-test 14: lock/unlock when 'write-lock' couldn't be obtained >> ]]] >That's odd. You can run just that one test: > cd subversion/tests/libsvn_fs > ./fs-test 14

locks-test fail when building subversion-1.10.0 from sources under Linux (Ubuntu 16)

Hello, First time for me building subversion from sources (Linux). I’ve upgraded a server from 1.9 to 1.10 and things seem ok, but I have just one test from “make check” failing. I’m just wondering if it’s a problem or it may be ignored. Followed instructions at