unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: swedebugia <swedebugia@riseup.net>
Cc: 34006@debbugs.gnu.org
Subject: bug#34006: Guix gc killed live roots - broke git
Date: Mon, 07 Jan 2019 18:52:32 +0100	[thread overview]
Message-ID: <87imz08ie7.fsf@elephly.net> (raw)
In-Reply-To: <276035e4-7b63-31b7-9b83-e4311441dbe5@riseup.net>


swedebugia <swedebugia@riseup.net> writes:

> On 2019-01-07 12:31, Ricardo Wurmus wrote:
>>
>> Hi swedebugia,
>>
>>> $ git pull swedebugia
>>> fatal: unable to fork
>>>
>>> Stracing it reveals that it is missing something (see full attached):
>>
>> Where do you see that?
>
> Ah, sorry the full command was:
> strace git pull swedebugia

What I meant is that the excerpt you showed does not reveal that
“missing something” is the cause of the error.  Having a bunch of things
not found is pretty normal given that search paths are used.

> I tried installing git again with guix package -i git, but it seems no
> substitutes are available anymore to my surprise (0.16 is not even 2
> months old).

Substitutes from berlin / ci.guix.info?

-- 
Ricardo

  reply	other threads:[~2019-01-09  5:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 10:07 bug#34006: Guix gc killed live roots - broke git swedebugia
2019-01-07 11:31 ` Ricardo Wurmus
2019-01-07 16:58   ` swedebugia
2019-01-07 17:52     ` Ricardo Wurmus [this message]
2019-01-08  7:50     ` Mark H Weaver
2019-01-08  8:50       ` swedebugia
2019-01-12 19:02       ` swedebugia

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=87imz08ie7.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=34006@debbugs.gnu.org \
    --cc=swedebugia@riseup.net \
    /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).