bug#41710: Possibly found a bug while doing a "guix pull"

[Julien Lepiller <julien@lepiller.eu>]

Le 4 juin 2020 10:38:09 GMT-04:00, "Léon Lain Delysid" <leon.lain.delysid@gmail.com> a écrit :
>Hello!
>I just tried to "guix pull" on my Debian Buster GNU/Linux system. Twice
>it
>made the system completely freeze for a few seconds and then reboot.
>And
>that third time it didn't crash the system but the guix pull failed and
>returned this error:
>https://pastebin.com/vhDR8gDC
>
>Can somebody help me please?
>
>(Before doing the third "pull", I did an "apt update" and "upgrade",
>but I
>wasn't that much behind in updates, I had done it less than a week ago
>last. My last "guix pull" was made at the same time as the "apt
>update", a
>few days ago.)
>
>Hoping I can resolve this soon or that my feedback was positive for the
>development of Guix. =)
>I can provide log debug info (if there is any) upon request.
>
>Best regards!

Sorry pastebin is not tor friendly, I couldn't look at it.

For the freezing part, could it be that you have relatively low free ram (<2GB) and no swap? Or maybe /tmp is mounted as a tmpfs and for some reason it takes a lot of space?

You might need to use substitutes when runnning guix pull. I don't have that much ram either on some computers, so I always take a look at https://ci.guix.gnu.org/jobset/guix-modular-master and choose the latest commit that was built for my architeeture. Then eg. guix pull --commit=c987b72

This will allow guix to download substitutes for guix pull instead of building locally, which doesn't require any ram usage.

HTH!