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

Re: Cannot commit/status/... on single files on network drive - bug in path construction

From: Felix Saphir <felix.saphir_at_kantarmedia.de>
Date: Mon, 28 Feb 2011 17:34:51 +0100

Am 28.02.2011 16:01, schrieb Eelke Spaak:
> Currently, I am using TortoiseSVN 1.6.12, 64bit version, on a 64-bit
> Windows 7 machine, and have checked out a repository to a folder on a
> mapped network drive.

Don't do that! It's recommended to put working copies on local drives.

> Whenever I try to commit (or check the status
> of) a file, the relevant dialog does pop up, but there is an error in
> the dialog: "Can't open file
> 'M:\fieldtrip-local\ft_singleplotTFR.m\.svn\entries': The directory
> name is invalid.". This error message was generated when trying to
> commit the *file* 'M:\fieldtrip-local\ft_singleplotTFR.m', so the
> directory name is indeed invalid.

Well, the file ...\.svn\entries is part of the metadata of a working
copy, and the name is perfectly valid. I think this is a side-effect of
keeping the working copy on a network drive.

> This seems like a bug to me. There are no problems whatsoever after
> checking out the same repository to a local drive, and attempting the
> same commit. Also, committing works perfectly from the Linux command
> line, using the checked out copy on the network drive.

It's not really a bug, I guess the server of the network drive is
somehow interfering.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-02-28 17:35:05 CET

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