You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by al...@ps.ge.com on 2004/07/13 09:31:32 UTC
Copy/Move issues
We just started using subversion and can say that it works fantastic, we use
the Tortoise client in combination with Apache.
Currently we have multiple repositories set up and we encounter a few
problems:
1. We want to use the Vendor drop mechanism, what basically means that we
want to branch a tag from one repository into the trunk of another
repository. When trying to do this, it fails with unclear errors. Searching
the net found issue 1313 which describes the fact that subversion cannot do
an inter repository branch. Question is though, can you point out when this
will be in the subversion product or what can we do to resolve the problems
ourselves?
2. We also want to move sources from one repository to another repository
using the move command. When performing this action the target repository
gets corrupted and can only be repaired by the Recover command. First this
seems like a bug but secondly is this move action supported anyway?
regards
Alwin van Driel
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Copy/Move issues
Posted by geoff <ot...@0x29a.org.uk>.
On Fri, 15 Oct 2004 16:36:46 +0900, "Hojin Choi"
<py...@users.kldp.net> wrote:
>Sorry for reminding old mail.
>I have encounterred same problem like below mail.
>
>Isn't it supported yet to copy/move between repository at svn 1.1.0?
Not a copy/move with history.
You can do an OS copy and lose the history. Do an SVN delete in the
source wc and an add in the dest wc, commit both wcs, and you've just
done a move.
I heard a rumour on the Tortoise list that the configuration
TortoiseSVN 1.1.1
SVN 1.1.1
Apache 2.0.52
at least doesn't wedge your repository when you try to do this and
fail.
Anybody know which change fixed this? Which issue described it?
I toured CHANGES on the trunk and found nothing to match.
--
best,
geoff
regrettably the email address above will bounce
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Copy/Move issues
Posted by Hojin Choi <py...@users.kldp.net>.
Sorry for reminding old mail.
I have encounterred same problem like below mail.
Isn't it supported yet to copy/move between repository at svn 1.1.0?
----- Original Message -----
From: "Ben Collins-Sussman" <su...@collab.net>
To: <al...@ps.ge.com>
Cc: "svn-dev-list" <de...@subversion.tigris.org>; <us...@subversion.tigris.org>
Sent: Tuesday, July 13, 2004 11:02 PM
Subject: Re: Copy/Move issues
> On Tue, 2004-07-13 at 04:31, alwin.vandriel@ps.ge.com wrote:
>>
>> 2. We also want to move sources from one repository to another repository
>> using the move command. When performing this action the target repository
>> gets corrupted and can only be repaired by the Recover command. First this
>> seems like a bug but secondly is this move action supported anyway?
>
> No, you cannot copy or move data between repositories. And if you want
> specific answers, you'l have to show us what you mean by "the target
> repository gets corrupted". If you try to run 'svn mv/cp URL1 URL2' and
> the two URLs represent different repositories, you should get a simple
> error. There's nothing that should cause BerkeleyDB to wedge. Show us
> details.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Copy/Move issues
Posted by Ben Collins-Sussman <su...@collab.net>.
On Tue, 2004-07-13 at 04:31, alwin.vandriel@ps.ge.com wrote:
> We just started using subversion and can say that it works fantastic, we use
> the Tortoise client in combination with Apache.
> Currently we have multiple repositories set up and we encounter a few
> problems:
>
> 1. We want to use the Vendor drop mechanism, what basically means that we
> want to branch a tag from one repository into the trunk of another
> repository. When trying to do this, it fails with unclear errors. Searching
> the net found issue 1313 which describes the fact that subversion cannot do
> an inter repository branch. Question is though, can you point out when this
> will be in the subversion product or what can we do to resolve the problems
> ourselves?
Repositories cannot share information or history. I don't think there
are any plans to do this -- not that I'm aware of. You can certainly
always export trees from one repository, re-import it to another. But
it will be no different than just importing a vendor tarball. The
repositories will not refer to one another.
>
> 2. We also want to move sources from one repository to another repository
> using the move command. When performing this action the target repository
> gets corrupted and can only be repaired by the Recover command. First this
> seems like a bug but secondly is this move action supported anyway?
No, you cannot copy or move data between repositories. And if you want
specific answers, you'l have to show us what you mean by "the target
repository gets corrupted". If you try to run 'svn mv/cp URL1 URL2' and
the two URLs represent different repositories, you should get a simple
error. There's nothing that should cause BerkeleyDB to wedge. Show us
details.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Copy/Move issues
Posted by François Beausoleil <fb...@ftml.net>.
Hi !
alwin.vandriel@ps.ge.com wrote:
> We just started using subversion and can say that it works fantastic, we use
> the Tortoise client in combination with Apache.
> Currently we have multiple repositories set up and we encounter a few
> problems:
>
> 1. We want to use the Vendor drop mechanism, what basically means that we
> want to branch a tag from one repository into the trunk of another
> repository. When trying to do this, it fails with unclear errors. Searching
> the net found issue 1313 which describes the fact that subversion cannot do
> an inter repository branch. Question is though, can you point out when this
> will be in the subversion product or what can we do to resolve the problems
> ourselves?
>
> 2. We also want to move sources from one repository to another repository
> using the move command. When performing this action the target repository
> gets corrupted and can only be repaired by the Recover command. First this
> seems like a bug but secondly is this move action supported anyway?
From your descriptions, it looks like you're trying to copy/move files
between two repositories. This is *not* supported at the moment.
I personally cannot answer the "when" question. If you want to try
something, take a look at SVK (search the archives for the link - it's
something like http://svk.elixus.org/ ). This tool works above
Subversion and manages a distributed repository. Might not be exactly
what you're looking for, but it might be a step towards it.
Bye,
François
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Copy/Move issues
Posted by François Beausoleil <fb...@ftml.net>.
Hi !
alwin.vandriel@ps.ge.com wrote:
> We just started using subversion and can say that it works fantastic, we use
> the Tortoise client in combination with Apache.
> Currently we have multiple repositories set up and we encounter a few
> problems:
>
> 1. We want to use the Vendor drop mechanism, what basically means that we
> want to branch a tag from one repository into the trunk of another
> repository. When trying to do this, it fails with unclear errors. Searching
> the net found issue 1313 which describes the fact that subversion cannot do
> an inter repository branch. Question is though, can you point out when this
> will be in the subversion product or what can we do to resolve the problems
> ourselves?
>
> 2. We also want to move sources from one repository to another repository
> using the move command. When performing this action the target repository
> gets corrupted and can only be repaired by the Recover command. First this
> seems like a bug but secondly is this move action supported anyway?
From your descriptions, it looks like you're trying to copy/move files
between two repositories. This is *not* supported at the moment.
I personally cannot answer the "when" question. If you want to try
something, take a look at SVK (search the archives for the link - it's
something like http://svk.elixus.org/ ). This tool works above
Subversion and manages a distributed repository. Might not be exactly
what you're looking for, but it might be a step towards it.
Bye,
François
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Copy/Move issues
Posted by Ben Collins-Sussman <su...@collab.net>.
On Tue, 2004-07-13 at 04:31, alwin.vandriel@ps.ge.com wrote:
> We just started using subversion and can say that it works fantastic, we use
> the Tortoise client in combination with Apache.
> Currently we have multiple repositories set up and we encounter a few
> problems:
>
> 1. We want to use the Vendor drop mechanism, what basically means that we
> want to branch a tag from one repository into the trunk of another
> repository. When trying to do this, it fails with unclear errors. Searching
> the net found issue 1313 which describes the fact that subversion cannot do
> an inter repository branch. Question is though, can you point out when this
> will be in the subversion product or what can we do to resolve the problems
> ourselves?
Repositories cannot share information or history. I don't think there
are any plans to do this -- not that I'm aware of. You can certainly
always export trees from one repository, re-import it to another. But
it will be no different than just importing a vendor tarball. The
repositories will not refer to one another.
>
> 2. We also want to move sources from one repository to another repository
> using the move command. When performing this action the target repository
> gets corrupted and can only be repaired by the Recover command. First this
> seems like a bug but secondly is this move action supported anyway?
No, you cannot copy or move data between repositories. And if you want
specific answers, you'l have to show us what you mean by "the target
repository gets corrupted". If you try to run 'svn mv/cp URL1 URL2' and
the two URLs represent different repositories, you should get a simple
error. There's nothing that should cause BerkeleyDB to wedge. Show us
details.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org