darcs

Issue 2103 darcs changes --repo URL doesn't work in 2.5.2 (stable)

Title darcs changes --repo URL doesn't work in 2.5.2 (stable)
Priority bug Status resolved
Milestone Resolved in
Superseder Nosy List dixiecko, twb
Assigned To twb
Topics

Created on 2011-10-26.14:47:46 by dixiecko, last changed 2011-10-27.15:09:12 by dixiecko.

Messages
msg14782 (view) Author: dixiecko Date: 2011-10-26.14:47:45
From IRC:
06:51 < twb> This used to work, right: darcs changes --repo
http://cyber.com.au/~twb
06:51 < twb> Now it doesn't (2.5.2)

Related response:
16:39 < sm> hi twb. Works here with darcs 2.7.98.1 (darcs-beta)
msg14784 (view) Author: dixiecko Date: 2011-10-26.21:02:32
I can not see any problem:
$ darcs --version
2.5.2 (release)
$ darcs changes --repo http://cyber.com.au/~twb | wc -l  
7283                                                  

Can you describe problem? 
Can you try execute that command with --debug-verbose?

Thanks!
msg14785 (view) Author: twb Date: 2011-10-26.22:18:01
Radoslav Dorcik wrote:
> 
> Radoslav Dorcik <dixiecko@gmail.com> added the comment:
> 
> I can not see any problem:
> $ darcs --version
> 2.5.2 (release)
> $ darcs changes --repo http://cyber.com.au/~twb | wc -l  
> 7283                                                  
> 
> Can you describe problem? 
> Can you try execute that command with --debug-verbose?

It was almost certainly a permissions problem; it's working now.
The error claimed it wasn't a repo at all, which led me astray.
msg14787 (view) Author: dixiecko Date: 2011-10-27.15:09:11
Ok.

And it seems that beta version of the darcs (2.7.98.1) already provides
in error message also HTTP Error code (e.g. 401, 404). But I'm not able
to track down the exact issue number related to this improvement.
History
Date User Action Args
2011-10-26 14:47:46dixieckocreate
2011-10-26 21:02:33dixieckosetstatus: needs-reproduction -> waiting-for
assignedto: dixiecko -> twb
messages: + msg14784
2011-10-26 22:18:02twbsetmessages: + msg14785
2011-10-27 15:09:12dixieckosetstatus: waiting-for -> resolved
messages: + msg14787