From: "Hans Åberg" <haberg-1@telia.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Warnings `_IOFBF' is deprecated. Use the symbol 'block instead.
Date: Fri, 13 Jul 2018 17:51:36 +0200 [thread overview]
Message-ID: <19F08B9A-62D9-43F7-8CEC-D560B0122B47@telia.com> (raw)
In-Reply-To: <87in5jfb5k.fsf@gnu.org>
> On 13 Jul 2018, at 16:44, Ludovic Courtès <ludo@gnu.org> wrote:
>
> Hans Åberg <haberg-1@telia.com> skribis:
>
>>> On 13 Jul 2018, at 10:13, Ludovic Courtès <ludo@gnu.org> wrote:
>>>
>>> The plan is for Guix to require Guile >= 2.2 sometime soon though,
>>> so at that point we can move to the new APIs.
>>
>> A bug that may or may not be carried over to Guix: I could not install
>> Nix on MacOS 10.13, and I think it may be due to the sudo timeout set
>> to zero, causing non-terminating confirmations. So the script may do
>> more root calls than explicitly asked for, a potential security
>> loophole.
>
> We’ve changed topics, right? :-)
Right. :-)
> I don’t know what Nix is doing. Guix works only on systems running the
> kernel Linux or the GNU Hurd, anyway.
It is only a problem if you have an installer for whatever system. The suggestion is to test the installation with sudo timeout set to 0.
prev parent reply other threads:[~2018-07-13 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-08 10:46 Warnings `_IOFBF' is deprecated. Use the symbol 'block instead Roel Janssen
2018-07-12 9:27 ` Ludovic Courtès
2018-07-12 20:41 ` Roel Janssen
2018-07-13 8:13 ` Ludovic Courtès
2018-07-13 12:45 ` Hans Åberg
2018-07-13 14:44 ` Ludovic Courtès
2018-07-13 15:51 ` Hans Åberg [this message]
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19F08B9A-62D9-43F7-8CEC-D560B0122B47@telia.com \
--to=haberg-1@telia.com \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.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.
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).