unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Akira Kyle <akira@akirakyle.com>
To: 55596@debbugs.gnu.org
Subject: bug#55596: Guix/Guile segfaults on `guix import texlive`
Date: Wed, 13 Jul 2022 22:24:39 -0600	[thread overview]
Message-ID: <86y1wwmid4.fsf@akirakyle.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2205231427160.11587@marsh.hcoop.net>

Hi,

> I don’t think so; the error message that was reported is:
> 
>   command "svn" "export" "--non-interactive" "--trust-server-cert" "-r" "59745" "svn://www.tug.org/texlive/tags/texlive-2021.3/Master/texmf-dist/doc/latex/cite/" "/tmp/guix-directory.09UnsN/doc/latex/cite/" failed with signal 11
> 
> It’s a message from ‘report-invoke-error’ in (guix build utils).  It’s
> really svn that’s segfaulting.

I recently encountered this issue and did some digging. I don't think svn is actually segfaulting, just that the command svn doesn't exist so when 'system*' is called inside 'invoke' in (guix build utils) it for some reason gives signal 11.

On a recent guix system, I can reproduce this error by running 'guix import texlive' when inside 'guix shell guix --pure'. However there is no error when inside 'guix shell guix subversion --pure'. I think this is ultimately due to 'download-multi-svn-to-store' (and 'download-svn-to-store' but the texlive importer only calls the former) not setting '#:svn-command' when it calls 'build:svn-fetch' so it uses the default argument of 'svn' rather than trying to explicitly use an svn from the store.

Unfortunately my guile and gexp knowledge is quite lacking so I'm not sure that I have the know-how to create a patch to fix this, however hopefully this is enough for someone else to easily fix this issue.

Thanks,
Akira





  parent reply	other threads:[~2022-07-14  4:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 18:29 bug#55596: subversion segfaul on `guix import texlive` Jack Hill
2022-05-23 18:40 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-07-14  4:24 ` Akira Kyle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-22 20:26 bug#55587: `guix import texlive PKG` fails with signal 11, no output Hugo Nobrega
2022-05-25 10:36 ` bug#55596: Guix/Guile segfaults on `guix import texlive` Ludovic Courtès
2022-05-26  0:20   ` Hugo
2022-05-26 13:36     ` bug#55596: bug#55587: " Jack Hill
2022-05-28 17:19       ` Ludovic Courtès
2022-05-28 18:51         ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-06-15 20:39           ` Ludovic Courtès

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=86y1wwmid4.fsf@akirakyle.com \
    --to=akira@akirakyle.com \
    --cc=55596@debbugs.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).