Hi all,
I was wondering what is required to implement an alternative authorization
mechanism (aside from the authz approach) possibly using MySQL or another
database?
I'm aware of setting up Subversion with Apache using mod authz_svn_db.
http://web.fhnw.ch/technik/projekte/i/fruehling09/BieliHal
On Mon, Dec 17, 2012 at 8:17 PM, Aubrey Barnard wrote:
> I am having trouble getting Subversion to work with the Gnome keyring and
> would like some advice on how to troubleshoot the situation. At this point I
> have tried everything I can find (Google, these archives), so I need to find
> how/wh
Hello,
if I co a working copy with -rREV with REV older than HEAD, I am able to get a
lock on any file. But it seems to me, that the lock is never published to the
server as no "svn info URL" shows an existing lock on the file on any working
revision, while the lock is existing in my wc (displa
On Tue, Dec 18, 2012 at 05:14:18PM +, Julian Ruhe wrote:
> Hello,
>
> if I co a working copy with -rREV with REV older than HEAD, I am able to get
> a lock on any file. But it seems to me, that the lock is never published to
> the server as no "svn info URL" shows an existing lock on the fil
On Tue, Dec 18, 2012 at 11:09 AM, Mark Phippard wrote:
> On Mon, Dec 17, 2012 at 8:17 PM, Aubrey Barnard wrote:
>
>> I am having trouble getting Subversion to work with the Gnome keyring and
>> would like some advice on how to troubleshoot the situation. At this point I
>> have tried everything I
On Tue, Dec 18, 2012 at 6:52 AM, Jonathan Holloway
wrote:
> Hi all,
>
> I was wondering what is required to implement an alternative authorization
> mechanism (aside from the authz approach) possibly using MySQL or another
> database?
svn+ssh works pretty well, and avoids the "storing password in
