Bug#539991: subversion: a succession of svn up can yield a working copy with local changes

2009-09-25 Thread Vincent Lefevre
tags 539991 upstream thanks This is the same issue as: http://subversion.tigris.org/issues/show_bug.cgi?id=1823 -- Vincent Lefèvre vinc...@vinc17.org - Web: http://www.vinc17.org/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.org/blog/ Work: CR INRIA - computer arithmetic /

Bug#539991: subversion: a succession of svn up can yield a working copy with local changes

2009-08-05 Thread Vincent Lefevre
On 2009-08-04 23:06:12 -0500, Peter Samuelson wrote: [Vincent Lefevre] $ svn co file:///home/vinc17/private/svn-...@1952 wd-test $ cd wd-test $ svn pl -v ensl/these/lplain.bst Properties on 'ensl/these/lplain.bst': svn:keywords Id Date $ grep Id ensl/these/lplain.bst % $Id:

Bug#539991: subversion: a succession of svn up can yield a working copy with local changes

2009-08-05 Thread Vincent Lefevre
On 2009-08-05 09:32:59 +0200, Vincent Lefevre wrote: The repository was regenerated from a dump file. When the file was added to the repository, it already had an Id keyword. So, I assume that $Id: lplain.bst,v 4.0 2000/01/31 18:11:53 vlefevre Exp $ is in the dump file (the data are

Bug#539991: subversion: a succession of svn up can yield a working copy with local changes

2009-08-05 Thread Peter Samuelson
[Vincent Lefevre] In fact, canonicalizing the $Id$ keyword would not be the correct solution, because when the Id keyword is removed, one should get the orignal data back (instead of $Id$), here $Id: lplain.bst,v 4.0 2000/01/31 18:11:53 vlefevre Exp $ I don't agree. I think you should

Bug#539991: subversion: a succession of svn up can yield a working copy with local changes

2009-08-05 Thread Vincent Lefevre
On 2009-08-05 11:35:17 -0500, Peter Samuelson wrote: [Vincent Lefevre] In fact, canonicalizing the $Id$ keyword would not be the correct solution, because when the Id keyword is removed, one should get the orignal data back (instead of $Id$), here $Id: lplain.bst,v 4.0 2000/01/31

Bug#539991: subversion: a succession of svn up can yield a working copy with local changes

2009-08-04 Thread Vincent Lefevre
Package: subversion Version: 1.6.3dfsg-1 Severity: grave Justification: causes non-serious data loss [More precisely a working copy can get corrupt due to a succession of updates.] With one of my repositories (regenerated from a dump): $ svn co file:///home/vinc17/private/svn-...@1952 wd-test $

Bug#539991: subversion: a succession of svn up can yield a working copy with local changes

2009-08-04 Thread Peter Samuelson
[Vincent Lefevre] $ svn co file:///home/vinc17/private/svn-...@1952 wd-test $ cd wd-test $ svn pl -v ensl/these/lplain.bst Properties on 'ensl/these/lplain.bst': svn:keywords Id Date $ grep Id ensl/these/lplain.bst % $Id: lplain.bst 1950 2003-12-08 12:30:36Z lefevre $ $ grep Id