Ben Collins-Sussman <sussman@collab.net> writes:
> For the last three days now, every morning I run 'svn st -u', followed
> immediately by 'svn up', and I always get *different* results! Here
> are my transcripts:
>
> -----------------------------------------------
> DAY 1
>
> $ svn st -u
> M 4192 notes/autoversioning-strategy.txt
> S 4193 subversion/mod_dav_svn
> M 4193 subversion/mod_dav_svn/deadprops.c
> Head revision: 4194
>
> $ svn up
> U subversion/include/svn_props.h
> Updated to revision 4194.
Ooooh. Yeah, why didn't it show svn_props.h as needing updating?
> DAY 2
>
> $ svn st -u
> M 4195 doc/book/outline.txt
> M 4195 notes/autoversioning-strategy.txt
> S 4195 subversion/mod_dav_svn
> Head revision: 4196
There must have been one other update, too, since you went from 4194
to 4195.
> $ svn up
> U doc/book/book/ch06.xml
> Updated to revision 4196.
Same with ch06.xml...
> DAY 3
>
> $ svn st -u
> M 4196 doc/book/outline.txt
> M 4196 notes/autoversioning-strategy.txt
> * notes/webdav-proxy
> S 4196 subversion/mod_dav_svn
> Head revision: 4204
>
> $ svn up
> A notes/webdav-proxy
> U subversion/svnadmin/main.c
> U subversion/svnlook/main.c
> U packages/rpm/redhat-7.x/subversion.spec
> U packages/rpm/redhat-8.x/subversion.spec
> Updated to revision 4204.
Well, I'm glad to see it noticed at least *one* of the outdated files
when you ran status :-(.
> Needless to say, I find this more than a little bit disturbing. :-(
>
> Can anyone else reproduce this? I wonder if it has something to do
> with having a switched subdir. My guess is that to reproduce, you
> simply need to 1. backdate your working copy a few revisions, so it's
> out of date ('svn up -r'), and 2. switch a subdir to a branch.
>
> This looks like a big, big bug to me.
Yup. Wonder if it's related to Andreas' bug...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Dec 29 18:05:22 2002