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

Re: Bug? "svn up" gets confused if repo has a property change, and the file was rm'd from the wc.

From: Ivan Zhakov <chemodax_at_gmail.com>
Date: 2005-10-07 10:32:59 CEST

On 10/7/05, Peter N. Lundblad <peter@famlundblad.se> wrote:
> On Fri, 7 Oct 2005, Aleksey Nogin wrote:
>
> > On 06.10.2005 23:20, Peter N. Lundblad wrote:
> >
> > > On Thu, 6 Oct 2005, Aleksey Nogin wrote:
> > >
> > >
> > >>I just came across the following unfortunate problem:
> > >>
> > >>A recent commit have changed the properties (svn:mime-type was removed)
> > >>on a file "foo". Meanwhile a wc that has not yet updated to that
> > >>revision had the file "foo" removed (with "svn rm --force"). Now I see
> > >>the following when doing "svn up" in that wc:
> > >>
> > >>svn: In directory 'xyz'
> > >>svn: Error processing command 'set-timestamp' in 'xyz'
> > >>svn: Can't set access time of 'xyz/foo': No such file or directory
> > >>
> > >
> > > I can't seem to reproduce this with 1.3.x. Can you post a complete recipe
> > > so we know that we do the same things?
> >
> > % svnadmin create /tmp/test
> >
> ...
> Strange. I've tried reproducing using latest trunk, latest 1.2.x and
> 1.2.0 without success. I'm on debian testing. Maybe someone else can
> reproduce?
I have reproduced this with svn 1.2.0, but only if 'use-commit-times'
is set to 'yes'. And don't reproduced without it. I could check this
with trunk and possibly fix, when I come to my office.

--
Ivan Zhakov
Received on Fri Oct 7 10:34:32 2005

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.