subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy Levy <andy.l...@gmail.com>
Subject Re: Problem with commit
Date Sat, 24 Jul 2010 02:02:40 GMT
That's not always a valid assumption. A plain copy of FSFS is
generally safER than doing the same w/ BDB, but it's not necessarily
100% safe.

On Fri, Jul 23, 2010 at 21:10, Ameet Nanda <ameet.nanda@gmail.com> wrote:
> It is a FSFS repo, so I assumed it would be safe.
>
> On Fri, Jul 23, 2010 at 6:08 PM, Ryan Schmidt
> <subversion-2010b@ryandesign.com> wrote:
>>
>> On Jul 23, 2010, at 17:34, Ameet Nanda wrote:
>>
>> > Additionally, I had checked out a few files from the repository on an
>> > old machine, and then I moved the repository to a new server. I didnot do a
>> > dump and move, just did a tar and scp and untar of the entire repository.
>> > When I try to check in to the new server [with the same hostname] it says
>> >
>> > svn: Commit failed (details follow):
>> > svn: Server sent unexpected return value (500 Internal Server Error) in
>> > response to MKACTIVITY request for '/repos/papers/!svn/act/
>> > a49a699c-96a7-11df-9e8f-654930a0ec4e'
>>
>> That's not the proper procedure for moving a repository, so it's not
>> unexpected that you might run into problems. Does "svnadmin verify" have
>> anything interesting to say about the repository? Is it a BDB or FSFS
>> repository?
>>
>>
>
>

Mime
View raw message