bug#75134: Issue with guix pull

Glad to hear --cores=1 helped! I have seen some strange behavior in x86_64 qemu VMs, but also --cores=1 did help me build rust-1.54 bootstrap on x86_64. It also might be a bug in guix-daemon, perhaps only in the old 1.4.0 revision, judging from how the error message says store protocol error. I

bug#75134: Issue with guix pull

Florian, Another idea would be to pull on one core > > guix pull --cores=1 Thanks for this tip! It did the trick and pull worked. But I don't understand _why_ it worked. Is there just some extra complexity with M chips and multiple cores and/or VMs? Thanks again! -- Eric

bug#75134: Issue with guix pull

Hi Eric. 8 GiB of RAM must be enough, since guix pull can run on 32-bit i686-linux. Another idea would be to pull on one core guix pull --cores=1 or generally to enable more debug output like guix pull --debug=4 I remember how someone used Guix on Ubuntu in a UTM virtual machine on a Macbook

bug#75134: Issue with guix pull

Hi Florian! Is this a Macbook? Perhaps bug > is relevant. > > Otherwise, perhaps you have insufficient RAM and should call `swapon` on > a swapfile first. > Sorry, I should have provided more information. I am indeed on a Macbook M1, but am running everything in VMs

bug#75134: Issue with guix pull

Hello Eric. Eric Gade writes: > failed to compute the derivation for Guix (version: > "8f24cefc2c8f91ab63bdf5f816ca49fa7adb43d7"; system: "aarch64-linux"; > host version: "1.4.0rc2"; pull-version: 1). > Please report the COMPLETE output above by email to . Is this a Macbook? Perhaps bug