From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44522) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cwpwI-00029H-Tq for guix-patches@gnu.org; Sat, 08 Apr 2017 08:58:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cwpwI-00067U-1n for guix-patches@gnu.org; Sat, 08 Apr 2017 08:58:02 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:39005) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cwpwH-00067D-UP for guix-patches@gnu.org; Sat, 08 Apr 2017 08:58:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cwpwH-0005yt-JF for guix-patches@gnu.org; Sat, 08 Apr 2017 08:58:01 -0400 Subject: bug#26366: Building Guix from within a container Resent-Message-ID: Date: Sat, 8 Apr 2017 12:57:46 +0000 From: Pjotr Prins Message-ID: <20170408125746.GA14578@mail.thebird.nl> References: <87inmjcn1o.fsf@lassieur.org> <87fuhjqdkf.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <87fuhjqdkf.fsf@gnu.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 26366@debbugs.gnu.org, =?UTF-8?Q?Cl=C3=A9ment?= Lassieur On Sat, Apr 08, 2017 at 02:38:40PM +0200, Ludovic Courtès wrote: > These warnings come from Guile 2.0 trying to load Guile 2.2 .go files > (in 2.2, .go files are ELF files; in 2.0, it’s a custom format.) > > They’re annoying but harmless and just mean that you have a mixture of > 2.2 and 2.0 files in GUILE_LOAD_COMPILED_PATH. To be honest I think we should get rid of harmless messages - or only show the first or last one (perhaps state that there are more similar messages which can be seen in debug mode). I understand that this is a guile thing, but the same holds for guix with all the warnings we get when sylinks/files are duplicated in the store. Irony is that sometimes we don't get warnings when we need them. Such as when you specify a substitute-url and if the server does not exist there is no indication. I have wasted many a time on figuring that problem out. It would be nice to have a policy where we do not show all harmless warnings by default, but only in debug mode, as well as missing services etc. I am happy to run --debug when I actually face a problem. Pj.