Hi!
I am unable to build certain packages from a custom-packages input in my
cuirass-specs below, and am triggering the below backtrace with below
config. The packages that trigger the errors can successfully be
installed otherwise by pointing to them with a guix channel. Failure
happens when
Does this mean I have non-free firmware?
I put "modprobe.blacklist=i915" in grub, but the problem is not resolved.
I am confused! Is there no solution?
Do you have another Linux Live Distro at hand to check what the device at
USB 1-1.3 actually is? This might help.
Malte
On Sun, 1 Nov 2020, 14:06 soheilkhanalipur--- via Bug reports for GNU Guix,
wrote:
> Does this mean I have non-free firmware?
> I put "modprobe.blacklist=i915" in grub, but t
Hi Jesse,
Jesse Gibbons writes:
> The --no-clear option is hard-coded for mingetty, with no documentation
> about why. The mingetty page says,
> --noclear
> Do not clear the screen before prompting for the login
> name (the
> screen is normally cleared).
>
Here's a revised patch, still untested, that also updates the
documentation.
Mark
>From 9229d0493cdbb521a2f7a821d47d60d2392b8447 Mon Sep 17 00:00:00 2001
From: Mark H Weaver
Date: Sun, 1 Nov 2020 11:16:08 -0500
Subject: [PATCH] UNTESTED: gnu: mingetty-shepherd-service: Make
'clear-on-log
Hey Maxim,
> Perhaps we should run 'vacuum' when invoking 'guix gc' or at some other
> key places (where lots of data gets removed from the DB). There's also
> the auto_vacuum PRAGMA, which is not enabled currently:
Vacuuming periodically seems important, however, it didn't resulted in
noticea
Hello Miguel,
> + ;; TRANSLATORS: The ~{ and ~} format specifiers are used to iterate the
> list
> + ;; of device names of the user partitions that will be formatted.
> + (run-confirmation-page (format #f (G_ "We are about to write the
> configured \
> +partition table to the disk and forma
Hello David,
> ice-9/boot-9.scm:1667:16: In procedure raise-exception:
> ERROR:
> 1. &evaluation-error:
> name: "my-pkgs"
> id:
Thanks for the bug report. Could you please send the associated log
trace in /var/log/cuirass/evaluations/xxx.gz?
Mathieu
On 2020-11-01 19:53, Mathieu Othacehe wrote:
Hello David,
ice-9/boot-9.scm:1667:16: In procedure raise-exception:
ERROR:
1. &evaluation-error:
name: "my-pkgs"
id:
Thanks for the bug report. Could you please send the associated log
trace in /var/log/cuirass/evaluations/xxx.gz?
M
Hi Mark,
Mark H Weaver skribis:
> In the meantime, does anyone object to changing the default behavior to
> clear-on-logout, which is the upstream default?
Fine with me; it’s probably a safer default.
> From 61d0055493c46cdee178d0ffbbf15742de930028 Mon Sep 17 00:00:00 2001
> From: Mark H Weave
Hi,
Bombadillo package fails to build.
This is the error I get, which like proposed in [1] doesn't show meaningful
information.
```
starting phase `install-license-files'
installing 1 license files from '.'
Backtrace:
11 (primitive-load "/gnu/store/mrrxfmi21va142li2jwh7w3cksv…")
In i
Ekaitz,
Ekaitz Zarraga 写道：
Bombadillo package fails to build.
Please update your Guix (with ‘$ guix pull’). This issue was
fixed some time ago[0].
If the error persists, please post the output of ‘$ guix
describe’.
Thanks!
T G-R
[0]: http://issues.guix.gnu.org/44127
signature.asc
De
While building the package of Guix itself [0], I noticed that Savannah
can't serve cheap "shallow clones" of the commits that these packages
are based on, so users will end up doing full clones (260M on
disk):
--
building
/gnu/store/ma04vkl42jyr9p2nw5yzlzw61r5s2h3p-guix-1.1.0-31.1c6d985-check
I poked around a bit and found that Savannah can serve shallow clones of
random commits, but does not allow shallow *fetching*, except for
special things such as Git tags. We fetch instead of clone.
Here's the output for the failing tests:
--8<---cut here---start->8---
96/99 pipelines_wavpack OK 0.82 s
97/99 orc_deinterlace FAIL 0.07 s (killed by signal
11 SIGSEGV)
98/99 orc_videomixer
15 matches
Mail list logo
