Hi Ludo,
Ludovic Courtès writes:
> Hi,
>
> Maxim Cournoyer skribis:
>
>> Ludovic Courtès writes:
>
> [...]
>
>>> The one that doesn’t is a private video-conferencing thing at work (not
>>> running Jitsi but very similar). With the commit above, it says “Error
>>> code: 4” (the GPU error was
Hello,
Maxim Cournoyer writes:
> Hello Ludovic,
>
> Maxim Cournoyer writes:
>
>> Hello again!
>>
>> Maxim Cournoyer writes:
>>
>>> Hello!
>>>
>>> Ludovic Courtès writes:
>>>
>>> [...]
>>>
The “@ download-progress” line is printed by (guix scripts substitute)
and later consumed by
Hi Guix,
I believe that this is a feature request. I would like to create a Guix
qcow2 image to run as a VM. Additionally, I would like the root file
system to be btrfs. Therefore, I created an operating system definition
with the following file-systems:
```
(file-systems (cons (file-system
Hi all,
I was able to bisect this down to a few kernel configuration options, so
perhaps those with more kernel experience can help me track down what’s going
on.
The two Kconfig options which seem to influence the behavior are:
1. CONFIG_EXPERT
2. CONFIG_UID16
CONFIG_EXPERT=y, CONFIG_UID16=y
Hi,
The commit bea3b17739fc591b8cf6db1f8d28a6f6c9585577 changed a bit the
importers. However, even before this commit, the errors are incorrectly
reported for ’gnu’ and ’json’, without the --recursive option, e.g,
commit 23e2cd156f. And bea3b17739 does not change anything. This very
same
On 2021-01-18, Julien Lepiller wrote:
> What does the log say? It should list test failures at the end.
I don't have the system handy at the moment, but there is a recent build
log failure from staging:
https://ci.guix.gnu.org/build/187255/log/raw
It appears to have logged 6 failures, though
Hi!
On #bootstrappable, mid-kid reported that ‘binutils-mesboot0’ in
commencement.scm lacks ‘--enable-deterministic-archives’. So I checked
if this had an effect by running:
guix build -e '(@@ (gnu packages commencement) gcc-core-mesboot0)' \
--check -K
and yes, it does:
Hi,
Leo Prikler skribis:
>> > diff --git a/gnu/system/shadow.scm b/gnu/system/shadow.scm
>> > index 0538fb1a24..7c57222716 100644
>> > --- a/gnu/system/shadow.scm
>> > +++ b/gnu/system/shadow.scm
>> > @@ -321,13 +321,13 @@ of user '~a' is undeclared")
>> > objects. Raise an error if a user
Hey Chris,
> The behaviour is configurable, but the default missing inputs hook will
> submit a new build for a missing input, but only if one doesn't already
> exist. Because of this, you don't get the behaviour where some missing
> prerequisite that fails to built is built over and over
What does the log say? It should list test failures at the end.
Le 17 janvier 2021 15:56:34 GMT-05:00, Vagrant Cascadian a
écrit :
>php 7.4.14 fails to build on aarch64 due to test suite failures.
>
>Reverting back to php 7.4.13 by reverting commit
>d033540e6c113323089403a26e39f9a288c9c857
Hi Mathieu,
sorry, didn't have much time to play with Guix recently.
All I can say is that I haven't experienced the issue lately.
I'm on commit c03875b0361f114634caeb54935fe37a9b7b05af.
I'll try the commands you suggested later. Thanks for your time!
signature.asc
Description: PGP signature
11 matches
Mail list logo
