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

Round 2: Merge error with mixed-revisions but subsequent "svn update" doesn't fix it

From: <webster.brent_at_rogers.com>
Date: Wed, 9 Mar 2016 16:25:16 +0000 (UTC)

Env: Server 1.9.3 (Windows) and client 1.8.15(Linux-Centos6.5) being run by all users.
We are in the mist of refactoring the directory structure. i.e. What's the process when converting a directory to use svn:externals?: http://mail-archives.apache.org/mod_mbox/subversion-users/201603.mbox/%3C1820009612.5161618.1457534793008.JavaMail.yahoo%40mail.yahoo.com%3E
When the merge issue: 'svn: E195020: Cannot merge into mixed-revision working copy [8:9775]; try updating first" raised its ugly head again. Running a"svn update' don't solve the merge error. The svnversion command is reporting 8:9775 where 9775 is the revision of this WC's primary repo/URL while 8 is the pegged version of the latest directory that was converted from a fully checked in directory to a svn:externals.  I'm having no luck reproducing the problem so I can run some of the suggested workarounds:  "svn update --ignore-externals" or execute "svn update -r XXX" with an explicit revision.
I know as the directory refactoring stabilizes, I hoping these issues will disappear but for now I have 100+ users that don't need this headache.  My only solution is to delete and recreate the WC which is a hour+ checkout.
 ---- Brent
Received on 2016-03-09 17:47:11 CET

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

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