search

ycaihua / svnx

Automatically exported from code.google.com/p/svnx
1 stars 0 forks source link

Working Copy shows path but leading character is missing #204

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1. Create, or check out, a project using Subversion version 1.7, and open the 
Working Copy in svnX. It should show the 'Name' column with the list of paths 
and files. This should show the folder and file names correctly.

2. Upgrade the project to Subversion version 1.8. Again, open the Working Copy 
in svnX. The first letter of the files/paths under the 'Name' column is chopped 
off:

"source/foo" appears as "ource/foo" and "myfile.txt" appears as "yfile.txt"

I had upgraded my projects via the command-line "svn upgrade" command.

What is the expected output? What do you see instead?

Expected: "source/foo"
Seen: "ource/foo"

Expected: "resources/assets/3d/file.3ds"
Seen: "esources/assets/3d/file.3ds"

What version of the product are you using? On what operating system?

svnX: 1.3.4
OS X: 10.8.4 (Mountain Lion)

Please provide any additional information below.

Files can still be submitted and pulled from the server normally; it only 
affects svnX visually, or if the "search" bar at the top is used: "source" 
cannot be found but "ource" can.
If screenshots would be helpful, let me know and I can provide those as needed.

Original issue reported on code.google.com by ste...@sunstormgames.com on 6 Aug 2013 at 8:15

GoogleCodeExporter commented 9 years ago 
I haven’t tried Subversion 1.8, but others are using it with no reported 
issues.
From where did you obtain your Subversion 1.8?
Does it include any patches?

Please do the following:
1. Launch svnX & open the WC window for the problematic WC.
2. Open the Activity window.
3. Select the ‘svn status’ task & click the ‘info’ button.
4. Select the text of the command and drag & drop it into a Terminal.app window.
5. Append ‘ | bzip2 -9 > ~/Desktop/svn-status.bz2’ to the line & press the 
return key.
    [You should have a command like ‘…/svn status --non-interactive -v --xml YOUR-WC-PATH | bzip2 -9 > ~/Desktop/svn-status.bz2’.]
6. Attach the ‘svn-status.bz2’ file that should appear on your desktop to 
this issue (or e-mail it directly to me).

This should help me to diagnose & fix the problem.

Original comment by chris...@gmail.com on 6 Aug 2013 at 10:50

GoogleCodeExporter commented 9 years ago 
I have used MacPorts to install Subversion, and used it to upgrade all the way 
from 1.6 through 1.8.

The full 'svn --version' dump gives:

svn, version 1.8.1 (r1503906)
   compiled Jul 30 2013, 20:33:13 on x86_64-apple-darwin12.3.0

Copyright (C) 2013 The Apache Software Foundation.
This software consists of contributions made by many people;
see the NOTICE file for more information.
Subversion is open source software, see http://subversion.apache.org/

The following repository access (RA) modules are available:

* ra_svn : Module for accessing a repository using the svn network protocol.
  - with Cyrus SASL authentication
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using serf.
  - handles 'http' scheme
  - handles 'https' scheme

Besides the dump, I am attaching a screenshot of the svnX window. The dump 
should show that everything is fine with the repo (and ALL repos that I've 
upgraded to 1.8 and tried svnX on, have displayed the same visual problem).

Original comment by ste...@sunstormgames.com on 7 Aug 2013 at 12:45

Attachments:

GoogleCodeExporter commented 9 years ago 
Steven,

I’ve looked into this … and there’s good news … and there’s bad news.

The bad news is that this is a bug in Subversion 1.8.0 & 1.8.1.
They don’t write the same paths in the XML entry elements as previous 
versions.

The good news is that this is apparently fixed in Subversion’s trunk and 
should thus, hopefully, appear in Subversion 1.8.2 - soon.
See <http://subversion.tigris.org/issues/show_bug.cgi?id=4398>

While it may be possible for me to work around this in svnX, I’m not sure 
that it’s worth it - assuming they have fixed it in Subversion.

A couple of options that may work for you:
1. If you have a suitable build of Subversion 1.8.1.  You could try enabling 
the ‘Call Subversion libraries directly’ preference.  This doesn’t use 
the XML output of `svn status` so should be immune to the problem.
    [A Subversion from <http://www.wandisco.com/subversion/download#osx> should work.]
2. You could update or patch your Subversion source with the changes mentioned 
in svn_issue 4398.

Hope that helps,

CHRIS

Original comment by chris...@gmail.com on 7 Aug 2013 at 3:53

GoogleCodeExporter commented 9 years ago 
Does the just released Subversion 1.8.3 fix your problem?
It should do as <http://svn.apache.org/repos/asf/subversion/tags/1.8.3/CHANGES> 
states:
    * status: always use absolute paths in XML output (issue #4398)

[There was no Subversion 1.8.2 release.]

Original comment by chris...@gmail.com on 31 Aug 2013 at 4:52

GoogleCodeExporter commented 9 years ago 
I have upgraded my Subversion version through MacPorts, and as of this writing, 
its port is only up to 1.8.1, and so I will update this issue once that has 
occurred, one way or another.

Original comment by ste...@sunstormgames.com on 1 Sep 2013 at 6:05

GoogleCodeExporter commented 9 years ago 
Alright; MacPorts is now up to subversion @1.8.3_2, and it looks like the 
problem with the "missing first letter" has been resolved through that update.

Original comment by ste...@sunstormgames.com on 3 Sep 2013 at 2:40

GoogleCodeExporter commented 9 years ago

Original comment by chris...@gmail.com on 21 May 2014 at 12:55