On 3/20/07, Paul <email@example.com> wrote:
> I looked at the TSVN issue tracker, and did not see anything like this...
> BACKGROUND INFORMATION:
> I have a USB flash drive that I use for my projects.
> I have the following directories on this drive:
> \svn-repos\apps my Subversion repository
> \project001\wc my WC of the trunk of a project in the repository.
> The drive letter that is assigned to the drive changes depending on
> the computer I am using. So, when I created my WC using the command
> line, I did not specify a drive letter as part of the file URL.
> Now, I cannot get TSVN to do anything that requires access the repository.
> Using v1.4.2 of the Subversion command line client, I created the
> local WC using the following command:
> svn checkout file:///svn-repos/apps/project001/trunk \project001\wc
> Now, if I try to use TSVN (v1.4.3 Build 8645) to do an SVN Update (or
> anything that requires connecting to the repository), I receive the
> following error:
> Unable to open an ra_local session to URL
> Unable to open repository 'file:///svn-repos/apps/project001/trunk'
> RECIPE TO REPRODUCE BUG:
> With the command line client installed, assuming you have a "\TEMP"
> directory, use, open a command prompt and use the following commands:
> svnadmin create \temp\tsvn_bug_repo
> svn mkdir file:///temp/tsvn_bug_repo/newdir -m "Creating a directory"
> mkdir \temp\tsvn_bug_wc
> svn checkout file:///temp/tsvn_bug_repo/newdir \temp\tsvn_bug_wc
> svn info \temp\tsvn_bug_wc
> Now, use TSVN to navigate to \TEMP, right click on tsvn_bug_wc, and
> select SVN Update.
> Is this a bug with TSVN, or is the SVN command line accepting an invalid URL ?
> Any help would be appreciated.
> I know I can work around this by using SUBST to remap the USB flash
> drive to a consistent drive letter for all systems, but if this is a
> TSVN bug I wanted to let the developers know about it.
I think the confusion stems from the fact that the SVN command-line
client is assuming that the file:/// URL is relative to the current
directory, whereas TSVN (probably) has no "current directory"
available to it due to how it interacts with the system.
To be honest, I didn't even realize you could do this - I thought
file:/// URLs needed to be full absolute paths (your SUBST solution),
because the SVN book only makes reference to them (see
Unfortunately, it seems like both are "right", though I would venture
to say that the command-line client is "less right" because it seems
to make that assumption about using the current directory.
IMHO, it's worth bringing this URL/current directory issue up on the
main SVN users list to see if it's desired/expected/known behavior.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Mar 20 19:10:34 2007