Re: svn client has inconsistent returnstatus for non-existing local files

[Daniel Shahaf <d....@daniel.shahaf.name>]

Sjon Hortensius wrote on Thu, Sep 16, 2010 at 17:04:19 +0200:
> LS,
> 
> Please advise if this is a bug, or a known feature. I have a local
> checkout on which I can execute svn commands. However, there seems to
> be some inconsistency in the exitcode of the client.
> 
> `svn ls repository/non-existing` exits with status 1, and so does `svn
> info repository/non-existing`. However, `svn ls
> repository/non-existing` has exit-status 0, although it echo's a "svn:
> warning: "
> 

Using trunk, both 'ls' and 'info' return non-zero, for both URLs and
paths under local working copies.  (But you said 'svn ls' twice; was
that a typo?)

> Is this a (known) bug? Can I post this issue on the bugtracker?
> 

If 'svn' reports an error that cannot be detected by a calling script,
then please post an issue.

> Thanks,
> 
> Sjon Hortensius

Re: svn client has inconsistent returnstatus for non-existing local files

[Daniel Shahaf <d....@daniel.shahaf.name>]

Sjon Hortensius wrote on Tue, Sep 21, 2010 at 09:19:17 +0200:
> Thanks for your reply, and yes, it seems I made an error describing
> the actual bug. I meant the exit-status of `svn cat`; which differs.
> 
> > If 'svn' reports an error that cannot be detected by a calling script,
> > then please post an issue.
> 
> I will do that, thanks!

I can reproduce the issue with 'cd $wc; svn cat ./nonexistent' with
current trunk.

Re: svn client has inconsistent returnstatus for non-existing local files

[Sjon Hortensius <Sj...@hortensius.net>]

On Tue, Sep 21, 2010 at 12:01 AM, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> Sjon Hortensius wrote on Thu, Sep 16, 2010 at 17:04:19 +0200:
>> LS,
>>
>> Please advise if this is a bug, or a known feature. I have a local
>> checkout on which I can execute svn commands. However, there seems to
>> be some inconsistency in the exitcode of the client.
>>
>> `svn ls repository/non-existing` exits with status 1, and so does `svn
>> info repository/non-existing`. However, `svn ls
>> repository/non-existing` has exit-status 0, although it echo's a "svn:
>> warning: "
>>
>
> Using trunk, both 'ls' and 'info' return non-zero, for both URLs and
> paths under local working copies.  (But you said 'svn ls' twice; was
> that a typo?)

Thanks for your reply, and yes, it seems I made an error describing
the actual bug. I meant the exit-status of `svn cat`; which differs.

>> Is this a (known) bug? Can I post this issue on the bugtracker?
>>
>
> If 'svn' reports an error that cannot be detected by a calling script,
> then please post an issue.
>
>> Thanks,
>>
>> Sjon Hortensius
>

I will do that, thanks!