Hmmm... That's what I thought too, that svn update always fetched *all* new
data. I was able to get him working again by deleting the failing directory
and doing an svn update on that directory. ("cd ..; rm -rf dirA; svn update
dirA").
I'll see if I can recreate the problem with a small test repository and work
tree.
thanks,
David
On 5/10/07, Ryan Schmidt <subversion-2007b@ryandesign.com> wrote:
>
>
> On May 9, 2007, at 22:32, David Ferguson wrote:
>
> > (I'm using Subversion 1.4.3) One of my users came to me with an
> > interesting problem which I don't know how to solve. He isn't
> > getting newly added directories when he does an 'svn update'. For
> > example:
> >
> > $ pwd
> > /work/user/dirA
> > $ ls
> > subdirB subdirC subdirD
> > $ svn ls
> > subdirB subdirC subdirD subdirE subdirF
> > $ svn update
> > At revision 639.
> > $ ls
> > subdirB subdirC subdirD
> >
> > Why didn't Subversion fetch subdirE and subdirF?? In CVS I would
> > tell him to always use "cvs update -d" which would fetch any newly
> > created directories. Is there a Subversion equivalent way to
> > update and get all newly created directories?
> >
> > I told him to explicitly update the subdirE and subdirF
> > directories, but is there a way to update and get new directories
> > without having to know what directories are missing?
> >
> > To finish out the example:
> >
> > $ svn update subdirE subdirF
> > A subdirE
> > A subdirF
> > Updated to revision 639.
> > $ ls
> > subdirB subdirC subdirD subdirE subdirF
>
> There is no way _not_ to get the new directories. "svn update" always
> fetches all new data. I can't explain why it didn't do that for you,
> other than that your working copy is messed up. Check out a new
> working copy and see if you can replicate the problem there. If not,
> continue using that working copy and trash the broken one.
>
>
>
Received on Thu May 10 16:08:12 2007