unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: xdrcft56 via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 53511@debbugs.gnu.org
Subject: bug#53511: guix pull command fails
Date: Wed, 26 Jan 2022 18:59:50 +0000	[thread overview]
Message-ID: <fsQDwop1CVYbdePqUS37Megz7LgrgoHhl3Oaob14a7gS-vmJ0n5pvgajlzWOn2zm1hlpPR04BXn-a9Sorp2OM560sFySJpQ7M5DPTCQ4RWM=@protonmail.com> (raw)
In-Reply-To: <fswxmP-UwRLodTcGZGoN05ZqzU-s-hdk-fUUuZSyg9pezwDmyZlflLc-XwgL-CZ1KIxKYMsANN_T4IBfvsFD09q7dn3RLQZgL1qNB6b5idc=@protonmail.com>

After debugging this a bit deeper, I see that libgit2.so.1.1.0 is generating the error message "error inflating zlib stream".  Which leads me to suspect that the reason I can't "guix pull" is related to guile-git.

I've already reinstalled guix and the error persists.

Is there a way to update guile-git/libgit2.so.1.1.0 without having the ability to "guix pull && guix package -u"?

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Tuesday, January 25th, 2022 at 1:32 PM, xdrcft56 <xdrcft56@protonmail.com> wrote:

> I attempted the "guix pull --cores=2 --max-jobs=1" command as root and received the following output and error:
>
> Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
>
> guix pull: error: Git error: error inflating zlib stream
>
> I also ran "guix archive --authorize < ~root/.config/guix/current/share/guix/ci.guix.gnu.org.pub" in order enable and authorize a substitute but received the same error as above upon running "guix pull --cores=2 --max-jobs=1" subsequently.
>
> Finally, I reviewed dmesg and saw no change during the course of executing these commands.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>
> On Tuesday, January 25th, 2022 at 2:59 AM, Maxime Devos maximedevos@telenet.be wrote:
>
> > xdrcft56 schreef op ma 24-01-2022 om 23:35 [+0000]:
> >
> > > Thank you. I've attached the requested log file (/var/log/guix/drvs/aj/mmafhpmi83ssxg860wd93z9yhhhk5w-gcc-10.3.0.drv.bz2).
> >
> > ‘collect2: fatal error: ld terminated with signal 9 [Killed]’
> >
> > this could indicate an out-of-memory situation, which Guix cannot
> >
> > really do anything about. If it is a OOM, the dmesg should contain a
> >
> > message about it (I don't know exactly how it looks like). A future
> >
> > OOM can be avoided by closing some memory intensive applications (e.g.
> >
> > most web browsers) and reducing the number of cores used for building:
> >
> > "guix pull --cores=2 --max-jobs=1".
> >
> > In principle, it could be something else though. Can you reproduce
> >
> > with "guix pull --cores=2 --max-jobs=1"?
> >
> > Also, I'm noticing you are building everything from source.
> >
> > To avoid having to build things (and hence reduce the chance of
> >
> > an OOM) (and save energy), I recommend enabling and authorising
> >
> > substitutes.
> >
> > Greetings,
> >
> > Maxime.




      reply	other threads:[~2022-01-26 19:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 18:28 bug#53511: guix pull command fails xdrcft56 via Bug reports for GNU Guix
2022-01-24 21:25 ` Maxime Devos
2022-01-24 23:35   ` xdrcft56 via Bug reports for GNU Guix
2022-01-25  7:59     ` Maxime Devos
2022-01-25 18:32       ` xdrcft56 via Bug reports for GNU Guix
2022-01-26 18:59         ` xdrcft56 via Bug reports for GNU Guix [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='fsQDwop1CVYbdePqUS37Megz7LgrgoHhl3Oaob14a7gS-vmJ0n5pvgajlzWOn2zm1hlpPR04BXn-a9Sorp2OM560sFySJpQ7M5DPTCQ4RWM=@protonmail.com' \
    --to=bug-guix@gnu.org \
    --cc=53511@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=xdrcft56@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).