From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=)
Subject: bug#33368: "guix archive" fails because of guix-authenticate
Date: Thu, 15 Nov 2018 11:43:56 +0100
Message-ID: <87h8gi4o43.fsf@gnu.org>
References: <m1d0r8259u.fsf@fastmail.net> <87bm6sklwy.fsf@gnu.org>
	<m1ftw3zoka.fsf@fastmail.net> <87muqbb9wq.fsf@gnu.org>
	<m1tvkizrcf.fsf@ordinateur-de-catherine--konrad.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58787)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gNF8x-0007BX-Ff
	for bug-guix@gnu.org; Thu, 15 Nov 2018 05:45:04 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gNF8w-00036R-EX
	for bug-guix@gnu.org; Thu, 15 Nov 2018 05:45:03 -0500
Received: from debbugs.gnu.org ([208.118.235.43]:48773)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1gNF8w-000368-9b
	for bug-guix@gnu.org; Thu, 15 Nov 2018 05:45:02 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gNF8w-0001hh-1F
	for bug-guix@gnu.org; Thu, 15 Nov 2018 05:45:02 -0500
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.33368.D33368.15422786466456@debbugs.gnu.org>
In-Reply-To: <m1tvkizrcf.fsf@ordinateur-de-catherine--konrad.home> (Konrad
	Hinsen's message of "Thu, 15 Nov 2018 09:18:24 +0100")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 33368-done@debbugs.gnu.org

Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:

> ludo@gnu.org (Ludovic Court=C3=A8s) writes:
>
>> Oops, this is fixed in commit 7a54b2281d1f60fd0ae2e058c219c5a600ad756b
>> (the next commit, 0fe1fba4af41f267c4bb2c006fb37f42422ab703, changes Guix
>> itself so that the script is installed as LIBEXECDIR/guix/authenticate,
>> for consistency.)
>>
>> To test it, you=E2=80=99ll have to run =E2=80=98guix pull=E2=80=99 as ro=
ot and to restart the
>> daemon.
>
> Done, works, thanks!
>
> It would be nice if guix could detect an outdated daemon and ask for an
> update. Technically that shouldn't be hard to do, but it requires
> keeping a daemon API version number.

There=E2=80=99s a protocol version that clients get during the handshake, so
clients could report about =E2=80=9Cold=E2=80=9D daemons.

Now, the client-daemon protocol is meant to be backward-compatible and
to change rarely, so I=E2=80=99m not sure if we should warn about it.

Thoughts?

Thanks,
Ludo=E2=80=99.