Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CFA3DC9D1 for ; Wed, 19 Jun 2013 11:12:06 +0000 (UTC) Received: (qmail 32880 invoked by uid 500); 19 Jun 2013 11:12:06 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 32862 invoked by uid 500); 19 Jun 2013 11:12:06 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 32855 invoked by uid 99); 19 Jun 2013 11:12:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Jun 2013 11:12:05 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of johan556@gmail.com designates 209.85.215.53 as permitted sender) Received: from [209.85.215.53] (HELO mail-la0-f53.google.com) (209.85.215.53) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Jun 2013 11:12:00 +0000 Received: by mail-la0-f53.google.com with SMTP id fs12so4511189lab.12 for ; Wed, 19 Jun 2013 04:11:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=ftXhzDa3qlNIOzDf03raQMSmDuo4DHERpe4xluGlFag=; b=QaLsdGRnaMa6Ln92PUVQWJPcZ2A4WWB9YTcYfHfHfdfmpL9gXbnkTJ0qryaK7Bm71y cy6m6PHBxVjugAPgbobIvAn7E6wS4BpYeEuN/s3ggTXYgWRyjnrcBWXkn6KThFWOdQPu pgUd1yHTQL1cjn+408w0SMegz7/LJRwMCHnPpWQUB1NfLMVo9HmDEukTVIPQRCxFWRJ/ NrQiUgn6BgxTXZUPWXvyk+nnxEd9jGO77lrZMVMfyZwOtT64966+8XzW665Mlvuusm4/ eRAr8yHjNLoXqu+lQaFZfwYPDcHZjsDwFtbKy4yRYqNqsvFy4OtSnIg/wvF73tLWnQK9 2pAw== MIME-Version: 1.0 X-Received: by 10.112.141.6 with SMTP id rk6mr3075334lbb.50.1371640299399; Wed, 19 Jun 2013 04:11:39 -0700 (PDT) Received: by 10.112.35.40 with HTTP; Wed, 19 Jun 2013 04:11:39 -0700 (PDT) Date: Wed, 19 Jun 2013 13:11:39 +0200 Message-ID: Subject: Problem, svn upgrade & externals & svn status (1.6 --> 1.7) From: Johan Holmberg To: users@subversion.apache.org Content-Type: multipart/alternative; boundary=001a11c26310ce314504df7fe43e X-Virus-Checked: Checked by ClamAV on apache.org --001a11c26310ce314504df7fe43e Content-Type: text/plain; charset=ISO-8859-1 Hi! I have just started using the Subversion client 1.7.5 (I used 1.6.17 previously). To be able to use my old working copies I had to do a "svnupgrade". But after the upgrade, the svn:externals are no longer fully recognized. The "svn status" command no longer "recurses into sub-projects" the way it used to. The difference can be seen by: ----------------------------- $ svn status proj1 X proj1/proj2-subdir $ $ svn status proj1-new X proj1-new/proj2-subdir Performing status on external item at 'proj1-new/proj2-subdir': ----------------------------- "proj1" is the old working copy with "svn upgrade" applied. "proj1-new" is a fresh checkout of the project with the new client version. I have looked around in the ".svn" directory of the projects and found a difference that perhaps explains the difference i behaviour: ----------------------------- $ sqlite3 proj1/.svn/wc.db 'select * from EXTERNALS order by local_relpath' 1|proj2-subdir||1|normal|unknown|||| $ $ sqlite3 proj1-new/.svn/wc.db 'select * from EXTERNALS order by local_relpath' 1|proj2-subdir||1|normal|dir||proj2|| ----------------------------- Note that the upgraded working copy has the externals entry marked "unknown". Is what I describe here a known problem of the "svn upgrade" command? I also wonder if there is some way to get my existing working copies fully functional again without doing a new checkout. /Johan Holmberg --001a11c26310ce314504df7fe43e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi!

I have just= started using the Subversion client 1.7.5 (I used 1.6.17 previously). To b= e able to use my old working copies I had to do a "svn upgrade". But after the upgrade, the svn:externals are no longer fully recognized. The "svn status" command no longer "recurses into sub-projects" the way it used to. T= he difference can be seen by:

-----------------------------
$ svn st= atus proj1=A0=A0=A0
X=A0=A0=A0=A0=A0=A0 proj1/proj2-subdir
$
$ svn status pro= j1-new
X=A0=A0=A0=A0=A0=A0 proj1-new/proj2-subdir=

Performing status on external item at 'proj1-new/proj2-subdir':=
-----------------------------

"proj1" is the old= working copy with "svn upgrade" ap= plied. "proj1-new" is a fresh checkout of the project with the ne= w client version. I have looked around in the ".svn" directory of the projects and found a difference that per= haps explains the difference i behaviour:

-----------------------------
$ sqlite3 proj1/.svn/wc.db 'select * from EXTERNA= LS order by local_relpath'=A0=A0=A0
1|proj2-= subdir||1|normal|unknown||||
$
$ sqlite3 proj1-new/.svn/wc.db 'select * from EXTERNALS order by local_relpath&#= 39;
1|proj2-subdir||1|normal|dir||proj2||
-----------------------------

Note that the upgraded working c= opy has the externals entry marked "unknown".

Is wha= t I describe here a known problem of the "svn upgrade" command?

I also wonder if there is some way to get my existing working cop= ies fully functional again without doing a=A0 new checkout.

/J= ohan Holmberg





--001a11c26310ce314504df7fe43e--