From: Jonathan Roberts via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 69596@debbugs.gnu.org
Subject: bug#69596: Possibly breaks Guix pull on foreign distros
Date: Tue, 30 Apr 2024 09:38:33 +0100 [thread overview]
Message-ID: <48BA9CD1-7ED9-4FB9-9BB6-3A4E91E0C5CA@googlemail.com> (raw)
In-Reply-To: <87zfvb6nwi.fsf@inria.fr>
Ran in to the error that a lot of people are reporting - too many heap sections on Guix pull.
Worked through commits to see where Guix pull stopped working for me, and the answer seems to be that it broke with 7cef6b7ba - gnu: guile-lzlib: Update to 0.3.0.
Could this be confirmed and reverted if it is breaking pull?
Sent from my iPhone
prev parent reply other threads:[~2024-04-30 22:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 21:39 bug#69596: ‘guix publish’ memory leak Ludovic Courtès
2024-04-28 22:03 ` Ludovic Courtès
2024-04-30 8:38 ` Jonathan Roberts 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=48BA9CD1-7ED9-4FB9-9BB6-3A4E91E0C5CA@googlemail.com \
--to=bug-guix@gnu.org \
--cc=69596@debbugs.gnu.org \
--cc=jonrob.one@googlemail.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).