>>> On Mar 2, 2016, at 10:16 AM, txm <tmell...@web.de> wrote: >>> >>> Hello, >>> >>> I am confused and frustrated by this: >>> >>> $ pwd >>> /home/user/nodes/dev_5_main >>> >>> $ svn info /home/user/nodes/dev_5_main >>> svn: '/home/user/nodes' is not a working copy >>> >>> $ svn info . >>> Path: . >>> URL: svn+ssh://user@10.120.11.5/COE/branches/dev_5_main >>> Repository Root: svn+ssh://user@10.120.11.5/COE >>> Repository UUID: (stuff) >>> Revision: 2249 >>> Node Kind: directory >>> Schedule: normal >>> Last Changed Author: developer >>> Last Changed Rev: 2241 >>> Last Changed Date: 2016-02-24 06:57:03 +0100 (Wed, 24 Feb 2016) >>> >>> Specifying the "current working directory" with a "." yields the >>> information I want, but using an absolute path requires accessing the >>> directory above? This is very problematic for my script. Is there a way >>> out? >>> >>> Tom >> >> I tested your scenario using svn 1.9.3 on OS X and I do not get the "is not >> a working copy" behavior you describe. You don't mention the version of SVN >> or of the operating system. >> > On Mar 3, 2016, at 12:06 AM, txm <tmell...@web.de> wrote: > > Sorry, > > svn, version 1.6.6 (r40053) > svn is hashed (/usr/bin/svn) > DISTRIB_DESCRIPTION="Ubuntu 10.04.4 LTS" > > Tom > > It's ubuntu
Version 1.6 is no longer supported. If there is indeed some bug in the 1.6 client that causes the behavior you describe it will not be fixed in the 1.6 release branch. If you can, upgrade to either 1.8 or 1.9. There were significant changes to the layout of the working copy during the years between 2009 and 2016 and the behavior you described might have been something seen in the past. I tested the scenario with 1.7.20 also and did not see the behavior.
