all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Jack Hill <jackhill@jackhill.us>
Cc: 55596@debbugs.gnu.org
Subject: bug#55596: subversion segfaul on `guix import texlive`
Date: Mon, 23 May 2022 20:40:55 +0200	[thread overview]
Message-ID: <87v8tw2ip2@nckx> (raw)
In-Reply-To: <alpine.DEB.2.21.2205231427160.11587@marsh.hcoop.net>

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

Jack Hill 写道:
> """
> $ guix import texlive qrcode
> command "svn" "export" "--non-interactive" "--trust-server-cert" 
> "-r"
> "59745"
> "svn://www.tug.org/texlive/tags/texlive-2021.3/Master/texmf-dist/doc/latex/qrcode/"
> "/tmp/guix-directory.6aY7Gk/doc/latex/qrcode/" failed with 
> signal 11
> guix import: error: failed to import package 'qrcode'
> """
>
> It seems something is unwell with our subversion package?

I don't know why I didn't think of this sooner, but I ran that svn 
command by hand (only replacing the output directory, say 
/tmp/foo) and… it ran fine.

So I checked my dmesg and it's actually Guix that's getting 
killed:

[146565.315921] guix[1767]: segfault at c0 ip 000076c46ae99e70 sp 
00007fffcbe9cb30 error 4 cpu 5 in 
libc-2.33.so[76c46ae57000+141000]
[146565.315937] Code: 56 41 55 41 54 55 48 89 fd 53 48 81 ec f8 04 
00 00 48 8b 05 ea 1f 15 00 48 89 34 24 89 4c 24 48 64 8b 00 89 84 
24 80 00 00 00 <8b> 87 c0 00 00 00 85 c0 0f 85 4a 02 00 00 c7 87 
c0 00 00 00 ff ff

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2022-05-23 18:44 UTC|newest]

Thread overview: 3+ 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 [this message]
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=87v8tw2ip2@nckx \
    --to=bug-guix@gnu.org \
    --cc=55596@debbugs.gnu.org \
    --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.