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

RE: Re: Bug Report: Missing Name attribute on 'subst' drives

From: Douglas Freed <anonymous.160.matthew.scott_at_gmail.com>
Date: Thu, 20 Aug 2009 08:24:41 -0700 (PDT)

> On Thu, Apr 23, 2009 at 22:00, Stephen 'Mac' Rowe
> <srowe_at_bcsinnovations.com.au> wrote:
> > Summary:  Check-ins don't work on substituted drive letters
> >
> > Version:   TortoiseSVN 1.6.1, Build 16129 - 32 Bit , 2009/04/10 08:14:05
> >
> > What I did:
> >
> > 1. Checked out a project into the directory:  C:\Projects\Tests
> >
> > 2. Created a substituted drive to that location:  eg: Command line:   subst
> > X: C:\Projects\Tests
> >
> > 3. Modified one of the files in the project
> >
> > 4. Checked the project back in
> >
> > What happened:
> >
> > Command: Commit
> >
> > Modified: X://Thefilename.txt
> >
> > Sending content: X://Thefilename.txt
> >
> > Error: Commit succeeded, but other errors follow:
> >
> > Error: Error bumping revisions post-commit (details follow):
> >
> > Error: In directory 'X:'
> >
> > Error: Log entry missing 'name' attribute (entry 'rm' for directory 'X:')
> >
> > Finished!:
> >
> > Then  I had to do a cleanup which also failed.  Project unable to be
> > synchronised from that point on.
> > What I expected to happen:
> > A normal check in!   It used to work in previous versions (unsure of exact
> > versions - I just updated to the most recent today)
> >
> > Other comments:
> > It might seem odd to use substituted drives like this but it is extremely
> > handy.  If you've ever inherited a project from someone else and tried to
> > use it, and discovered a few dozen accidentally hard-coded paths in settings
> > file (eg: C:\Documents And Settings\Fred\Desktop) you'll know what I mean.
> > Some nasty compilers have a habit of putting full path names in project
> > files ... substituting a drive letter for the working directory ensures that
> > it will always work.
> > Or it used to mean that until I updated to Version 1.6.1
>
> I believe this is a known problem with the Subversion libraries. Try
> the same steps with the command-line client.

I tried with the latest Subversion client from CollabNet's certified binaries and it works just fine. The problem must lie with TortoiseSVN, then.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2385659

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-08-20 17:25:37 CEST

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

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