From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#33419: guix package is not showing that the checksum is mismatching Date: Wed, 21 Nov 2018 23:16:12 +0100 Message-ID: <8736ruqdoz.fsf@gnu.org> References: <20181118150433.63437ece@alma-ubu> <87sgzwx11l.fsf@gnu.org> <20181121211808.039a4d17@alma-ubu> 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]:55334) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gPanu-0004gr-Rf for bug-guix@gnu.org; Wed, 21 Nov 2018 17:17:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gPant-0005Zh-TO for bug-guix@gnu.org; Wed, 21 Nov 2018 17:17:02 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:36034) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gPant-0005ZU-Q9 for bug-guix@gnu.org; Wed, 21 Nov 2018 17:17:01 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gPant-0004At-LH for bug-guix@gnu.org; Wed, 21 Nov 2018 17:17:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20181121211808.039a4d17@alma-ubu> ("=?UTF-8?Q?Bj=C3=B6rn_?= =?UTF-8?Q?H=C3=B6fling?="'s message of "Wed, 21 Nov 2018 21:18:08 +0100") 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: =?UTF-8?Q?Bj=C3=B6rn_?= =?UTF-8?Q?H=C3=B6fling?= Cc: 33419-done@debbugs.gnu.org Bj=C3=B6rn H=C3=B6fling skribis: > On Mon, 19 Nov 2018 21:30:46 +0100 > ludo@gnu.org (Ludovic Court=C3=A8s) wrote: > >> Hello, >>=20 >> Bj=C3=B6rn H=C3=B6fling skribis: > >> > Is it intended that this build-failure detail is not shown? I >> > suppose not. At least in a log it should be shown.=20=20 >>=20 >> I suspect you=E2=80=99re running an =E2=80=9Cold=E2=80=9D guix-daemon, a= ren=E2=80=99t you? >>=20 >> Could you try again with an up-to-date daemon (and client)? The code >> that prints hash mismatch errors when talking to recent daemons is in >> (guix status). > > Indeed! Short story: After really updating the daemon/root's Guix, it > works now. Cool! > Long story: Pffew, quite a journey. Hopefully upgrading the daemon on foreign distro will be easier and more natural with . Thanks, Ludo=E2=80=99.