I just discovered that 4 out of 5 armhf build slots on Hydra have been
stuck for 24 hours, apparently after the network connections to the
build slaves were lost, possibly due to a temporary network outage.
I've seen this kind of thing happen periodically since we switched to
using guile-ssh for o
```
Some deprecated features have been used. Set the environment
variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
program to get more information. Set it to "no" to suppress
this message.
make[1]: Leaving directory
'/tmp/guix-build-guile-ssh-0.11.3.drv-0/guile-ssh-0.11.3/tests'
make
Hello,
Reed Campbell Meyerson skribis:
> I am experiencing some strange behavior when upgrading packages. After a
> substitution fails, the upgrade will fail at the same point every time
> until I upgrade that point on its own, and then it will proceed until it
> potentially fails at a different
On Fri, 16 Nov 2018 21:51:49 +0100
l...@gnu.org (Ludovic Courtès) wrote:
> Hello,
>
> Björn Höfling skribis:
>
> > is this a bug or by intention?
> >
> > In src/cuirass/database.scm, in the db-add-* procedures, we have a
> > catch-clause like this:
> >
> > (with-db-critical-section db
> > (ca
Hello,
Björn Höfling skribis:
> is this a bug or by intention?
>
> In src/cuirass/database.scm, in the db-add-* procedures, we have a
> catch-clause like this:
>
> (with-db-critical-section db
> (catch 'sqlite-error
> (lambda ()
> )
> (lambda (key who code message . rest)
>
Hello,
Ricardo Wurmus skribis:
> I’ve just got the very same error:
>
> downloading from
> https://berlin.guixsd.org/nar/gzip/iql35g1g5q9dkap5splc7f9ggskr31vl-NamesList.txt...
> Backtrace:
> In guix/scripts/package.scm:
>913:10 19 (_)
> In guix/status.scm:
> 600:4 18 (call-with-status-r
Hi,
is this a bug or by intention?
In src/cuirass/database.scm, in the db-add-* procedures, we have a
catch-clause like this:
(with-db-critical-section db
(catch 'sqlite-error
(lambda ()
)
(lambda (key who code message . rest)
;; If we get a unique-constraint-failed error
Danny Milosavljevic skribis:
>> It is kind of documented under the '--socket' option of Shepherd:
>>
>> https://www.gnu.org/software/shepherd/manual/shepherd.html
>
> Shouldn't it be:
>
> Receive further commands on the socket special file file. If this option is
> not specified, localstatedir/
> It is kind of documented under the '--socket' option of Shepherd:
>
> https://www.gnu.org/software/shepherd/manual/shepherd.html
Shouldn't it be:
Receive further commands on the socket special file file. If this option is not
specified, localstatedir/run/shepherd/socket is taken when running
