From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#33272: guix refresh/download backtrace error when missing nss-certs Date: Mon, 5 Nov 2018 15:48:02 -0500 Message-ID: <20181105204802.GD19298@jasmine.lan> References: <20181105202650.GB19298@jasmine.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="qGV0fN9tzfkG3CxV" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50493) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gJlo1-0005k9-Lt for bug-guix@gnu.org; Mon, 05 Nov 2018 15:49:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gJlny-0003Zr-91 for bug-guix@gnu.org; Mon, 05 Nov 2018 15:49:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:59691) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gJlny-0003Zb-15 for bug-guix@gnu.org; Mon, 05 Nov 2018 15:49:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gJlnx-0002rh-VA for bug-guix@gnu.org; Mon, 05 Nov 2018 15:49:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: swedebugia Cc: 33272@debbugs.gnu.org --qGV0fN9tzfkG3CxV Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 05, 2018 at 09:39:15PM +0100, swedebugia wrote: > How do we catch the error? I am basically a novice Schemer still, so you will have to figure out most of this on your own, unless someone else brings more advice :) In general, dealing with exceptions in Guile: https://www.gnu.org/software/guile/manual/html_node/Exceptions.html There are lots of examples of how to use those mechanisms in the Guix source code =E2=80=94 the error message in your original email comes from a caught exception in (guix build download). You'll need to find out what is crashing and generating the backtrace, and then decide what counts as a failure mode that we want to catch in that context. --qGV0fN9tzfkG3CxV Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlvgrIIACgkQJkb6MLrK fwhSxxAAltxSMyI6uq4FJ3LwFgr55ZNxGWLPGfVw8T/IVkB+86J2ZzaYDR1mADRZ 67Luqu4wqUrzWKbN/0XabZnuGpniyinIJuU+V/uxgynmfY/SeU8PKwseh+zHaKTd TYBpF4oqa69IepDXjflepL3839PpRrjgX0KUTq2lSGMjfeBKJsrWSWI9q++FG6Y3 PfBKUPPLpDZ5zXZIumsnegqleQeGd8tRUU2UPFwCPEd0lJ2b0X4oob6+JLiGWzGh IcGdHVBnJCVnCcA16eUUTZufDn4pWOYVOhalIQkXaaWybtSfJAXPUgGA+ZwCamxG b4jK5XxTyTUZyiDsRcmpggibrZDrEP1j8VtMKLBWvZG/+r6IeB8U34/wwc8hlOAA NzcaCmb2uzxsEkuTtNhadgv78gIdyvMKWahHSMpnM7P9hwFnA1JRVq3mnOxytqeR OiuhCKATBSGCgYT9aqQAgHifzimHjw7DxDmmhjULOXwiDlKd4zk6CvjeEk6+QfUl NeQ1H9sBaFLhqBPG6r7tVbE9SMXOO7OceUuBKljdoK+U/1PiiEoYbJ2c8F+DeFHU Ke3djrHVq1sXp05PCt3t5bmRYgyBLw7ug2oxvMODydT2haZLICpwe4/y+R8IvUHN nwKBrix0SX1jF/BxPkRuDDhQcuYyi6TezqDwfqHiDhPKqcPDYVA= =1+gX -----END PGP SIGNATURE----- --qGV0fN9tzfkG3CxV--