On 3/16/06, Byron Whitlock <bwhitlock@stormfront.com> wrote:
> The main problem here is somehow the repository got to a state where
> the client thinks it is up to date, but is missing a directory in the
> entries file and in the working copy.
> I am still tracking down how this happened in the first place....
>
> This is the same state as when you do a svn co -N (except svn puts all
> subdirectories in this state).
>
> The second problem is the difference between the way the svn works, and the
> api.
> "UI" is a folder neither in the working copy nor the entries file.
>
> C:\projects\Testdb\Prospero\Local Assets>svn up
> At revision 272.
>
> C:\projects\Testdb\Prospero\Local Assets>svn up "UI"
> A UI
> A UI\XBox
> A UI\XBox\Textures
> Updated to revision 272.
>
> If I make the equivalent call to svn up "UI" using svn_client_update2, I
> just get 'svn_wc_notify_skip' in the notification callback. Nothing gets
> updated.
Well, 'svn up' calls literally the same function, in pretty much the
same way. If you're seeing different behavior I'd suggest printing
out the arguments that svn is passing to svn_client_update2 and making
sure that they are in fact identical to what you're passing.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 17 00:18:32 2006