I think it's reasonable for Subversion to enforce its "ownership"
of the repository directory and not support users creating stuff
in it. (Encapsulation is a good thing.) Perhaps the following
layout would do what you want:
mkdir project1
svnadmin create project1/repos
mkdir project1/projectA
s
On Sat, Feb 12, 2011 at 05:31:50PM +0200, Daniel Shahaf wrote:
> Stefan Sperling wrote on Sat, Feb 12, 2011 at 13:59:16 +0100:
> > What I am saying is that the following should error out:
> > $ svnadmin create repos
> > $ cd repos/db
> > $ svnadmin create repos
> > $
>
> Oh, sorry,
Stefan Sperling wrote on Sat, Feb 12, 2011 at 13:59:16 +0100:
> What I am saying is that the following should error out:
> $ svnadmin create repos
> $ cd repos/db
> $ svnadmin create repos
> $
Oh, sorry, Stefan. I missed that it doesn't error when the cwd is
repos/db. (Wh
On Fri, Feb 11, 2011 at 10:10:40PM +0200, Daniel Shahaf wrote:
> Stefan Sperling wrote on Fri, Feb 11, 2011 at 21:10:20 +0100:
> > On Fri, Feb 11, 2011 at 07:16:24PM +0200, Daniel Shahaf wrote:
> > > Stefan Sperling wrote on Thu, Feb 10, 2011 at 16:59:11 +0100:
> > > > But I also think that the che
On 2/11/2011 10:22 AM, Bob Archer wrote:
If I have a project that has child sub-project I really really want them to be in the
same repository. Actually, I put all my projects in the same repository so I can browser
them in "some" repository browser like T-SVN of ViewVC.
Viewvc is perfectly
Stefan Sperling wrote on Fri, Feb 11, 2011 at 21:10:20 +0100:
> On Fri, Feb 11, 2011 at 07:16:24PM +0200, Daniel Shahaf wrote:
> > Stefan Sperling wrote on Thu, Feb 10, 2011 at 16:59:11 +0100:
> > > But I also think that the check for an existing repository should
> > > work within any subdirectory
On Fri, Feb 11, 2011 at 07:16:24PM +0200, Daniel Shahaf wrote:
> Stefan Sperling wrote on Thu, Feb 10, 2011 at 16:59:11 +0100:
> > But I also think that the check for an existing repository should
> > work within any subdirectory of the repository, not just within the
> > top-level directory of the
On Fri, Feb 11, 2011 at 11:26:36AM -0500, Bob Archer wrote:
> Perhaps redmine doesn't require the nested projects to actually point to
> nested repositories?
>
It doesn't.
In redmine, each subproject has some repository location associated with it.
For Subversion, that's a URL. So it can be in
Daniel Shahaf wrote on Fri, Feb 11, 2011 at 19:16:24 +0200:
> The reason? Because the URLs would be ambiguous: what should
> % svn info file://$PWD/path/to/dir/trunk | grep -i 'repository root:'
> print?
(forgot to say that both $PWD and $PWD/path/to are repositories)
Stefan Sperling wrote on Thu, Feb 10, 2011 at 16:59:11 +0100:
> But I also think that the check for an existing repository should
> work within any subdirectory of the repository, not just within the
> top-level directory of the repository.
>
> Can you help by filing a DEFECT issue in our issue tr
> Am Thu, 10 Feb 2011 14:27:17 -0600
> schrieb Ryan Schmidt :
>
> >
> > $ svnadmin create repo1
> > $ svnadmin create repo1/repo2
> > svnadmin: 'repo1/repo2' is a subdirectory of an existing
> repository
> > rooted at 'repo1' $ svnadmin create repo2 $ mv repo2 repo1 $ ls
> repo1
> > README.txt db
> 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 swi
> -Original Message-
> From: Fabian Richter [mailto:fabian.rich...@trust.cased.de]
> Sent: 11 February 2011 09:18
> To: users@subversion.apache.org
> Subject: Re: svnadmin create complains about subrepositories
>
> Am Thu, 10 Feb 2011 14:27:17 -0600
&
Guten Tag Fabian Richter,
am Freitag, 11. Februar 2011 um 10:18 schrieben Sie:
> I also want to grant access to that project to different people than I
> granted to x.
authz-file and it's directory dependant permissions doesn't fit your
needs?
> Funny noone of you mentioned one damn reason why t
Am Thu, 10 Feb 2011 14:27:17 -0600
schrieb Ryan Schmidt :
>
> $ svnadmin create repo1
> $ svnadmin create repo1/repo2
> svnadmin: 'repo1/repo2' is a subdirectory of an existing repository
> rooted at 'repo1' $ svnadmin create repo2
> $ mv repo2 repo1
> $ ls repo1
> README.txtdb h
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
> > >
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
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
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
28 matches
Mail list logo
