Geoffrey Alan Washburn wrote:
> Nico Kadel-Garcia wrote:
>> Geoffrey Alan Washburn wrote:
>>> Nico Kadel-Garcia wrote:
>>>> Geoffrey Alan Washburn wrote:
>>>>> Nico Kadel-Garcia wrote:
>>>>>> Geoffrey Alan Washburn wrote:
>>>>>>> I wanted to check here before I wrote something of my own, but
>>>>>>> is anyone aware of a wrapper or some other tool that
>>>>>>> encapsulates the functionality of "svnadmin dump" and preserves
>>>>>>> hooks? I am going to be upgrading my server and want to
>>>>>>> rebuild the numerous repositories it hosts to take advantage of
>>>>>>> improvements on the server side, but it gets kind of tedious
>>>>>>> having to manually deal with each repository's hooks.
>>>>>>
>>>>>> hot-backp.py, I think. It's available in the contribs directory
>>>>>> of the Subversion repository.
>>>>>
>>>>> That appears to be for performing a hotcopy on BDB repositories. As
>>>>> far I as understand, that is not the same thing as doing a
>>>>> repository dump.
>>>>
>>>> It seems to have worked on an FSFS directory today.
>>>
>>> That's besides the point. Or is "svnadmin hotcopy" the same as
>>> "svnadmin dump"? And if so, why does it have two different names?
>>
>> "svnadmin dump" is quite distinct from "svnadmin hotcopy": try it
>> and see!
>
> Okay, so then what, if anything, does you original suggestion have to
> with my original question? I wanted something for "svnadmin dump" not
> "svnadmin hotcopy".
Well, you wanted to "encapuslate the functionality of svnadmin dump and
preserve hooks". A complete hot-backup, with the hooks and conf files,
integrated to another mirror directory seems just the thing.
Do you want to have the svnadmin dump instead for editing reasons, and a
separate process for grabbing hooks and conf files?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Apr 1 04:13:53 2006