From: Petter Gustad on

It seems like whenever I run clbuild it will hang at some point, e.g.

../clbuild install weblocks
....
NEW darcs get cffi
Copying patches, to get lazy repository hit ctrl-C...
Copying patches 218/678

I can break it and restart it, but it will eventually hang on some
random darcs get operation:

NEW darcs get cl-ppcre
Identifying repository http://common-lisp.net/~loliveira/ediware/cl-ppcre

The network connection appears to be fine. Have anybody else
experienced this kind of behaviour with clbuild? It might be a problem
with darcs as well (I'm running 2.0.2).


Petter
--
..sig removed by request.
From: D Herring on
On 05/13/2010 03:00 PM, Petter Gustad wrote:
>
> It seems like whenever I run clbuild it will hang at some point, e.g.
>
> ./clbuild install weblocks
> ...
> NEW darcs get cffi
> Copying patches, to get lazy repository hit ctrl-C...
> Copying patches 218/678
>
> I can break it and restart it, but it will eventually hang on some
> random darcs get operation:
>
> NEW darcs get cl-ppcre
> Identifying repository http://common-lisp.net/~loliveira/ediware/cl-ppcre
>
> The network connection appears to be fine. Have anybody else
> experienced this kind of behaviour with clbuild? It might be a problem
> with darcs as well (I'm running 2.0.2).

Hmm... That feels familiar. Don't remember why.

I would definitely recommend upgrading darcs. It has silently
corrupted the gzip checksum for a long time; the latest versions
automatically detect the problem and offer commands to fix it.

- Daniel
From: Pascal J. Bourguignon on
D Herring <dherring(a)at.tentpost.dot.com> writes:

> On 05/13/2010 03:00 PM, Petter Gustad wrote:
>>
>> It seems like whenever I run clbuild it will hang at some point, e.g.
>>
>> ./clbuild install weblocks
>> ...
>> NEW darcs get cffi
>> Copying patches, to get lazy repository hit ctrl-C...
>> Copying patches 218/678
>>
>> I can break it and restart it, but it will eventually hang on some
>> random darcs get operation:
>>
>> NEW darcs get cl-ppcre
>> Identifying repository http://common-lisp.net/~loliveira/ediware/cl-ppcre
>>
>> The network connection appears to be fine. Have anybody else
>> experienced this kind of behaviour with clbuild? It might be a problem
>> with darcs as well (I'm running 2.0.2).
>
> Hmm... That feels familiar. Don't remember why.
>
> I would definitely recommend upgrading darcs. It has silently
> corrupted the gzip checksum for a long time; the latest versions
> automatically detect the problem and offer commands to fix it.

Perhaps. Personnaly I've upgraded to git. The fact that haskell seems
harder to port to various platforms (specifically cygwin) than Common
Lisp implementations didn't help me staying with darcs either.


--
__Pascal Bourguignon__
From: D Herring on
On 05/13/2010 10:02 PM, Pascal J. Bourguignon wrote:
> D Herring<dherring(a)at.tentpost.dot.com> writes:
>> I would definitely recommend upgrading darcs. It has silently
>> corrupted the gzip checksum for a long time; the latest versions
>> automatically detect the problem and offer commands to fix it.
>
> Perhaps. Personnaly I've upgraded to git. The fact that haskell seems
> harder to port to various platforms (specifically cygwin) than Common
> Lisp implementations didn't help me staying with darcs either.

For the casual observer: find a pre-built, static darcs binary. You
do not want to do a full haskell install with all its libraries just
to run darcs.

On linux, the 32-bit binary may appear to run on 64-bit systems; but
it will have obscure download errors until you install the 32-bit
compatibility libs.

- Daniel
From: Petter Gustad on
D Herring <dherring(a)at.tentpost.dot.com> writes:

> I would definitely recommend upgrading darcs. It has silently

Thank you for your suggestion. Upgrading to 2.2.1 resolved the
problem.

Petter
--
..sig removed by request.