You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Aleksey Nogin <al...@nogin.org> on 2005/10/07 05:59:08 UTC
Bug? "svn up" gets confused if repo has a property change, and the
file was rm'd from the wc.
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
Right after this message, svn exits (with code 1), aborting the update
in the middle.
Is this a known bug? Should I file an issue?
P.S. I tried versions 1.2.3 (r15833) and 1.1.0 (r11180)
--
Aleksey Nogin
Home Page: http://nogin.org/
E-Mail: nogin@cs.caltech.edu (office), aleksey@nogin.org (personal)
Office: Moore 04, tel: (626) 395-2200
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Bug? "svn up" gets confused if repo has a property change, and
the file was rm'd from the wc.
Posted by "Peter N. Lundblad" <pe...@famlundblad.se>.
On Fri, 7 Oct 2005, Ivan Zhakov wrote:
> On 10/7/05, Peter N. Lundblad <pe...@famlundblad.se> wrote:
> On Fri, 7 Oct 2005, Ivan Zhakov wrote:
>
> Aha! I don't use that option:-)
I also don't use this option, but 'set-timestamp' pointed me to
possible problem.
I consider we should run all regression tests with two value of this option.
Not always, I hope:-) But some nightly test that did that would be nice
IMO.
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Bug? "svn up" gets confused if repo has a property change, and
the file was rm'd from the wc.
Posted by Philip Martin <ph...@codematters.co.uk>.
Ivan Zhakov <ch...@gmail.com> writes:
> On 10/7/05, Peter N. Lundblad <pe...@famlundblad.se> wrote:
>> On Fri, 7 Oct 2005, Ivan Zhakov wrote:
>>
>> > > 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'
>>
>> Aha! I don't use that option:-)
> I also don't use this option, but 'set-timestamp' pointed me to
> possible problem.
>
> I consider we should run all regression tests with two value of this option.
I suspect you are thinking of changing $HOME/.subversion/config. That
won't work since the regression tests use --config-dir and so the
users config file has no effect on the tests. I did write one tiny
use-commit-times regression test when I fixed an entries file
text-time bug; as far as I know that's the only regression testing
that use-commit-times gets.
--
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Bug? "svn up" gets confused if repo has a property change, and the file was rm'd from the wc.
Posted by Ivan Zhakov <ch...@gmail.com>.
On 10/7/05, Peter N. Lundblad <pe...@famlundblad.se> wrote:
> On Fri, 7 Oct 2005, Ivan Zhakov wrote:
>
> > > 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'
>
> Aha! I don't use that option:-)
I also don't use this option, but 'set-timestamp' pointed me to
possible problem.
I consider we should run all regression tests with two value of this option.
--
Ivan Zhakov
Re: Bug? "svn up" gets confused if repo has a property change, and
the file was rm'd from the wc.
Posted by "Peter N. Lundblad" <pe...@famlundblad.se>.
On Fri, 7 Oct 2005, Ivan Zhakov wrote:
> > 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'
Aha! I don't use that option:-)
Thanks,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Bug? "svn up" gets confused if repo has a property change, and the file was rm'd from the wc.
Posted by Ivan Zhakov <ch...@gmail.com>.
On 10/7/05, Peter N. Lundblad <pe...@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
Re: Bug? "svn up" gets confused if repo has a property change, and
the file was rm'd from the wc.
Posted by "Peter N. Lundblad" <pe...@famlundblad.se>.
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?
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Bug? "svn up" gets confused if repo has a property change, and
the file was rm'd from the wc.
Posted by Aleksey Nogin <al...@nogin.org>.
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
% svn co file:///tmp/test wc1
Checked out revision 0.
% touch wc1/foo
% svn add wc1/foo
A wc1/foo
% svn ps svn:mime-type application/foo wc1/foo
property 'svn:mime-type' set on 'wc1/foo'
% svn ci -m "" wc1/foo
Adding (bin) wc1/foo
Transmitting file data .
Committed revision 1.
% svn co file:///tmp/test wc2
A wc2/foo
Checked out revision 1.
% svn rm --force wc2/foo
D wc2/foo
% svn pd svn:mime-type wc1/foo
property 'svn:mime-type' deleted from 'wc1/foo'.
% svn ci -m "" wc1/foo
Sending wc1/foo
Committed revision 2.
% svn up wc2
U wc2/foo
svn: In directory 'wc2'
svn: Error processing command 'set-timestamp' in 'wc2'
svn: Can't set access time of 'wc2/foo': No such file or directory
--
Aleksey Nogin
Home Page: http://nogin.org/
E-Mail: nogin@cs.caltech.edu (office), aleksey@nogin.org (personal)
Office: Moore 04, tel: (626) 395-2200
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Bug? "svn up" gets confused if repo has a property change, and
the file was rm'd from the wc.
Posted by "Peter N. Lundblad" <pe...@famlundblad.se>.
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?
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org