You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Sean Ellis <Se...@arm.com> on 2007/06/28 13:26:38 UTC
Strange problem with multiple ".." in path
All,
I am seeing a problem with SVN 1.4.2 (Windows) when there are multiple
consecutive ".." entries in the path. I have searched the mailing list
archives and the web, but with no useful results, so I am posting here
in case anyone else has seen it.
Paths starting with ".." and "..\.." are interpreted correctly.
Paths starting with "..\..\.." are interpreted as starting with ".."
instead
Paths starting with "..\..\..\.." are interpreted as starting with
"..\.." instead
Paths starting with "..\..\..\..\.." are interpreted as starting with
".." instead
Paths starting with "..\..\..\..\..\.." are interpreted as starting with
"..\.." instead
...and so on, alternating between .. and ..\.. depending on the number
of ..s in the path.
Here are some examples that illustrate the problem. Assume we are deep
enough in a file hierarchy that all the following are still within a
valid working copy, and that there is a folder called "source/common"
under the root.
Cd <working copy>
Svn status source
(output, as expected)
Svn status nonexistent_dir
(no output, as expected)
Cd <first level subdirectory>
Svn status ..\source
(output, as expected)
Cd <second level>
Svn status ..\..\source
(output, as expected)
Cd <third level>
Svn status ..\..\..\source
(strange, no output. It is as if ..\..\..\source does not exist)
Svn status ..\..\..\source\common
svn: warning: '..\source\common' is not a working copy
(very strange. I asked for the status 3 levels up, not 1)
The same behaviour can be seen in the Windows shell and in the Cygwin
Bash shell.
Anyone else seen this? Is this a real defect? Any information would be
gratefully appreciated.
--
Sean Ellis
--
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Strange problem with multiple ".." in path
Posted by Sean Ellis <Se...@arm.com>.
Andy Levy wrote:
> Yes, I've seen it, didn't believe it when I saw it posted on
> SVNForum several months ago but I tried it myself
> and confirmed. Only tested with Windows, no Cygwin.
For reference, this is the topic Andy was referring to:
http://www.svnforum.org/2017/viewtopic.php?t=3791
Lieven Govaerts wrote:
> This is a know issue:
> http://subversion.tigris.org/issues/show_bug.cgi?id=1869
Many thanks. I couldn't believe that something this nasty wouldn't have
been seen by at least one other person.
Unfortunately, Google tunes "../../.." out as punctuation, so you can't
easily search for it.
--
Sean Ellis
--
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Strange problem with multiple ".." in path
Posted by Lieven Govaerts <sv...@mobsol.be>.
Sean,
This is a know issue: http://subversion.tigris.org/issues/show_bug.cgi?id=1869
The original issue has been solved in APR, one of the libraries Subversion
relies on. Unfortunately the fixed version of APR (0.9.13) wasn't distributed
with Subversion 1.4.4.
Which leaves you two options:
- build subversion from source with the new apr packages
- wait till Subversion 1.5
hth,
Lieven
Quoting Sean Ellis <Se...@arm.com>:
> All,
>
> I am seeing a problem with SVN 1.4.2 (Windows) when there are multiple
> consecutive ".." entries in the path. I have searched the mailing list
> archives and the web, but with no useful results, so I am posting here
> in case anyone else has seen it.
>
> Paths starting with ".." and "..\.." are interpreted correctly.
> Paths starting with "..\..\.." are interpreted as starting with ".."
> instead
> Paths starting with "..\..\..\.." are interpreted as starting with
> "..\.." instead
> Paths starting with "..\..\..\..\.." are interpreted as starting with
> ".." instead
> Paths starting with "..\..\..\..\..\.." are interpreted as starting with
> "..\.." instead
> ...and so on, alternating between .. and ..\.. depending on the number
> of ..s in the path.
>
> Here are some examples that illustrate the problem. Assume we are deep
> enough in a file hierarchy that all the following are still within a
> valid working copy, and that there is a folder called "source/common"
> under the root.
>
> Cd <working copy>
> Svn status source
> (output, as expected)
>
> Svn status nonexistent_dir
> (no output, as expected)
>
> Cd <first level subdirectory>
> Svn status ..\source
> (output, as expected)
>
> Cd <second level>
> Svn status ..\..\source
> (output, as expected)
>
> Cd <third level>
> Svn status ..\..\..\source
> (strange, no output. It is as if ..\..\..\source does not exist)
>
> Svn status ..\..\..\source\common
> svn: warning: '..\source\common' is not a working copy
> (very strange. I asked for the status 3 levels up, not 1)
>
> The same behaviour can be seen in the Windows shell and in the Cygwin
> Bash shell.
>
> Anyone else seen this? Is this a real defect? Any information would be
> gratefully appreciated.
>
> --
> Sean Ellis
>
> --
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Strange problem with multiple ".." in path
Posted by Andy Levy <an...@gmail.com>.
On 6/28/07, Sean Ellis <Se...@arm.com> wrote:
> All,
>
> I am seeing a problem with SVN 1.4.2 (Windows) when there are multiple
> consecutive ".." entries in the path. I have searched the mailing list
> archives and the web, but with no useful results, so I am posting here
> in case anyone else has seen it.
>
> Paths starting with ".." and "..\.." are interpreted correctly.
> Paths starting with "..\..\.." are interpreted as starting with ".."
> instead
> Paths starting with "..\..\..\.." are interpreted as starting with
> "..\.." instead
> Paths starting with "..\..\..\..\.." are interpreted as starting with
> ".." instead
> Paths starting with "..\..\..\..\..\.." are interpreted as starting with
> "..\.." instead
> ...and so on, alternating between .. and ..\.. depending on the number
> of ..s in the path.
>
> Here are some examples that illustrate the problem. Assume we are deep
> enough in a file hierarchy that all the following are still within a
> valid working copy, and that there is a folder called "source/common"
> under the root.
>
> Cd <working copy>
> Svn status source
> (output, as expected)
>
> Svn status nonexistent_dir
> (no output, as expected)
>
> Cd <first level subdirectory>
> Svn status ..\source
> (output, as expected)
>
> Cd <second level>
> Svn status ..\..\source
> (output, as expected)
>
> Cd <third level>
> Svn status ..\..\..\source
> (strange, no output. It is as if ..\..\..\source does not exist)
>
> Svn status ..\..\..\source\common
> svn: warning: '..\source\common' is not a working copy
> (very strange. I asked for the status 3 levels up, not 1)
>
> The same behaviour can be seen in the Windows shell and in the Cygwin
> Bash shell.
>
> Anyone else seen this? Is this a real defect? Any information would be
> gratefully appreciated.
Yes, I've seen it, didn't believe it when I saw it posted on SVNForum
several months ago but I tried it myself and confirmed. Only tested
with Windows, no Cygwin.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org