From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Thompson, David" Subject: Re: Invalid nar signature Date: Thu, 15 Jan 2015 08:39:01 -0500 Message-ID: References: <87zjapejo3.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me> <87ppbkompf.fsf@gnu.org> <87ppbkfw4w.fsf@gnu.org> <87ppbkedf2.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me> <871tnz8qwx.fsf@gnu.org> <87mw5kkbue.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me> <87zj9k74ob.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55762) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YBkjo-0000k0-TE for guix-devel@gnu.org; Thu, 15 Jan 2015 08:45:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YBkjj-0004pl-OO for guix-devel@gnu.org; Thu, 15 Jan 2015 08:45:28 -0500 Received: from na3sys009aog128.obsmtp.com ([74.125.149.141]:44949 helo=mail-pa0-f54.google.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YBkjj-0004op-Hn for guix-devel@gnu.org; Thu, 15 Jan 2015 08:45:23 -0500 Received: by mail-pa0-f54.google.com with SMTP id fb1so17544181pad.13 for ; Thu, 15 Jan 2015 05:45:21 -0800 (PST) In-Reply-To: <87zj9k74ob.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: =?UTF-8?Q?Ludovic_Court=C3=A8s?= Cc: guix-devel On Thu, Jan 15, 2015 at 4:51 AM, Ludovic Court=C3=A8s wrote: > David Thompson skribis: > >> Despite that, I tried to compress the nar with bzip2 just for fun, but I >> ran into another problem: >> >> warning: call to primitive-fork while multiple threads are running; >> further behavior unspecified. See "Processes" in the >> manual, for more information. >> >> I'm running a REPL server in addition to the web server, but I imagine >> the web server also spawns additional threads to handle requests, so >> either way 'filtered-output-port' won't work here. > > (web server http) does not use threads so it should be OK. But we=E2=80= =99ll > see that afterwards. :-) Ah, okay. Even so, requiring a single-threaded application in order to use compressed/decompressed ports makes hacking on 'guix publish' inconvenient, as it eliminates use of the REPL. But sure, we'll deal with this afterwards. - Dave