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 ADF5E7F61 for ; Tue, 1 Nov 2011 21:00:06 +0000 (UTC) Received: (qmail 48069 invoked by uid 500); 1 Nov 2011 21:00:05 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 47840 invoked by uid 500); 1 Nov 2011 21:00:05 -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 Delivered-To: moderator for users@subversion.apache.org Received: (qmail 5674 invoked by uid 99); 1 Nov 2011 20:50:16 -0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=FREEMAIL_FROM,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 204.13.40.82 is neither permitted nor denied by domain of snhirsch@gmail.com) X-RC-FROM: X-RC-RCPT: Message-ID: <4EB05B69.3010602@gmail.com> Date: Tue, 01 Nov 2011 16:49:45 -0400 From: Steven Hirsch User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15 MIME-Version: 1.0 To: users@subversion.apache.org Subject: Odd path name Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I'm seeing a nasty bug in several of the GUI front-end tools for subversion, and the error messages from several involved a path containing: .../!svn/bc/12345/... where 12345 is one of the revisions involved. The complaint is about the path not being found, but I'm not clear on where it's coming from in the first place. Neither "!svn" or "bc" are currently or were ever part of the project in question. Does this ring any bells with anyone? FYI: The situation that appears to cause problems is when a repository directory tree is "collapsed" by moving the contents of a nested directory to that directory's parent and removing the original directory. From that point on, all the GUI front ends get very confused when trying to difference revisions of a relocated file that span the committed move. I do not believe the problem is with SVN, per se, since command line diffs using the two revision numbers against the current file location work fine. I'm thinking that path is part of SVN's bookkeeping and it would help to understand it in more depth. Steve