Hi Maxim,
> I agree! We don't want people to send bug reports every time their
> network is flaky, if this is indeed what has happened. Would you be
> interested at surveying if that's the case in the current code? Perhaps
> the right change would then become apparent.
Interested, maybe, but I
Hi Konrad,
Konrad Hinsen writes:
> Hi Maxim,
>
> Thanks for your reply!
>
>> Indeed. I note that the error message that leads to a request to the
>> bug report mention it could be due to a network failure, which could
>> explain the transient nature of the problem we see here.
>>
>> Had you tri
Hi Maxim,
Thanks for your reply!
> Indeed. I note that the error message that leads to a request to the
> bug report mention it could be due to a network failure, which could
> explain the transient nature of the problem we see here.
>
> Had you tried multiple times in a row with the same failur
Hi Konrad!
Konrad Hinsen writes:
> Trying the "guix pull" a short while (and one commit to Guix) later, the
> error is gone. Which is a bit strange: whatever the cause of the error
> was, it's hard to believe that adding the package
> "python-sqlalchemy-stubs" (which is what commit
> f8a4724c101
Trying the "guix pull" a short while (and one commit to Guix) later, the
error is gone. Which is a bit strange: whatever the cause of the error
was, it's hard to believe that adding the package
"python-sqlalchemy-stubs" (which is what commit
f8a4724c101880892640dcc2fe3438dc2a26b624 did) could fix i
Today's "guix pull" resulted in an error message that ends with a
request for a bug report. So here it comes:
===
Updating channel 'guix-past' from Git repository at
'https://gitlab.inria.fr/guix-hpc/guix-past'...
Updating ch
