all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: Mark H Weaver <mhw@netris.org>
Cc: "34006@debbugs.gnu.org" <34006@debbugs.gnu.org>
Subject: bug#34006: Guix gc killed live roots - broke git
Date: Tue, 08 Jan 2019 09:50:19 +0100	[thread overview]
Message-ID: <511E32D6-D335-4BD5-AF4F-8247C6106864@pretty.Easy.privacy> (raw)
In-Reply-To: <b41d4d9f15f13476ff73dff0cee9a0f9@riseup.net> <87muocr9ej.fsf@elephly.net> <276035e4-7b63-31b7-9b83-e4311441dbe5@riseup.net>; <87k1jfk2o7.fsf@netris.org>;


[-- Attachment #1.1: Type: text/html, Size: 2407 bytes --]

[-- Attachment #1.2: Type: text/plain, Size: 1722 bytes --]

Mark H Weaver <mhw@netris.org> skrev: (8 januari 2019 08:50:53 CET)
>Hi,
>
>swedebugia <swedebugia@riseup.net> writes:
>
>> On 2019-01-07 12:31, Ricardo Wurmus wrote:
>>>
>>>> $ 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
>
>I looked at the strace output you provided, and didn't find any
>evidence
>of a missing file, which I doubt would lead to the error message
>"unable
>to fork" anyway.  The short excerpt that you quoted in your earlier
>mail
>showed the failure to find "/etc/ld.so.preload", but that's expected,
>and does not indicate a problem.  The problem might be happening in the
>child process (/home/sdb/.guix-profile/libexec/git-core/git), so adding
>the -f option to strace, i.e. "strace -f git pull swedebugia", might
>yield more useful information.
>
>If I'm not mistaken, "unable to fork" more likely indicates a lack of
>available resources, possibly due to configured resource limits (see
>ulimit(3) and the 'ulimit' bash builtin, e.g. try "ulimit -a").
>Otherwise, I guess it could be due to restrictions imposed by the use
>of
>a security framework.
>
>       Mark

Thanks for the -f tip. I thought the errors were significant, but now I understood they are not.
I will reply to the thread with more information if upgrading does not solve it. 
It is a vanilla 0.16 with a few packages installed, no security framework. 
I will share the whole environment also.
Git has been upgraded so I will try installing the newer version next.
-- 
Sent from my p≡p for Android.

[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 3825 bytes --]

  reply	other threads:[~2019-01-08  8:51 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
2019-01-08  7:50     ` Mark H Weaver
2019-01-08  8:50       ` swedebugia [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=511E32D6-D335-4BD5-AF4F-8247C6106864@pretty.Easy.privacy \
    --to=swedebugia@riseup.net \
    --cc=34006@debbugs.gnu.org \
    --cc=mhw@netris.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 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.