From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=)
Subject: bug#22629: =?UTF-8?Q?=E2=80=9CStable=E2=80=9D?= branch
Date: Fri, 31 Aug 2018 00:02:48 +0200
Message-ID: <878t4nqzqv.fsf@gnu.org>
References: <87vb5vsffd.fsf@gnu.org> <87pny2iks2.fsf@gnu.org>
	<877ekagtg9.fsf@netris.org> <87zhx5msfl.fsf@pompo.co>
	<87lg8pccys.fsf_-_@netris.org> <87zhx59gh3.fsf@elephly.net>
	<m1wos82y70.fsf@ordinateur-de-catherine--konrad.home>
	<875zzs9wzl.fsf@netris.org> <m1d0u0qi4v.fsf@fastmail.net>
	<874lfcxd2v.fsf_-_@gnu.org> <87wos8lzcj.fsf@pompo.co>
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]:36433)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1fvV76-00074j-KO
	for bug-guix@gnu.org; Thu, 30 Aug 2018 18:08:30 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1fvV2o-00065o-1P
	for bug-guix@gnu.org; Thu, 30 Aug 2018 18:04:03 -0400
Received: from debbugs.gnu.org ([208.118.235.43]:34516)
	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 1fvV2n-00065k-Uk
	for bug-guix@gnu.org; Thu, 30 Aug 2018 18:04:01 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1fvV2n-00062f-Q2
	for bug-guix@gnu.org; Thu, 30 Aug 2018 18:04:01 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.22629.B22629.153566659123157@debbugs.gnu.org>
In-Reply-To: <87wos8lzcj.fsf@pompo.co> (Alex Sassmannshausen's message of
	"Thu, 30 Aug 2018 16:10:20 +0200")
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: Alex Sassmannshausen <alex@pompo.co>
Cc: 26608@debbugs.gnu.org, 22629@debbugs.gnu.org, 32022@debbugs.gnu.org

Hi Alex,

(Cc=E2=80=99ing <https://bugs.gnu.org/32022> and <https://bugs.gnu.org/2660=
8>,
which are related.)

Alex Sassmannshausen <alex@pompo.co> skribis:

> I don't know if this is what Konrad desires, but from my perspective, a
> desirable part of the definition of stable would be a that the build
> farms have produced a set of binaries/substitutes for a given Guix
> revision that is "good enough".

I just had a bright idea (yes!): this can be addressed by writing
something like this in ~/.config/guix/channels.scm:

  (map latest-commit-with-substitutes-available
       %default-channels)

The hypothetical =E2=80=98latest-commit-with-substitutes-available=E2=80=99=
 would use
(git) and (guix ci) to find the latest commit for which substitutes of
interest are available, and would return:

  (channel
    ;; =E2=80=A6
    (commit "cabbag3"))   ;the ideal commit

This has to be done with great care to prevent a downgrade attack and to
make sure the user doesn=E2=80=99t miss out on security updates, but maybe =
we
could provide a procedure that makes reasonable choices.

Food for thought=E2=80=A6

Ludo=E2=80=99.