On Jun 26, 2008, at 22:57, Oren Eini (Murphy & Associates) wrote:
> Ryan Schmidt wrote:
>
>> On Jun 26, 2008, at 11:35, Oren Eini (Murphy & Associates) wrote:
>>
>>> I have the following situation:
>>> Src repository on my machine.
>>> Remote repository on another machine, which I don't have local
>>> access to.
>>> I need to copy my local repository to a folder on the remote one,
>>> hopefully with history.
>>> This is an existing repository, so svnsync is not applicable.
>>> Any ideas?
>>
>> "svnadmin dump" your repository.
>> Send the dumpfile to the administrator of the remote repository.
>> Have them "svnadmin load" it into their repository.
>>
>> If the history is expendable, then you don't need the remote
>> administrator's assistance, and you can just "svn export" from your
>> repository and "svn import" into theirs. This will also lose any svn
>> properties however.
>
> I don't have administrator support, just the HTTP access.
> History is important there.
You should get administrator support then. There is no way to load a
dumpfile from your repository into the remote repository via the
client libraries. The only way is with the svnadmin command, which
can only be run with direct file access to the repository.
The other alternative for importing preserving history would be to
check out from the remote repository, then manually re-create and
commit each of your revisions in that repository. This would be a lot
of work since there is no assistance for this in Subversion. You may
be able to automate this, but I don't know if there's already such a
script written.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-27 09:30:22 CEST