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

[TSVN] Trapping yourself with externals

From: Lübbe Onken <l.onken_at_rac.de>
Date: 2005-07-12 11:00:27 CEST

Hi Folks,

A colleague of mine ran into an interesting problem today with his use of

His repository is set up in a way that it contains several main projects
plus several library projects, say:


His libraries are referenced as externals from inside his main project(s),
so when he checks out trunk/main1, he gets a WC like:

Main1/src/lib1 (external pointing to trunk/lib1)
Main1/src/lib2 (external pointing to trunk/lib2)

If he now changes somthing inside src *and* inside lib1 and tries to commit
main1, TortoiseSVN fills the commit dialog with all changes *without* a
warning that there are changes in externals which should be committed

The commit fails with two different error messages. Both are written from
memory, so I don't have the exact text at hand.
Either: "the versioned ressource does not correspond... " (most of the time
it's "src"), "...update your working copy"
Or (haven't seen this one myself): "... Please run cleanup"

Committing the externals (lib1) first and the other changes (src) afterwards
works as usual.

I think the reason for the failure is that the externals point to the same
repository as the main source, but to a different location in the tree.
Probably TSVN calculates a wrong base path for the commit.

- Lübbe

  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Jul 12 11:00:55 2005

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

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