[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

What is UDS in subversion? (Strange issue in SCC SVN client PushOk)

From: Roman Kellner <muzungu_at_gmx.net>
Date: Wed, 29 Jan 2014 09:10:16 +0100 (CET)


We are using a MSSCCI to SVN client (PushOk) which in the version 1.7.13 and with our project does strange things.
When opening our IDE SccProjectOpen() is called on the MSSCCI interface.

I do not exactly know what is done on the SVN level, but with the SccProjectOpen() call, outdated local copy files get somehow "updated" (which they should not). Strangly only the base file and the meta (.svn) data get updated but the "real" working copy file remains unchanged, rendering this file "locally modified".
TortoiseSVN (1.7.13-svn1.7.10), used for verification shows outdated before and uptodate but locally modified afterwards.

The only indication I have from PushOk is that it is printing

UDS<some number>/a/sub/path/to/our/project/root/path/aFile.ext
UDS<some number>/a/sub/path/to/our/project/root/path/anotherFile.ext

in its status box.

Does that look familiar to someone?

Could that be SVN messages from callbacks that are shown here?

Instead of your projects root folder always UDS<some number> is printed where as the <some number> does NOT change for one SccProjectOpen() call but does change for a next call.
Why is the projects root folder replaced?

I searched "subversion and uds" in the internet and found "uds_path" in some hits. Generally it looked like a session id to me in the first place.
What is this UDS<some number>?
What is a uds_path?
What stands "uds" for?

I know I should ask the PushOk folks about what they are doing in their MSSCCI-SVN provider. But communication is basically non-existent (no answers for a looong time).

I am only trying to get hints to understand what is happening and would appreciate any clue.


Received on 2014-01-29 09:11:04 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.