From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: verbose backtraces when =?utf-8?B?4oCcaW52b2tl4oCd?= fails Date: Mon, 21 Jan 2019 09:21:25 +0100 Message-ID: <87ef96e7zu.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:41513) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1glUpx-0001ZZ-6T for guix-devel@gnu.org; Mon, 21 Jan 2019 03:21:42 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1glUpw-0002rX-Eg for guix-devel@gnu.org; Mon, 21 Jan 2019 03:21:41 -0500 Received: from sender-of-o53.zoho.com ([135.84.80.218]:21761) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1glUpw-0002p4-5l for guix-devel@gnu.org; Mon, 21 Jan 2019 03:21:40 -0500 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" To: guix-devel@gnu.org Hi Guix, I=E2=80=99d like us to catch the errors raised by =E2=80=9Cinvoke=E2=80=9D,= so that the output of a failing build looks nicer again. Before we used =E2=80=9Cinvoke=E2=80=9D build phases evaluating to #f would= cause the build system to abort and print a nice message. Now users get an ugly backtrace that is much too verbose for what it=E2=80=99s trying to say, nam= ely that a command invocation failed. There is no value in the backtrace itself (users don=E2=80=99t care where =E2=80=9Cinvoke=E2=80=9D is defined, for example); we only want the error m= essage. Shall we fix this on core-updates? -- Ricardo