[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Final line in revision file longer than 64 characters

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: Thu, 24 Jan 2008 17:18:44 -0600

On Jan 24, 2008, at 17:03, Vitus Jensen wrote:

> Am Donnerstag, 24. Januar 2008 schrieb Ulrich Eckhardt:
>> On Thursday 24 January 2008, Lorenz wrote:
>>> have you perhaps created the repository from your workstation and
>>> not
>>> on the server?
> Perhaps, I don't remember.
>>> In that case endianness or end-of-line handling my be the cause for
>>> your problems.
>>> Always create the repository with the svnadmin from the same
>>> distribution your svnserve comes from.
>> Ahem, are you sure? I was under the assumption that the FSFS
>> format [1]
>> was designed to be OS-independent and thus could be copied to any
>> machine.
> fsfs is the format of the db, checked the format some minutes ago.
> I remember that I tried to use the svnserve process first, but
> failed and
> then switched to using file access method. As I used Kubuntu at
> that time
> there may another subversion version be involved: 1.4.0. Perhaps
> 1.4.0
> aren't compatible if one accesses the repository using the file
> method?
> Anyway, the best way to clean up this mess seems to be to setup a new
> repositoty. Is the following correct?
> * dump at the client (where it is successfull)
> * wipe repository
> * create a new repository locally at the server
> * import the dump locally at the server
> * start svnserve process on the server
> * use only method "svn:" in the future
> Dumps are portable, right?

Dumps are portable, yes. But "dump" is an svnadmin command, and as
such it can only be run on the server, and not on the client.

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-25 00:19:21 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.