On Thursday 10 February 2011, Stefan Sperling wrote:
> On Thu, Feb 10, 2011 at 07:02:18PM +0100, Fabian Richter wrote:
> > Am Thu, 10 Feb 2011 11:24:09 -0600
> > schrieb Ryan Schmidt :
> > > On Feb 10, 2011, at 09:59, Stefan Sperling wrote:
> > > >> and can you please add an --force switch to
> > >
-Original Message-
From: Rajesh Saha [mailto:rajeshsaha...@gmail.com]
Sent: Thursday, February 10, 2011 10:46 PM
To: users@subversion.apache.org
Subject: Re: svnadmin create repo/path - Error
Hi
I was trying to create a repository with this command.
>
> Hi
>
> I was trying to create a repository with this command.
>
> svnadmin create --fs-type fsfs newrepo
>
> But, it is giving error as follows.
>
> svnadmin: Repository creation failed
> svnadmin: Creating db lock file
> svnadmin: Can't open file 'newrepo/locks/db.lock': Permission denied
>
>
What the "anon-access = none" option does is remove the ANONYMOUS
mech from the list of SASL mechs offered by svnserve (I see this in
tcpflow). If this mech is present in the mech list, the svn client
does not bother to authenticate even if a valid Kerberos ticket is
available.
If the svn client h
Ryan Schmidt wrote:
[dd]
>
> This looks like http://subversion.tigris.org/issues/show_bug.cgi?id=2930
>
> i.e., you've found the current status quo; there is no better method
> currently available.
>
I have always been told that I am a good tester (i.e. have the
ability to come across bugs),
On Feb 10, 2011, at 23:33, Victor Sudakov wrote:
> I like very much the default output of the FreeBSD diff program.
> So I prefer using "svn diff --diff-cmd=/usr/bin/diff -x --normal"
> instead of just "svn diff".
>
> However, when I put the line "diff-cmd = /usr/bin/diff -x --normal"
> into ~/.
Colleagues,
I like very much the default output of the FreeBSD diff program.
So I prefer using "svn diff --diff-cmd=/usr/bin/diff -x --normal"
instead of just "svn diff".
However, when I put the line "diff-cmd = /usr/bin/diff -x --normal"
into ~/.subversion/config, I get the following error messa
For what it's worth, I have run into the same problem and the only
solution I have found is to switch to a different access method. As
best as I can tell svnserve is simply not an option when trying to set
up a repository with path based authentication when select areas are
flagged inaccessible to
The problem is probably in the following. When anon-access is other
than "none", svnserve does not request authentication for some
important operations like "svn log", and I have found no way to force
it to request authentication. This effectively breaks path based
authorization.
I have found som
On Feb 10, 2011, at 20:43, debu --- Debajit kataki wrote:
> This is an issue only while I try to commit via any GUI client/rep browser.
> Currently I am using Tortoise and I could reproduce it there. Some people
> also saw it in Eclipse which I am yet to reproduce.
>
> Via command line I have
Thanks Ryan for your reply.
Sorry I was NOT clear and let me elaborate it further.
This is an issue only while I try to commit via any GUI client/rep browser.
Currently I am using Tortoise and I could reproduce it there. Some people
also saw it in Eclipse which I am yet to reproduce.
Via command
Thanks guys - I was just reporting a bug, and didn't expect help. It
is much appreciated, and I now have things working.
Ryan - that's why I qualified "up to date" with "per the Synaptic
package manager" I am sorry I didn't specify further, which brings me
to Andy - you were right. 1.6.6 is what'
On Feb 10, 2011, at 15:19, Andy Levy wrote:
> Please be sure to specify the actual version of Subversion you're
> using. "Up to date" could have two meanings here - up to date with
> regard to what's in the Ubuntu 10.04 repository, or up to date with
> regard to Subversion releases. From what I c
On Thu, Feb 10, 2011 at 16:00, Shannon Dillman
wrote:
> Hello there,
>
> I am writing because my Subversion is reporting a situation that it
> feels is a bug. Unfortunately, I am not really a programmer (yet), so
> please accept my apologies in advance for any shortcomings in this
> report. I am
See this FAQ:
http://subclipse.tigris.org/wiki/PluginFAQ#head-73584410a8d4fbad6781c7b16be39f6518410a61
The error usually means that some tool you are using deleted a folder
and then recreated it. The problem is that this deletes the .svn
metadata folder inside it.
SVN 1.7 will solve this proble
Hello there,
I am writing because my Subversion is reporting a situation that it
feels is a bug. Unfortunately, I am not really a programmer (yet), so
please accept my apologies in advance for any shortcomings in this
report. I am also not dead certain that when it says "please report,"
it means
On Thu, Feb 10, 2011 at 07:02:18PM +0100, Fabian Richter wrote:
> Am Thu, 10 Feb 2011 11:24:09 -0600
> schrieb Ryan Schmidt :
> > On Feb 10, 2011, at 09:59, Stefan Sperling wrote:
> >
> > >> and can you please add an --force switch to
> > >> still being able to create Repositories within the path
Hello,
I'm trying to do an svn switch and keep getting an error:
svn switch https://.../services/branches/ementor .
svn: Directory 'ementor' is missing
svn: Directory 'ementor' is missing
[hostname]$
The directory is currently switched to the trunk. The trunk has no ementor
directory.
There i
On Feb 10, 2011, at 09:15, Fabian Richter wrote:
> Why is that a "feature" and can you please add an --force switch to
> still being able to create Repositories within the path of another?
I should add: this check was added to Subversion to prevent people from doing
things that make no sense.
On Feb 10, 2011, at 12:55, Kris Deugau wrote:
>> something like that. And the comparison to mysql DB doesnt make sense,
>> because in a dbms I am able to deklare multiple databases for the same
>> server or "root" dir, thats what is apparently not possible for svn...
>
> Well, when you create a
Fabian Richter wrote:
To be frank: I dont see why I am not able to create nested repos
A Subversion repository, from the point of view of the filesystem it
lives on, is intended to be (mostly) a black box that you interact with
through the SVN repository access layer you've configured.
or
On 2/10/2011 10:19 AM, Fabian Richter wrote:
Am Thu, 10 Feb 2011 13:07:27 -0500
schrieb Bob Archer:
I expect that this all happens inside the repository. A repository's
contents can have whatever folder layout you want. However, the
repositories themselves on the server each need to be peers. Y
Am Thu, 10 Feb 2011 13:07:27 -0500
schrieb Bob Archer :
>
> I expect that this all happens inside the repository. A repository's
> contents can have whatever folder layout you want. However, the
> repositories themselves on the server each need to be peers. You
> can't nest repos nor should you n
> > On Feb 10, 2011, at 09:59, Stefan Sperling wrote:
> >
> > >> and can you please add an --force switch to
> > >> still being able to create Repositories within the path of
> another?
> > >
> > > That's a reasonable request, I think. Not a usual use case but
> why
> > > not?
> >
> > Really? What
Am Thu, 10 Feb 2011 11:24:09 -0600
schrieb Ryan Schmidt :
>
> On Feb 10, 2011, at 09:59, Stefan Sperling wrote:
>
> >> and can you please add an --force switch to
> >> still being able to create Repositories within the path of another?
> >
> > That's a reasonable request, I think. Not a usual u
On Feb 10, 2011, at 09:59, Stefan Sperling wrote:
>> and can you please add an --force switch to
>> still being able to create Repositories within the path of another?
>
> That's a reasonable request, I think. Not a usual use case but why not?
Really? What possible reason could exist for doing
Hello,
A Subversion server with a big repository was inherited to me recently
and I'm trying to figure out its configuration. We are using an old
version that we are going to upgrade as soon as we are confident that
we understand the current configuration and setup.
We have subversion 1.4.3 (r230
On Thu, Feb 10, 2011 at 04:15:16PM +0100, Fabian Richter wrote:
> Hi,
>
> I just recently upgraded to svn 1.6.12 and had to realize
Which version did you upgrade from?
As far as I can tell this behaviour has existed for some time,
since at least 1.5. Did you upgrade from an earlier version which
> I just recently upgraded to svn 1.6.12 and had to realize
>
> svnadmin create
>
> wont let me create Repositories inside directories where have
> already
> repositories been created.
>
> Why is that a "feature" and can you please add an --force switch to
> still being able to create Repositori
Hi,
I just recently upgraded to svn 1.6.12 and had to realize
svnadmin create
wont let me create Repositories inside directories where have already
repositories been created.
Why is that a "feature" and can you please add an --force switch to
still being able to create Repositories within the
Dear Colleagues,
I am trying to setup the following policy: a private repository with
some public paths. Is such configuration supported at all?
The following configuration:
== conf/svnserve.conf:
anon-access = read
auth-access = write
authz-db = authz
== conf/authz:
[/]
@noc =
Jörg Buchberger joerg-buchberger.de> writes:
>
> First of all, thanks for the quick response.
>
> Hmm, perhaps I should mention that the server is windoze (2003) and that
> this is not a normal apache setup but visualsvnserver (2.1.5) - however,
> I tried both - ordinary apache setup and visuals
32 matches
Mail list logo
