unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Jack Hill <jackhill@jackhill.us>
Cc: 55596@debbugs.gnu.org, 55587@debbugs.gnu.org,
	Hugo <hugonobrega@ic.ufrj.br>
Subject: bug#55587: bug#55596: Guix/Guile segfaults on `guix import texlive`
Date: Sat, 28 May 2022 19:19:21 +0200	[thread overview]
Message-ID: <875ylpbmna.fsf_-_@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2205260933340.11587@marsh.hcoop.net> (Jack Hill's message of "Thu, 26 May 2022 09:36:28 -0400 (EDT)")

Hi,

Jack Hill <jackhill@jackhill.us> skribis:

> On Wed, 25 May 2022, Hugo wrote:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> Jack, Hugo: What does “type -P svn” say?
>>>
>>> Does the bug occur within ‘guix shell subversion’ as shown above?
>>
>> Well, I feel kind of silly now, after actually installing subversion the
>> command works as expected :)
>
> Same for me, and I feel equally silly :)

You mentioned an error report from Guix:

  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

To me that means that an “svn” command was indeed found in $PATH but
that it segfaulted.

What did “type -P svn” return?  Perhaps there was an “svn” command
coming from the host distro, like /usr/bin/svn?

Or am I missing something?

Thanks,
Ludo’.




  reply	other threads:[~2022-05-28 17:20 UTC|newest]

Thread overview: 9+ 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 [this message]
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
2022-08-05 12:22             ` bug#55587: " 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=875ylpbmna.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 \
    /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).