> -Original Message-
> From: lieven.govae...@gmail.com [mailto:lieven.govae...@gmail.com] On
> Behalf Of Lieven Govaerts
> Sent: vrijdag 8 oktober 2010 19:59
> To: Wolff, Dave
> Cc: users@subversion.apache.org
> Subject: Re: crash report
>
> On Fri, Oct 8, 2010 at 6:32 PM, Wolff, Dave w
On Sat, Oct 9, 2010 at 5:58 PM, Stefan Sperling wrote:
> It sounds like your main problem is local operations in the working
> copy (i.e. disk i/o).
> Could you do another evaluation of Subversion when we start issuing
> beta releases of Subversion 1.7 probably at the end of this year?
> We're tr
On Sat, Oct 9, 2010 at 2:05 PM, Les Mikesell wrote:
> On 10/9/10 12:51 PM, Nico Kadel-Garcia wrote:
>> Yeah, both Subversion and SSH share the flaw of *ALLOWING* such
>> unprotected keys to be stored locally, with no special command line
>> arguments or special settings, and impossible to compile
On Sat, Oct 9, 2010 at 3:05 PM, jehan procaccia wrote:
> Le 09/10/2010 20:40, Nico Kadel-Garcia a écrit :
>>
>> svn+ssh is the most secure, but it conflcts with your desire for LDAP
>> access. The SSH keys normally live under a single user's account, the
>> user who owns the repository, who hsould
On 10/10/10 3:12 PM, Nico Kadel-Garcia wrote:
On Sat, Oct 9, 2010 at 2:05 PM, Les Mikesell wrote:
On 10/9/10 12:51 PM, Nico Kadel-Garcia wrote:
Yeah, both Subversion and SSH share the flaw of *ALLOWING* such
unprotected keys to be stored locally, with no special command line
arguments or spe
Le 09/10/2010 15:39, Nico Kadel-Garcia a écrit :
On Fri, Oct 8, 2010 at 11:15 AM, Bob Archer wrote:
The client should be able to store the credentials if you have it set up to do
so. On windows/mac it is encrypted with OS included libraries. For Linux you
need to set up gnome keyring or
On 10/09/2010 09:23 AM, 肖晗 wrote:
I am just new to subversion and encountered some confusion.
I have set up a svn server on my ubuntu/linux.
After creating an account called "test" under /var/svn(using svnadmin
create /var/svn/test), I checked out the repository under "/home"
directory.
And all
Le 09/10/2010 20:40, Nico Kadel-Garcia a écrit :
svn+ssh is the most secure, but it conflcts with your desire for LDAP
access. The SSH keys normally live under a single user's account, the
user who owns the repository, who hsould have a locked password. You
see why this conflicts with LDAP based
This an initial announcement for my new Subversion-related project:
svn-graph-branches
This tool parses the Subversion log of a repository to generate
a graph of the important events of the project: tag/branches
creation/deletion and their revisions.
Here is an example picture:
http://svn-g
Hi,
I want to authenticate SVN users against the local machine accounts;
the system is Debian Testing. But every time a user tries to
authenticate, he gets:
svn: Commit failed (details follow):
svn: Authentication error from server: SASL(-13): user not found: no
secret in database
What's going on
All my repositories live under /var/lib/svn/.
Let's the output of the following command (on the SVN server):
# svn changed /var/lib/svn/projectA/
is
A PartA/tags/DEV-1.00_RC5/
Now in my post-commit hook I need the following value in a variable (say
EMAIL_URL):
EMAIL_URL=/var/lib/svn/projectA/Pa
On Oct 10, 2010, at 21:34, Tech Geek wrote:
> All my repositories live under /var/lib/svn/.
>
> Let's the output of the following command (on the SVN server):
> # svn changed /var/lib/svn/projectA/
> is
> A PartA/tags/DEV-1.00_RC5/
>
> Now in my post-commit hook I need the following value in
>
> I assume you mean to also pass "-t $TXN" to svnlook in there somewhere.
>
Yes. I just copied the command from the shell prompt although I noticed that
svnlook command works just fine without the "-t $TXN" argument inside the
post-commit hook.
> Or are you asking if there's a simpler way?
Yes
---
Daniel Becroft
On Mon, Oct 11, 2010 at 12:34 PM, Tech Geek wrote:
> All my repositories live under /var/lib/svn/.
>
> Let's the output of the following command (on the SVN server):
> # svn changed /var/lib/svn/projectA/
> is
> A PartA/tags/DEV-1.00_RC5/
>
> Now in my post-commit hook I ne
Daniel,
>That is not possible for SVN to determine, as it does not know *how* you
are serving the repository (HTTP, HTTPS, svn+ssh, svn, >etc). $REPOS will
give you the physical path to the repository, not necessarily the publicly
accessible path.
That not a problem. I can always prefix the protoco
On Oct 10, 2010, at 22:37, Tech Geek wrote:
>> That is not possible for SVN to determine, as it does not know *how* you are
>> serving the repository (HTTP, HTTPS, svn+ssh, svn, etc). $REPOS will give
>> you the physical path to the repository, not necessarily the publicly
>> accessible path.
>
16 matches
Mail list logo
