[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: "svn info" good return code on bad URL

From: John Belmonte <john_at_neggie.net>
Date: 2005-10-10 13:40:08 CEST

Peter N. Lundblad wrote:
> On Mon, 9 Oct 2005 kfogel@collab.net wrote:
>>John Belmonte <john@neggie.net> writes:
>>>>I expect "svn info <URL>" to have a non-zero rcode if the URL is not
>>>>valid. Seen in version 1.2.3. May I file a bug?
>>>> $ svn info http://svn.collab.net/repos/svn/bad_url
>>>> http://svn.collab.net/repos/svn/bad_url: (Not a valid URL)
>>>> $ echo $?
>>>> 0
>>>One more thing... the error message above should be on stderr, not stdout.
>>I think this should be a bug, yes -- consider your bug buddied :-).
>>And agree about stderr vs stdout.
> In r15065, the warnings were moved from stdout to stderr, so the situation
> on trunk is a little better:-)
> The problem with the return code is that these are handled like warnings,
> a message is printed and we continue with the next target (but the output
> is not preceded by svn: warning: as it should). So we can't return a
> failure status in this case.

Hi Peter,

Are you saying that you can't correct the return code problem? Surely
it's arbitrary (from the point of view of the client) that the case
above succeeds while the following fails. Any bad URL should fail.

  $ svn info http://svn.collab.net/repos/svn_bad
  svn: PROPFIND request failed on '/repos/svn_bad'
  svn: PROPFIND of '/repos/svn_bad': 405 Method Not Allowed
  $ echo $?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 10 13:41:34 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.