Hello,
Thanks for the bug report and sorry for the inconvenience.
> In gnu/system/uuid.scm:
> 317:2 18 (uuid->string . _)
It looks like the UUID extraction of an "ext4" partition failed. Did you
use automatic or manual partitioning?
Thanks,
Mathieu
Does the answer on the following page solve the problem?
https://unix.stackexchange.com/questions/621179/guix-system-problem-with-gnome-boxes
File Modified:
[]
Problem not solved...
Hello,
The glib build is broken on armhf due to a timeout in the test suite,
see:
https://ci.guix.gnu.org/log/m6rd864j30khc6k60gr2wqr1pz40f1di-glib-2.62.6-bin.
It looks like it's also broken on the 1.2.0 branch.
This prevents the evaluation of the guix-modular specification, see:
https://ci.gu
In the interest of protecting users we should probably not create DCA
keys by default. That would leave us with RSA, ECDSA and ED25519.
--
Efraim Flashner אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received
Done
Solved
[1]
[2]
[3]
Thanks to those who helped me for solve the problem(Ben Sturmfels, ...).
On Mon, Nov 16, 2020 at 07:24:28PM +0100, Marius Bakke wrote:
> Hello,
>
> On the 'staging' branch, the "alacritty" package fails to build:
>
> --8<---cut here---start->8---
> starting phase `build'
> error: --features is not allowed in the root of a virtual wo
--dry-run is an option listed in `guix deploy --help` but when I try it,
it isn't recognized:
$ guix deploy --dry-run deploy.scm
guix deploy: error: dry-run: unrecognized option
Hi znavko,
zna...@disroot.org skribis:
> Hello! I use Xfce4 under Guix OS. I have several Shortcuts in Launchers on
> Xfce4 Panel:
> IceCat, Gimp, Ungoogled-Chrom, PcmanFM.
> Every time I update software, delete old generations and run garbage collector
> this removes packages from the /gnu/stor
Hi!
Vagrant Cascadian skribis:
> My *wild* guess is it maybe has something to do with the use of
> canonicalize-path:
>
> (define (find-current-checkout arguments)
> "Find the first checkout of ARGUMENTS that provided the current file.
> Return #f if no such checkout is found."
> (let ((cu
Hi,
Vagrant Cascadian skribis:
> Updating the build dependency to libgit2-dev >= 1.0.1 (which pulls in a
> similar version to what guix is using) fixes test suite failures ... but
> only on the amd64 architecture. The same tests pass Using an older
> version of libgit2-dev (0.28). FWIW, this is
Hi,
after the installation of ungoogled-chromium I tried to run it,
receiving this message:
[20998:20998:1126/122306.639343:FATAL:zygote_host_impl_linux.cc(117)] No
usable sandbox! Update your kernel or see
https://chromium.9oo91esource.qjz9zk/chromium/src/+/master/docs/linux/suid_sandbox_developm
Hi Chris,
Christopher Lemmer Webber skribis:
> Seems strange... the message I get:
>
> guix deploy: error: failed to deploy tulsi: ~A: ~S
>
> Errors upon errors! Formatting this time, apparently. :)
>
> Looking at the relevant code:
>
> (define (deploy-machine* store machine)
> "Deploy MACH
On Thu, 26 Nov 2020 16:53:29 +0100
Andrea Rossi via Bug reports for GNU Guix wrote:
> Hi,
> after the installation of ungoogled-chromium I tried to run it,
> receiving this message:
>
> [20998:20998:1126/122306.639343:FATAL:zygote_host_impl_linux.cc(117)]
> No usable sandbox! Update your kernel
On Thu, 26 Nov 2020 15:30:31 +0100 (CET)
musics--- via Bug reports for GNU Guix wrote:
> Solved
> [1]
> [2]
> [3]
>
>
> Thanks to those who helped me for solve the problem(Ben Sturmfels,
> ...).
in the future, please copy the text instead of taking a screenshot. it
makes it easier for others t
On 2020-11-26, Ludovic Courtès wrote:
> Vagrant Cascadian skribis:
>
>> Updating the build dependency to libgit2-dev >= 1.0.1 (which pulls in a
>> similar version to what guix is using) fixes test suite failures ... but
>> only on the amd64 architecture. The same tests pass Using an older
>> versi
17 matches
Mail list logo
