On 10.08.2011 19:25, Nicklas Norling wrote:
> Hi devs,
> Today I installed the 1.7.0 beta2 win32 at work (32-bit Vista).
> After reboot I proceeded to upgrade a WC from the latest 1.6 version,
> the WC contains (among other things)
> a folder with 12 file externals.
> Before upgrade, ran cleanup, no uncommitted changes in the WC.
> Upgrade went fine (no errors).
> Ran Update, got an error for each file external indicating that the
> external could not be checked out since
> the same file already was versioned.
> Scratching the WC and checking out fresh will result in a WC that works
> (no error when Updating).
> I got the impression that the upgrade script somehow added the file
> externals as file that are versioned
> in the WC directly. I guess that would be a bug?
> I am uncertain if this is a bug in TSVN or Subversion as I do not know
> how upgrade is initiated, therefore I am
> mailing this list rather then svn-dev, can you advice?
Upgrading is done by the svn library. You should report this on the SVN
mailing list (users at subversion tigris org).
And please include an example svn:externals property in your report -
I've tried with a test working copy and a few file externals - the
upgrade worked fine for me.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-08-10 21:20:10 CEST