From debbugs-submit-bounces@debbugs.gnu.org Tue May 30 16:31:34 2017 Received: (at submit) by debbugs.gnu.org; 30 May 2017 20:31:35 +0000 Received: from localhost ([127.0.0.1]:45723 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dFnni-0004lV-Mw for submit@debbugs.gnu.org; Tue, 30 May 2017 16:31:34 -0400 Received: from eggs.gnu.org ([208.118.235.92]:56705) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dFnnh-0004lJ-Pp for submit@debbugs.gnu.org; Tue, 30 May 2017 16:31:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dFnnb-00058Q-Q2 for submit@debbugs.gnu.org; Tue, 30 May 2017 16:31:28 -0400 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50 autolearn=disabled version=3.3.2 Received: from lists.gnu.org ([2001:4830:134:3::11]:46213) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dFnnb-00058M-N1 for submit@debbugs.gnu.org; Tue, 30 May 2017 16:31:27 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47670) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dFnna-0005mP-HX for bug-guix@gnu.org; Tue, 30 May 2017 16:31:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dFnnX-00057L-D6 for bug-guix@gnu.org; Tue, 30 May 2017 16:31:26 -0400 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21081) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dFnnX-000571-4v for bug-guix@gnu.org; Tue, 30 May 2017 16:31:23 -0400 Received: from localhost (port-92-200-122-160.dynamic.qsc.de [92.200.122.160]) by mx.zohomail.com with SMTPS id 1496176278492781.1333973983982; Tue, 30 May 2017 13:31:18 -0700 (PDT) User-agent: mu4e 0.9.18; emacs 25.2.1 From: Ricardo Wurmus To: bug-guix@gnu.org Subject: deprecation warnings with Guile 2.2.2 X-URL: https://elephly.net X-PGP-Key: https://elephly.net/rekado.pubkey X-PGP-Fingerprint: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC Date: Tue, 30 May 2017 22:31:15 +0200 Message-ID: <87wp8y2ijw.fsf@elephly.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-ZohoMailClient: External X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 2001:4830:134:3::11 X-Spam-Score: -4.0 (----) X-Debbugs-Envelope-To: submit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -4.0 (----) I get a couple of deprecation warnings with Guile 2.2.2, for example Import (ice-9 threads) to have access to `current-processor-count'. `_IOFBF' is deprecated. Use the symbol 'block instead. I only see them after “export GUILE_WARN_DEPRECATED=detailed”. Without that variable I get a block of text that informs me that deprecated features have been used. This happens especially when running “make” or when not all files have been compiled. -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net From debbugs-submit-bounces@debbugs.gnu.org Wed May 31 17:00:43 2017 Received: (at 27152) by debbugs.gnu.org; 31 May 2017 21:00:43 +0000 Received: from localhost ([127.0.0.1]:47958 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dGAjO-0000Nf-FQ for submit@debbugs.gnu.org; Wed, 31 May 2017 17:00:43 -0400 Received: from eggs.gnu.org ([208.118.235.92]:35405) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dGAjH-0000NM-UR for 27152@debbugs.gnu.org; Wed, 31 May 2017 17:00:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dGAj8-0005pR-My for 27152@debbugs.gnu.org; Wed, 31 May 2017 17:00:26 -0400 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=-0.5 required=5.0 tests=BAYES_05,RP_MATCHES_RCVD autolearn=disabled version=3.3.2 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:44962) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dGAj8-0005pM-Je; Wed, 31 May 2017 17:00:22 -0400 Received: from reverse-83.fdn.fr ([80.67.176.83]:53160 helo=ribbon) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dGAj7-0006lp-Rs; Wed, 31 May 2017 17:00:22 -0400 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) To: Ricardo Wurmus Subject: Re: bug#27152: deprecation warnings with Guile 2.2.2 References: <87wp8y2ijw.fsf@elephly.net> X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 12 Prairial an 225 de la =?utf-8?Q?R=C3=A9volution?= X-PGP-Key-ID: 0x090B11993D9AEBB5 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 3CE4 6455 8A84 FDC6 9DB4 0CFB 090B 1199 3D9A EBB5 X-OS: x86_64-unknown-linux-gnu Date: Wed, 31 May 2017 23:00:19 +0200 In-Reply-To: <87wp8y2ijw.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 30 May 2017 22:31:15 +0200") Message-ID: <87h90091y4.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-Spam-Score: -5.0 (-----) X-Debbugs-Envelope-To: 27152 Cc: 27152@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -5.0 (-----) Hi, Ricardo Wurmus skribis: > I get a couple of deprecation warnings with Guile 2.2.2, for example > > Import (ice-9 threads) to have access to `current-processor-count'. > `_IOFBF' is deprecated. Use the symbol 'block instead. We can fix the first one with #:use-module (ice-9 threads). The second one is just a pain: in 2.2 one is supposed to write (setvbuf port 'block) instead of (setvbuf port _IOFBF) So we could do: (cond-expand (guile-2.2 (define _IOFBF 'block)) (else #t)) in some central place (that doesn=E2=80=99t exist), but really, that=E2=80= =99s annoying. So I=E2=80=99m tempted to do nothing. Note that normally users do not see these deprecation warnings at all. Thoughts? Ludo=E2=80=99. From debbugs-submit-bounces@debbugs.gnu.org Fri Jun 02 20:40:08 2017 Received: (at 27152) by debbugs.gnu.org; 3 Jun 2017 00:40:08 +0000 Received: from localhost ([127.0.0.1]:52175 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dGx6u-0007DJ-1T for submit@debbugs.gnu.org; Fri, 02 Jun 2017 20:40:08 -0400 Received: from mail-yb0-f177.google.com ([209.85.213.177]:35761) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dGx6s-0007Ck-2B for 27152@debbugs.gnu.org; Fri, 02 Jun 2017 20:40:06 -0400 Received: by mail-yb0-f177.google.com with SMTP id r66so21971401yba.2 for <27152@debbugs.gnu.org>; Fri, 02 Jun 2017 17:40:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=k+3fTL0Oi/7Ne47lyXdzgMyMajY+Vc9rAxz6XFBaqfE=; b=AqF4xC/xll98sd96JlsJNnQlPvfliwKEEFRuSAkB4ON3dHhOpPrDm/tj78QObZlI56 44jWSUYI4I0EWSPO5llPcQFNQs1riIItCrsKLn2YebFKzF0wPFjsSeS8GFFAmgwIsw2g xJK1pU9kzEpSFEjZKxm5A+bi15pLcEigqPUOcx8JzLuq2GAFN+xNBAK5XHoIXXAJ30x9 TvSHcaKQmi5sPii95FI8DJi12UIXPY4hQcVC648N9QtFC0/NBd3Co/GNXTnOJVdRNDik 8me6r8I808WzmJObAYxYz1J5CPk5QPWGw3Bya3xQXQJVkNNSoQ77nCfHZVXR8ybayHc9 lHSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=k+3fTL0Oi/7Ne47lyXdzgMyMajY+Vc9rAxz6XFBaqfE=; b=qex6EvCDUYJ1CVnEgIrgdb6ciU59yED3yFVBBJQvkZcrN5aTEAUnIeubQzjvI6LsOr tekY+XgZs00ehJJ5YaqNcBf6uEigJRg4AdwAWn4LBaVoHWN3zUX177gBHk5HaMghIS93 mHJWag3xSdw/V6tETh9Oxik0tunq8csNE9ZNlJVGGauMgT901TDzQqFl6R/F/Krq7AKk Z8ckqJfiE/w18nOneCGBtNL6jZTOL4uSUD7mW7B5Pwfs8JUhoPocg/PzLzOwjDMfsItI NV3Tz+zniLMwUxVYja8Z9aWOPNI7apln/kdntk2nlMhjlSt5JJXkFEJX2BJhh55BuRdX zQaQ== X-Gm-Message-State: AODbwcBgwD1Vnqmk70Kx0JzhcuAUzY3aRefmTwDlyxVNRXDqG+ioohwM V8qxvBpHhszzuTWqJhQB6cCrgAdwqg== X-Received: by 10.37.173.81 with SMTP id l17mr2118246ybe.256.1496450400171; Fri, 02 Jun 2017 17:40:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.129.179.202 with HTTP; Fri, 2 Jun 2017 17:39:59 -0700 (PDT) In-Reply-To: <87h90091y4.fsf@gnu.org> References: <87wp8y2ijw.fsf@elephly.net> <87h90091y4.fsf@gnu.org> From: Maxim Cournoyer Date: Fri, 2 Jun 2017 17:39:59 -0700 Message-ID: Subject: Re: bug#27152: deprecation warnings with Guile 2.2.2 To: =?UTF-8?Q?Ludovic_Court=C3=A8s?= Content-Type: multipart/alternative; boundary="f403045ebf1086df940551038287" X-Spam-Score: 0.5 (/) X-Debbugs-Envelope-To: 27152 Cc: Ricardo Wurmus , 27152@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.5 (/) --f403045ebf1086df940551038287 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, May 31, 2017 at 2:00 PM, Ludovic Court=C3=A8s wrote: > Hi, > > Ricardo Wurmus skribis: > > > I get a couple of deprecation warnings with Guile 2.2.2, for example > > > > Import (ice-9 threads) to have access to `current-processor-count'. > > `_IOFBF' is deprecated. Use the symbol 'block instead. > > We can fix the first one with #:use-module (ice-9 threads). > > The second one is just a pain: in 2.2 one is supposed to write > > (setvbuf port 'block) > > instead of > > (setvbuf port _IOFBF) > > So we could do: > > (cond-expand (guile-2.2 (define _IOFBF 'block)) > (else #t)) > in some central place (that doesn=E2=80=99t exist), but really, that=E2=80= =99s annoying. > > So I=E2=80=99m tempted to do nothing. > > Note that normally users do not see these deprecation warnings at all. > > Thoughts? > Why not let good old sed have a run at it? Seems like a simple find and replace operation, and 'block looks nicer than _IOFBF to my eyes. Maxim --f403045ebf1086df940551038287 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On W= ed, May 31, 2017 at 2:00 PM, Ludovic Court=C3=A8s <ludo@gnu.org> = wrote:
Hi,

Ricardo Wurmus <rekado@elephly.net= > skribis:

> I get a couple of deprecation warnings with Guile 2.2.2, for example >
>=C2=A0 =C2=A0 =C2=A0Import (ice-9 threads) to have access to `current-p= rocessor-count'.
>=C2=A0 =C2=A0 =C2=A0`_IOFBF' is deprecated.=C2=A0 Use the symbol &#= 39;block instead.

We can fix the first one with #:use-module (ice-9 threads).

The second one is just a pain: in 2.2 one is supposed to write

=C2=A0 (setvbuf port 'block)

instead of

=C2=A0 (setvbuf port _IOFBF)

So we could do:

=C2=A0 (cond-expand (guile-2.2 (define _IOFBF 'block))
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(else #t))
=C2=A0
in some central place (that doesn=E2=80=99t exist), but really, that=E2=80= =99s annoying.

So I=E2=80=99m tempted to do nothing.

Note that normally users do not see these deprecation warnings at all.

Thoughts?
=C2=A0
Why not let good old sed ha= ve a run at it? Seems like a simple find and replace operation, and 'bl= ock looks nicer than _IOFBF to my eyes.
=C2=A0
Maxim
<= /div>
--f403045ebf1086df940551038287-- From debbugs-submit-bounces@debbugs.gnu.org Fri Jun 02 21:20:23 2017 Received: (at 27152) by debbugs.gnu.org; 3 Jun 2017 01:20:24 +0000 Received: from localhost ([127.0.0.1]:52218 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dGxjr-0001VO-NQ for submit@debbugs.gnu.org; Fri, 02 Jun 2017 21:20:23 -0400 Received: from world.peace.net ([50.252.239.5]:38840) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dGxjq-0001VB-LU for 27152@debbugs.gnu.org; Fri, 02 Jun 2017 21:20:22 -0400 Received: from pool-72-93-32-114.bstnma.east.verizon.net ([72.93.32.114] helo=jojen) by world.peace.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dGxjk-0000n3-PV; Fri, 02 Jun 2017 21:20:16 -0400 From: Mark H Weaver To: Maxim Cournoyer Subject: Re: bug#27152: deprecation warnings with Guile 2.2.2 References: <87wp8y2ijw.fsf@elephly.net> <87h90091y4.fsf@gnu.org> Date: Fri, 02 Jun 2017 21:20:03 -0400 In-Reply-To: (Maxim Cournoyer's message of "Fri, 2 Jun 2017 17:39:59 -0700") Message-ID: <871sr1yiik.fsf@netris.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 27152 Cc: Ludovic =?utf-8?Q?Court=C3=A8s?= , 27152@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.0 (/) Maxim Cournoyer writes: > On Wed, May 31, 2017 at 2:00 PM, Ludovic Court=C3=A8s wrot= e: > > Ricardo Wurmus skribis: > > > I get a couple of deprecation warnings with Guile 2.2.2, for example > > > > Import (ice-9 threads) to have access to `current-processor-count'. > > `_IOFBF' is deprecated. Use the symbol 'block instead. > > We can fix the first one with #:use-module (ice-9 threads). > > The second one is just a pain: in 2.2 one is supposed to write > > (setvbuf port 'block) > > instead of > > (setvbuf port _IOFBF) > > So we could do: > > (cond-expand (guile-2.2 (define _IOFBF 'block)) > (else #t)) > > in some central place (that doesn=E2=80=99t exist), but really, that=E2= =80=99s annoying. > > So I=E2=80=99m tempted to do nothing. > > Note that normally users do not see these deprecation warnings at all. > > Thoughts? > > Why not let good old sed have a run at it? Seems like a simple find and r= eplace operation, and 'block looks nicer than _IOFBF to my eyes. If we did that, then Guix would stop working with guile-2.0. Given that guile-2.2 is not yet available from many popular distros, I think it would be unwise to drop guile-2.0 at this time. Mark From debbugs-submit-bounces@debbugs.gnu.org Sat Jun 03 00:43:17 2017 Received: (at 27152) by debbugs.gnu.org; 3 Jun 2017 04:43:17 +0000 Received: from localhost ([127.0.0.1]:52283 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dH0uD-0007v1-Gp for submit@debbugs.gnu.org; Sat, 03 Jun 2017 00:43:17 -0400 Received: from mail-pf0-f182.google.com ([209.85.192.182]:36241) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dH0uB-0007uo-2p for 27152@debbugs.gnu.org; Sat, 03 Jun 2017 00:43:15 -0400 Received: by mail-pf0-f182.google.com with SMTP id m17so60182906pfg.3 for <27152@debbugs.gnu.org>; Fri, 02 Jun 2017 21:43:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-transfer-encoding; bh=nU9hS1i/rozdSW9bp0iBNcYyIyIrwRaknTdeR4cABn4=; b=jtD6tjS8qX09H97NifaVn2XzpZ12puoNVfhDf9DJAKKcNlXX1d9oZ4gTrhOn8ZLwns uU7FpiF9bV1KDexhMYn1oMqAPryly1PBm0HjqxQ4qQ+VeHnznyMZ58/WspXQaexgpqt6 FDuuTFmSdVjZIztqpZz0dE6rpWsNvpNkYSC6G+Izwere9YQ6zhWg9D30SvPCaZj95drT EUqCRh8hm/fY09woufk2UGb2AfDWJSojF4LayuaWpuEpcKR7qgQ15EfCzFnjHtcpIUYw O0N1k4eJDIWk8YDRPFPbLGu/+yAS3cHrByt/E/Ncd/WVvX6m2qLcLKC4Hs/bXSNDTA6x 5Csw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=nU9hS1i/rozdSW9bp0iBNcYyIyIrwRaknTdeR4cABn4=; b=GagKe86VnU6lduYQfzxZhq61pX0sNnDa2IGqBRvQIhu+E8D1J9SewfZ8sFSU9+I6uz FUMa176nhVcVVjeyyPDEG+2YMxdzXHrcx5qfeMLe6DWCceSD871FCLrC3VS9IykJ9CCn sT18LFkBTdA2dY1IReg66HTrWPuFmy9ch0UkkdLO4yiuIbqti5En5oxUlk0yOJlyd3Rf q7wLy1GVV4NO5C2ojixFJVvV4kWTVUQ7sIoyBz5i4W/IsxHTMvIDy1n2xLAEep0jk328 1eEMqQU5r/UfO4ke/3FZjt9j+pmaXSfXuKqaVq86GaIGslyDNvKDMsPl20xmy1YlfnXD YOZw== X-Gm-Message-State: AODbwcBB2vT4gQO7YTuC7IxqNRXxpFbB8gm/awUe2mrWUE7e5m6nJgx7 eIzD0oYIaomGo8pNfsw= X-Received: by 10.84.218.78 with SMTP id f14mr3360714plm.214.1496464987663; Fri, 02 Jun 2017 21:43:07 -0700 (PDT) Received: from apteryx ([2601:647:4a01:bacd:c2f8:daff:fe5d:2f2f]) by smtp.gmail.com with ESMTPSA id i67sm44807909pfk.87.2017.06.02.21.43.06 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 02 Jun 2017 21:43:07 -0700 (PDT) From: Maxim Cournoyer To: Mark H Weaver Subject: Re: bug#27152: deprecation warnings with Guile 2.2.2 References: <87wp8y2ijw.fsf@elephly.net> <87h90091y4.fsf@gnu.org> <871sr1yiik.fsf@netris.org> Date: Fri, 02 Jun 2017 21:43:05 -0700 In-Reply-To: <871sr1yiik.fsf@netris.org> (Mark H. Weaver's message of "Fri, 02 Jun 2017 21:20:03 -0400") Message-ID: <87h8zxr89y.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 27152 Cc: Ludovic =?utf-8?Q?Court=C3=A8s?= , 27152@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.3 (--) Hi Mark, Mark H Weaver writes: > Maxim Cournoyer writes: > >> On Wed, May 31, 2017 at 2:00 PM, Ludovic Court=C3=A8s wro= te: >> >> Ricardo Wurmus skribis: >> >> > I get a couple of deprecation warnings with Guile 2.2.2, for example >> > >> > Import (ice-9 threads) to have access to `current-processor-count'. >> > `_IOFBF' is deprecated. Use the symbol 'block instead. >> >> We can fix the first one with #:use-module (ice-9 threads). >> >> The second one is just a pain: in 2.2 one is supposed to write >> >> (setvbuf port 'block) >> >> instead of >> >> (setvbuf port _IOFBF) >> >> So we could do: >> >> (cond-expand (guile-2.2 (define _IOFBF 'block)) >> (else #t)) >> >> in some central place (that doesn=E2=80=99t exist), but really, that=E2= =80=99s annoying. >> >> So I=E2=80=99m tempted to do nothing. >> >> Note that normally users do not see these deprecation warnings at all. >> >> Thoughts? >> >> Why not let good old sed have a run at it? Seems like a simple find and = replace operation, and 'block looks nicer than _IOFBF to my eyes. > > If we did that, then Guix would stop working with guile-2.0. Given that > guile-2.2 is not yet available from many popular distros, I think it > would be unwise to drop guile-2.0 at this time. Isn't Guile included in the Guix binary releases? I would have thought so. Otherwise, I just tried "guix pack guile@2.2" and the resulting archive is 40 MiB. I'm not saying it's worth it, but it's an option. Maxim From debbugs-submit-bounces@debbugs.gnu.org Sun Jun 04 01:18:37 2017 Received: (at 27152) by debbugs.gnu.org; 4 Jun 2017 05:18:37 +0000 Received: from localhost ([127.0.0.1]:54497 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dHNvw-0007eu-Vt for submit@debbugs.gnu.org; Sun, 04 Jun 2017 01:18:37 -0400 Received: from world.peace.net ([50.252.239.5]:40861) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dHNvu-0007ee-G7 for 27152@debbugs.gnu.org; Sun, 04 Jun 2017 01:18:35 -0400 Received: from pool-72-93-32-114.bstnma.east.verizon.net ([72.93.32.114] helo=jojen) by world.peace.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dHNvo-0007tZ-6t; Sun, 04 Jun 2017 01:18:28 -0400 From: Mark H Weaver To: Maxim Cournoyer Subject: Re: bug#27152: deprecation warnings with Guile 2.2.2 References: <87wp8y2ijw.fsf@elephly.net> <87h90091y4.fsf@gnu.org> <871sr1yiik.fsf@netris.org> <87h8zxr89y.fsf@gmail.com> Date: Sun, 04 Jun 2017 01:18:11 -0400 In-Reply-To: <87h8zxr89y.fsf@gmail.com> (Maxim Cournoyer's message of "Fri, 02 Jun 2017 21:43:05 -0700") Message-ID: <871sr0wcto.fsf@netris.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 27152 Cc: Ludovic =?utf-8?Q?Court=C3=A8s?= , 27152@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.0 (/) Maxim Cournoyer writes: > Mark H Weaver writes: > >> Maxim Cournoyer writes: >> >>> Why not let good old sed have a run at it? Seems like a simple find >>> and replace operation, and 'block looks nicer than _IOFBF to my >>> eyes. >> >> If we did that, then Guix would stop working with guile-2.0. Given that >> guile-2.2 is not yet available from many popular distros, I think it >> would be unwise to drop guile-2.0 at this time. > > Isn't Guile included in the Guix binary releases? Yes, but that's not the only supported method to install Guix. While I acknowledge that most new users are happy to use our binary tarball, many users prefer to compile our source tarball, or to try out a Guix package provided by their existing distribution. Security conscious users tend to be nervous about entrusting their computer's security to a source of precompiled binaries that is new to them. While it's true that they will need our bootstrap binaries, and that they are highly likely to end up using our binary substitutes before long, it nonetheless seems to me that it is best not to ask newcomers to trust a large binary from us as their first step into our community, without providing other easy methods that are more comfortable to them. Users are comfortable installing a package from a distro that they've already put their trust in. So, I would prefer to continue supporting guile-2.0 until guile-2.2 is more widely deployed in popular distros, or at least until it becomes a hassle to continue supporting guile-2.0. I'll also mention that there's apparently an unresolved bug somewhere (guile2.2-ssh?) that prevents us from using guix-based-on-guile-2.2 on hydra.gnu.org: https://bugs.gnu.org/26976 Mark From debbugs-submit-bounces@debbugs.gnu.org Sun Jun 04 01:51:34 2017 Received: (at 27152) by debbugs.gnu.org; 4 Jun 2017 05:51:34 +0000 Received: from localhost ([127.0.0.1]:54514 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dHORq-0000Fd-2c for submit@debbugs.gnu.org; Sun, 04 Jun 2017 01:51:34 -0400 Received: from mail-pf0-f179.google.com ([209.85.192.179]:36826) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dHORo-0000FR-ET for 27152@debbugs.gnu.org; Sun, 04 Jun 2017 01:51:33 -0400 Received: by mail-pf0-f179.google.com with SMTP id m17so68989024pfg.3 for <27152@debbugs.gnu.org>; Sat, 03 Jun 2017 22:51:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=6u378RQwJylKFp3FHRjSv5W1DxI1x+ICUdVRXr+CieU=; b=tcn2tJIbWorITevrFWthSO8d/Ja1t4EKTtTrPErXLS4gg4R4ufa66hIutlQ46Mu3XK OtFfTtTSDNAH93/VxPPmoY+PjVMeCuxX/pc6OKSs+QLFjTc5bnxSomw78ZTQTUWVL7qA FymMFcRhEqYEUYmvYgHDiLmwtSngwV0UV7fqEbEDe55D03m5PjeXUR/++eEEjtuuL75j PbFPtwTADPFmbr+jzTPvprUqKAYt0MBjsaJO3vAB0SqrDC5ziUIgh60tNSG5kE94iV4k Ba0Tc7rn7eWiuklU6MKNOOMv24Z8TlF2xspRYcJQccxJpR/Ut58Oo98IHtycYRoQ/JoG 86DQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=6u378RQwJylKFp3FHRjSv5W1DxI1x+ICUdVRXr+CieU=; b=N5OdZesl+XiUzWv2JO/GcAuiLRXPHpDcXcEvxvD5SiA24jpSN9/IRreNRUfdqr3gMl gx19bIztXhEJY3Ou0CW99XaZS4kpVJ9t5gSjNYUmZLK3AgZBhm/9jYF5S8PGjEQMYt1k Dz+xBHV5c3Y7GgkTmEsM/FTz2qaAL1zyc0oKTHyFCyGrjiGsbUs5sTgZEtTa9c9sXnW8 g0Qi/pf91b5LTWjwylyze85YeIy/wC38Xsq47SN0HXkc4sM0LFUgT43ibpHVoELYvS+/ wtJNz/YtQ4L9rmNykx5x5rgqqKgrddGrgoeXQgVH0Bk4PtBewUWZipH0fRld6VjxSQBa 8idw== X-Gm-Message-State: AODbwcAYS27/E0oZd8u0j9VhFeyMus2XHEbiDaLQFA6gBTJ+xmxChC4w z6Ee+U+o1l5UyH7DNOY= X-Received: by 10.99.109.73 with SMTP id i70mr15168719pgc.62.1496555486024; Sat, 03 Jun 2017 22:51:26 -0700 (PDT) Received: from apteryx ([2601:647:4a01:bacd:c2f8:daff:fe5d:2f2f]) by smtp.gmail.com with ESMTPSA id w76sm39938790pfd.76.2017.06.03.22.51.25 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 03 Jun 2017 22:51:25 -0700 (PDT) From: Maxim Cournoyer To: Mark H Weaver Subject: Re: bug#27152: deprecation warnings with Guile 2.2.2 References: <87wp8y2ijw.fsf@elephly.net> <87h90091y4.fsf@gnu.org> <871sr1yiik.fsf@netris.org> <87h8zxr89y.fsf@gmail.com> <871sr0wcto.fsf@netris.org> Date: Sat, 03 Jun 2017 22:51:24 -0700 In-Reply-To: <871sr0wcto.fsf@netris.org> (Mark H. Weaver's message of "Sun, 04 Jun 2017 01:18:11 -0400") Message-ID: <878tl8pag3.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -2.8 (--) X-Debbugs-Envelope-To: 27152 Cc: Ludovic =?utf-8?Q?Court=C3=A8s?= , 27152@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.8 (--) Hello Mark, Mark H Weaver writes: > Maxim Cournoyer writes: > >> Mark H Weaver writes: >> >>> Maxim Cournoyer writes: >>> >>>> Why not let good old sed have a run at it? Seems like a simple find >>>> and replace operation, and 'block looks nicer than _IOFBF to my >>>> eyes. >>> >>> If we did that, then Guix would stop working with guile-2.0. Given that >>> guile-2.2 is not yet available from many popular distros, I think it >>> would be unwise to drop guile-2.0 at this time. >> >> Isn't Guile included in the Guix binary releases? > > Yes, but that's not the only supported method to install Guix. While I > acknowledge that most new users are happy to use our binary tarball, > many users prefer to compile our source tarball, or to try out a Guix > package provided by their existing distribution. > > Security conscious users tend to be nervous about entrusting their > computer's security to a source of precompiled binaries that is new to > them. > > While it's true that they will need our bootstrap binaries, and that > they are highly likely to end up using our binary substitutes before > long, it nonetheless seems to me that it is best not to ask newcomers to > trust a large binary from us as their first step into our community, > without providing other easy methods that are more comfortable to them. > Users are comfortable installing a package from a distro that they've > already put their trust in. > > So, I would prefer to continue supporting guile-2.0 until guile-2.2 is > more widely deployed in popular distros, or at least until it becomes a > hassle to continue supporting guile-2.0. > > I'll also mention that there's apparently an unresolved bug somewhere > (guile2.2-ssh?) that prevents us from using guix-based-on-guile-2.2 on > hydra.gnu.org: > > https://bugs.gnu.org/26976 > > Mark OK, I understand better your point of view now, thanks for taking the time to explain it in details! I'd be somewhat concerned though about Guix sooner than later not running smoothly on Guile 2.0 due to the vast majority of users using and testing with Guile 2.2 rather than Guile 2.0. There was some breaking changes in 2.2, and it seems like wanting to support both might lead to code complexity or restraint that would otherwise allow simplifications and clean-ups of the code base. Also, nothing is stopping security minded individuals from building Guile 2.2 from sources, so the argument about security seems a bit moot to me. But I will leave it to the Guix maintainers to decide what works best for minimizing their load :) Thanks again for sharing your thoughts, Maxim From debbugs-submit-bounces@debbugs.gnu.org Sun Jun 04 18:04:53 2017 Received: (at 27152) by debbugs.gnu.org; 4 Jun 2017 22:04:53 +0000 Received: from localhost ([127.0.0.1]:56217 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dHddh-00040z-VD for submit@debbugs.gnu.org; Sun, 04 Jun 2017 18:04:53 -0400 Received: from world.peace.net ([50.252.239.5]:42092) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dHddg-00040i-LE for 27152@debbugs.gnu.org; Sun, 04 Jun 2017 18:04:48 -0400 Received: from pool-72-93-32-114.bstnma.east.verizon.net ([72.93.32.114] helo=jojen) by world.peace.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dHdda-0004Fr-9F; Sun, 04 Jun 2017 18:04:42 -0400 From: Mark H Weaver To: Maxim Cournoyer Subject: Re: bug#27152: deprecation warnings with Guile 2.2.2 References: <87wp8y2ijw.fsf@elephly.net> <87h90091y4.fsf@gnu.org> <871sr1yiik.fsf@netris.org> <87h8zxr89y.fsf@gmail.com> <871sr0wcto.fsf@netris.org> <878tl8pag3.fsf@gmail.com> Date: Sun, 04 Jun 2017 18:04:30 -0400 In-Reply-To: <878tl8pag3.fsf@gmail.com> (Maxim Cournoyer's message of "Sat, 03 Jun 2017 22:51:24 -0700") Message-ID: <87h8zvv28h.fsf@netris.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 27152 Cc: Ludovic =?utf-8?Q?Court=C3=A8s?= , 27152@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.0 (/) Maxim Cournoyer writes: > Mark H Weaver writes: > >> Maxim Cournoyer writes: >> >>> Mark H Weaver writes: >>> >>>> Maxim Cournoyer writes: >>>> >>>>> Why not let good old sed have a run at it? Seems like a simple find >>>>> and replace operation, and 'block looks nicer than _IOFBF to my >>>>> eyes. >>>> >>>> If we did that, then Guix would stop working with guile-2.0. Given that >>>> guile-2.2 is not yet available from many popular distros, I think it >>>> would be unwise to drop guile-2.0 at this time. >>> >>> Isn't Guile included in the Guix binary releases? >> >> Yes, but that's not the only supported method to install Guix. While I >> acknowledge that most new users are happy to use our binary tarball, >> many users prefer to compile our source tarball, or to try out a Guix >> package provided by their existing distribution. >> >> Security conscious users tend to be nervous about entrusting their >> computer's security to a source of precompiled binaries that is new to >> them. >> >> While it's true that they will need our bootstrap binaries, and that >> they are highly likely to end up using our binary substitutes before >> long, it nonetheless seems to me that it is best not to ask newcomers to >> trust a large binary from us as their first step into our community, >> without providing other easy methods that are more comfortable to them. >> Users are comfortable installing a package from a distro that they've >> already put their trust in. >> >> So, I would prefer to continue supporting guile-2.0 until guile-2.2 is >> more widely deployed in popular distros, or at least until it becomes a >> hassle to continue supporting guile-2.0. >> >> I'll also mention that there's apparently an unresolved bug somewhere >> (guile2.2-ssh?) that prevents us from using guix-based-on-guile-2.2 on >> hydra.gnu.org: >> >> https://bugs.gnu.org/26976 >> >> Mark > > OK, I understand better your point of view now, thanks for taking the > time to explain it in details! I'd be somewhat concerned though about > Guix sooner than later not running smoothly on Guile 2.0 due to the vast > majority of users using and testing with Guile 2.2 rather than Guile > 2.0. There was some breaking changes in 2.2, and it seems like wanting to > support both might lead to code complexity or restraint that would > otherwise allow simplifications and clean-ups of the code base. > > Also, nothing is stopping security minded individuals from building > Guile 2.2 from sources, so the argument about security seems a bit moot > to me. It's true that security conscious users would still have the option of building Guix, Guile, GnuTLS, and maybe some other prerequisites from source code, but that's a lot of work to try Guix for the first time. The other option currently available to them is to install a 'guix' package from their distro, but I guess that most of those distro packages would have to be dropped (or not upgraded anytime soon) if we stop supporting guile-2.0. Having said all of this, I acknowledge that it's not a strong argument, and if it starts becoming difficult to support guile-2.0, then we should drop that support. I don't feel strongly about it. > Thanks again for sharing your thoughts, Likewise, thanks for the discussion! Mark From debbugs-submit-bounces@debbugs.gnu.org Sat Aug 26 06:09:02 2017 Received: (at control) by debbugs.gnu.org; 26 Aug 2017 10:09:03 +0000 Received: from localhost ([127.0.0.1]:56049 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dlY1W-0002JE-ON for submit@debbugs.gnu.org; Sat, 26 Aug 2017 06:09:02 -0400 Received: from eggs.gnu.org ([208.118.235.92]:49613) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dlY1U-0002Ig-2C for control@debbugs.gnu.org; Sat, 26 Aug 2017 06:09:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dlY1L-0001XU-0U for control@debbugs.gnu.org; Sat, 26 Aug 2017 06:08:54 -0400 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD autolearn=disabled version=3.3.2 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:32855) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dlY1K-0001XQ-TD for control@debbugs.gnu.org; Sat, 26 Aug 2017 06:08:50 -0400 Received: from x590d0e4d.dyn.telefonica.de ([89.13.14.77]:49926 helo=ribbon) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dlY1K-0001A7-9g for control@debbugs.gnu.org; Sat, 26 Aug 2017 06:08:50 -0400 Date: Sat, 26 Aug 2017 12:08:48 +0200 Message-Id: <87bmn2bpzj.fsf@gnu.org> To: control@debbugs.gnu.org From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: control message for bug #27152 MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-Spam-Score: -5.0 (-----) X-Debbugs-Envelope-To: control X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -5.0 (-----) tags 27152 wontfix close 27152 From unknown Sat Jun 21 03:29:01 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Sat, 23 Sep 2017 11:24:06 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator