From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 55596@debbugs.gnu.org, jackhill@jackhill.us,
55587@debbugs.gnu.org, hugonobrega@ic.ufrj.br
Subject: bug#55596: Guix/Guile segfaults on `guix import texlive`
Date: Wed, 15 Jun 2022 22:39:21 +0200 [thread overview]
Message-ID: <87sfo5psp2.fsf_-_@gnu.org> (raw)
In-Reply-To: <87y1ylwkm8@nckx> (Tobias Geerinckx-Rice's message of "Sat, 28 May 2022 20:51:53 +0200")
Hello,
Tobias Geerinckx-Rice <me@tobias.gr> skribis:
> I think you might be barking up the wrong tree (or, likely, that there
> are multiple trees here). I could reproduce the segfault on Guix
> System and encouraged Jack to file this bug.
>
> It's not foreign-distro-related. The process actually segfaulting is
> Guix, not svn, possibly due to a missing svn.
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.
Should we close and reopen if/when we have more info?
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-06-15 20:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
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-05-29 10:19 ` Hugo
2022-06-15 20:39 ` Ludovic Courtès [this message]
2022-08-05 12:22 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2022-05-23 18:29 bug#55596: subversion segfaul " Jack Hill
2022-07-14 4:24 ` bug#55596: Guix/Guile segfaults " Akira Kyle
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfo5psp2.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=55587@debbugs.gnu.org \
--cc=55596@debbugs.gnu.org \
--cc=hugonobrega@ic.ufrj.br \
--cc=jackhill@jackhill.us \
--cc=me@tobias.gr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.