From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:46549) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jDAgh-0000bS-9O for guix-patches@gnu.org; Sat, 14 Mar 2020 13:35:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jDAgg-0003HL-8X for guix-patches@gnu.org; Sat, 14 Mar 2020 13:35:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:56177) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jDAgg-0003Fe-3S for guix-patches@gnu.org; Sat, 14 Mar 2020 13:35:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jDAgg-0007pP-15 for guix-patches@gnu.org; Sat, 14 Mar 2020 13:35:02 -0400 Subject: [bug#39777] [PATCH V3 04/11] gnu: python-jsonschema: Update to 3.2.0. Resent-Message-ID: Date: Sat, 14 Mar 2020 13:33:56 -0400 From: Leo Famulari Message-ID: <20200314173356.GD23309@jasmine.lan> References: <20200309081827.13489-1-tanguy@bioneland.org> <20200309081827.13489-4-tanguy@bioneland.org> <20200311191542.GB13879@jasmine.lan> <20200312084828.o5lsuze5mmdrjg6w@rafflesia> <20200312174421.GA2140@jasmine.lan> <20200313084541.zeditu3oaouqm2du@rafflesia> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200313084541.zeditu3oaouqm2du@rafflesia> 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: Tanguy Le Carrour Cc: 39777@debbugs.gnu.org On Fri, Mar 13, 2020 at 09:45:41AM +0100, Tanguy Le Carrour wrote: > So, I'm left with the same question: > - why does it fail with `No module named jsonschema`? and with a second one I'm not sure, I'm not that strong with Python. > - why wasn't I able to reproduce the error from the build directory?! There are lots of things that could have changed. First, I would use `guix environment --pure` to try isolating the rest of the system, beginning to approximate the build chroot. You could even try `guix environment --container` if your system supports it. Second, the tests might be idempotent. You'll have a hard time reproducing the build environment exactly but it's usually possible to figure out why the test is failing.