> To be honest, I think the answer to "but I deleted all the metadata
> outside the scope of svn" is "don't do that".
Sure, I'll get right on the phone and tell our 3rd party tool developer
to stop removing the meta-data when they manipulate the database...
right.
"Could someone test this under 1.5?" Please? I don't have ready access
to a compiled version.
If it still fails then can I/someone file a bug or whip out a quick
patch?
It seems trivial to remove the scheduled-for-deletion flag and just mark
it as missing.
Eric
> -----Original Message-----
> From: dglasser_at_gmail.com [mailto:dglasser_at_gmail.com] On Behalf Of
David
> Glasser
> Sent: Wednesday, January 09, 2008 11:40 AM
> To: Miller, Eric
> Cc: dev_at_subversion.tigris.org
> Subject: Re: Bug with missing scheduled-for-delete dir
>
> To be honest, I think the answer to "but I deleted all the metadata
> outside the scope of svn" is "don't do that".
>
> Now, would life be better if the metadata was all in one place and not
> scattered everywhere? Yup, and we hope to fix that in a future
> version. But until then, I'm not sure how much it's worth it to fix
> this sort of issue...
>
> --dave
>
> On Jan 9, 2008 1:14 PM, Miller, Eric <Eric.Miller_at_amd.com> wrote:
> > Yes, but I have other things I don't want updated... the working
copy is
> > huge and I only want that one sub-path updated.
> >
> >
> > > -----Original Message-----
> > > From: dglasser_at_gmail.com [mailto:dglasser_at_gmail.com] On Behalf Of
> > David
> > > Glasser
> > > Sent: Wednesday, January 09, 2008 11:12 AM
> > > To: Miller, Eric
> > > Cc: dev_at_subversion.tigris.org
> > > Subject: Re: Bug with missing scheduled-for-delete dir
> > >
> > > Doesn't "svn up wc" work?
> > >
> > > --dave
> > >
> > > On Jan 9, 2008 1:02 PM, Miller, Eric <Eric.Miller_at_amd.com> wrote:
> > > > I think this is another working copy bug. Could someone test
this
> > under
> > > > 1.5?
> > > >
> > > > Synopsis: A scheduled-for-delete path is removed via system
command
> > or
> > > > 3rd party application. Depending on the contents of the working
> > copy,
> > > > this may not be recoverable using svn commands.
> > > >
> > > > Recipe using 1.4.4:
> > > > svnadmin create repos
> > > > svn co file://`pwd`/repos wc
> > > > touch wc/afile
> > > > mkdir -p wc/dir/subdir
> > > > svn add wc/*
> > > > svn ci -m '' wc
> > > > svn up -N wc
> > > > svn lock wc/afile
> > > > svn rm wc/dir
> > > > mkdir wc/dir2
> > > > rm -rf wc/dir
> > > >
> > > > Now we are somewhat hosed:
> > > > % svn up wc/dir
> > > > svn: Directory 'wc/dir' is missing
> > > >
> > > > % svn up -N wc/dir
> > > > svn: Directory 'wc/dir' is missing
> > > >
> > > > % svn st -N wc
> > > > ? wc/dir2
> > > > K wc/afile
> > > > D wc/dir
> > > >
> > > > % svn st -N -u wc
> > > > ! ? wc/dir
> > > > ? wc/dir2
> > > > K 1 wc/afile
> > > > Status against revision: 1
> > > >
> > > > But... oddly enough we can remove the blockage:
> > > > % svn unlock wc/afile
> > > > 'afile' unlocked.
> > > >
> > > > And then through some trickery, restore the path:
> > > > % svn up -N wc/dir
> > > > D wc/dir
> > > > Updated to revision 1.
> > > >
> > > > % svn up -N wc/dir
> > > > A wc/dir
> > > > Updated to revision 1.
> > > >
> > > > All is well:
> > > > % svn st -u wc
> > > > ? wc/dir2
> > > > Status against revision: 1
> > > >
> > > >
> > > >
> >
---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
> > > > For additional commands, e-mail: dev-help_at_subversion.tigris.org
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > David Glasser | glasser_at_davidglasser.net |
> > http://www.davidglasser.net/
> > >
> >
> >
> >
> >
>
>
>
> --
> David Glasser | glasser_at_davidglasser.net |
http://www.davidglasser.net/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-01-09 19:52:23 CET