From: Peacememories <peacememories@posteo.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 70659@debbugs.gnu.org
Subject: bug#70659: Too many heap sections on guix pull
Date: Tue, 30 Apr 2024 15:34:17 +0000 [thread overview]
Message-ID: <6458e7390af2b1f97ced47e0a885e470@posteo.net> (raw)
In-Reply-To: <87ikzzxlj0.fsf@gnu.org>
Hi, thanks for the quick reply!
On 30.04.2024 11:11, Ludovic Courtès wrote:
> Hi,
>
> Peacememories <peacememories@posteo.net> skribis:
>
>> `guix pull` on a fresh install on WSL Ubuntu 24.04 fails with the
>> following log.
>>
>> The same happened to me when trying GUIX on NixOS 23.11 via the
>> `services.guix` option.
>>
>> ```
>>
>> hint: Consider installing the `glibc-locales' package and defining
>> `GUIX_LOCPATH', along these lines:
>>
>> guix install glibc-locales
>> export GUIX_LOCPATH="$HOME/.guix-profile/lib/locale"
>>
>> See the "Application Setup" section in the manual, for more info.
>>
>> Updating channel 'guix' from Git repository at
>> 'https://git.savannah.gnu.org/git/guix.git'...
>> Authenticating channel 'guix', commits 9edb3f6 to ddf3759 (29,446 new
>> commits)...
>> Building from this channel:
>> guix https://git.savannah.gnu.org/git/guix.git ddf3759
>
> [...]
>
>> -Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
>> guix pull: error: You found a bug: the program
>
> Thanks for the report. As someone confirmed on IRC, this was caused by
> 7cef6b7ba555a9dfaf6d09cb7e112b0df77d5114, which introduced a circular
> dependency, but only for those systems running a version of guix-daemon
> lacking “builtin:git-download” (added in Sept. 2023).
>
> Commit df3d30819e650a490ef39dd6692740bb13263c75 fixes that; you should
> be able to pull now.
I can indeed confirm that
(1) Using an older commit caused the error to disappear
(2) Pulling the newest version now seems to work as well
>
> I would recommend upgrading guix-daemon though, as noted in:
>
> https://guix.gnu.org/manual/devel/en/html_node/Upgrading-Guix.html
>
> One of the main reasons to do so is this:
>
>
> https://guix.gnu.org/en/blog/2024/fixed-output-derivation-sandbox-bypass-cve-2024-27297/
I'll definitely update guix on the WSL installation (I had just done the
initial installation which presumably comes with an older version), but
I think I'll hold off on the update in NixOS. For one, trying to change
the binary and service definition under Nix' nose seems dangerous, but
also it seems that Nix already backported the CVE fix you mentioned
(https://github.com/NixOS/nixpkgs/blob/12430e43bd9b81a6b4e79e64f87c624ade701eaf/pkgs/by-name/gu/guix/package.nix#L47-L58)
Just thought I'd mention that here in case anyone stumbles across this
in a similar situation
All the best,
Peacememories
>
> Thanks for reporting the bug!
>
> Ludo’.
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-04-29 23:36 bug#70659: Too many heap sections on guix pull Peacememories
2024-04-30 9:11 ` Ludovic Courtès
2024-04-30 15:34 ` Peacememories [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=6458e7390af2b1f97ced47e0a885e470@posteo.net \
--to=peacememories@posteo.net \
--cc=70659@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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).