'svn ls' not showing the contents of the repository

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

'svn ls' not showing the contents of the repository

Anton Shepelev
Hello, all

Why can 'svn ls' show different results when invoked from
two working copies of the same repository?  According to the
documentation is should always list the acutal contents of
the corresponding repository:

  The default TARGET is ., meaning the repository URL of the
  current working copy directory.

'svn info' from both the working copies returns:

  URL: http://sbo-prod1:18080/svn/Sources

so why the outout of 'svn ls' is not the same?  In the
working copy that I checked-out later it shows some newly
added directories that it does not "see" from within the
older working copy.  When I invoke:

  svn ls http://sbo-prod1:18080/svn/Sources

from the older working copy the output is as expected.

--
Please, do not forward replies to the list to my e-mail.

Reply | Threaded
Open this post in threaded view
|

Re: 'svn ls' not showing the contents of the repository

Daniel Shahaf-2
Anton Shepelev wrote on Wed, 29 Nov 2017 20:18 +0300:
> Why can 'svn ls' show different results when invoked from
> two working copies of the same repository?

Probably because the working copy's BASE revision is different.  'svn ls'
runs 'svn ls .@BASE' by default.  If you pass an explicit revision
you'll get identical output: 'svn ls -r HEAD'.

This could also be caused by authz settings.
Reply | Threaded
Open this post in threaded view
|

Re: 'svn ls' not showing the contents of the repository

Anton Shepelev
Daniel Shahaf to Anton Shepelev:

> > Why can 'svn ls' show different results when invoked
> > from two working copies of the same repository?
>
> Probably because the working copy's BASE revision is
> different.  'svn ls' runs 'svn ls .@BASE' by default.

Disregarding what is writ in the Book?

> If you pass an explicit revision you'll get identical
> output: 'svn ls -r HEAD'.

So I must either commit or update the whole working copy in
order for the new directory to become availble for download
to the workng copy?

> This could also be caused by authz settings.

Impossible.

--
Please, do not forward replies to my e-mail.

Reply | Threaded
Open this post in threaded view
|

Re: 'svn ls' not showing the contents of the repository

Branko Čibej
In reply to this post by Daniel Shahaf-2
On 29.11.2017 18:34, Daniel Shahaf wrote:
> Anton Shepelev wrote on Wed, 29 Nov 2017 20:18 +0300:
>> Why can 'svn ls' show different results when invoked from
>> two working copies of the same repository?
> Probably because the working copy's BASE revision is different.  'svn ls'
> runs 'svn ls .@BASE' by default.  If you pass an explicit revision
> you'll get identical output: 'svn ls -r HEAD'.

If it's "svn ls URL" then the default revision is HEAD, not BASE.

-- Brane

Reply | Threaded
Open this post in threaded view
|

Re: 'svn ls' not showing the contents of the repository

Lorenz-2
In reply to this post by Daniel Shahaf-2
Daniel Shahaf wrote:
>Anton Shepelev wrote on Wed, 29 Nov 2017 20:18 +0300:
>> Why can 'svn ls' show different results when invoked from
>> two working copies of the same repository?
>
>Probably because the working copy's BASE revision is different.  'svn ls'
>runs 'svn ls .@BASE' by default.  If you pass an explicit revision
>you'll get identical output: 'svn ls -r HEAD'.

Then perhaps this fact should be mentioned in the BOOK and "svn help
ls".

"The default TARGET is “.”, meaning the repository URL of the current
working copy directory."

vs.

"The default TARGET is “.@BASE”, meaning the repository URL of the
current working copy directory at the time of checkout or last
update."


Lorenz