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

Re: serious bug: a succession of "svn up" can yield a working copy with local changes

From: Stephen Butler <sbutler_at_elego.de>
Date: Wed, 05 Aug 2009 16:13:56 +0200

Quoting Vincent Lefevre <vincent+svn_at_vinc17.org>:

> On 2009-08-05 08:05:23 -0500, Peter Samuelson wrote:
>> Is there a reproduceable way to get a file in this state in the first
>> place?
>
> I don't know. My files were modified only with the svn client.
>
>> (If the only way is to load a dumpfile, how was the dumpfile
>> generated?)
>
> With svnadmin dump --incremental --deltas.

Hello Vincent,

I believe the question is: how did the files get from CVS into
Subversion? Your text-base file contains the string

   $Id: lplain.bst,v 4.0 2000/01/31 18:11:53 vlefevre Exp $

which must have been generated by CVS (note the ",v" appended to the
filename).

Creating a new file with that string in it, importing into a
Subversion repository, and setting its svn:keywords property has
the desired affect. The file in the working copy contains a
Subversion-style value:

   $Id: alpha 2 2009-08-05 13:28:53Z steve $

and its text-base contains the unexpanded keyword:

   $Id$

So it appears that your file is part of a repository generated
by a CVS-to-Subversion tool. Can you find out which one?

Steve

-- 
Stephen Butler | Software Developer
elego Software Solutions GmbH
Gustav-Meyer-Allee 25 | 13355 Berlin | Germany
fon: +49 30 2345 8696 | mobile: +49 163 25 45 015
fax: +49 30 2345 8695 | http://www.elegosoft.com
Geschäftsführer: Olaf Wagner | Sitz der Gesellschaft: Berlin
Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2380469
Received on 2009-08-05 16:14:16 CEST

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

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