From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#26608: bug#22629: =?UTF-8?Q?=E2=80=9CStable=E2=80=9D?= branch Date: Tue, 04 Sep 2018 14:22:35 +0200 Message-ID: <8736upcv04.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> <875zzs9wzl.fsf@netris.org> <874lfcxd2v.fsf_-_@gnu.org> <87wos8lzcj.fsf@pompo.co> <878t4nqzqv.fsf@gnu.org> <87r2iau0wz.fsf@pompo.co> <87zhwywe8v.fsf@gnu.org> <87pnxtu1uw.fsf@pompo.co> 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]:40677) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fxAMJ-0007kU-84 for bug-guix@gnu.org; Tue, 04 Sep 2018 08:23:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fxAMI-0003dq-CH for bug-guix@gnu.org; Tue, 04 Sep 2018 08:23:03 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:40096) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fxAMI-0003dU-7z for bug-guix@gnu.org; Tue, 04 Sep 2018 08:23:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fxAMI-0003Dr-1g for bug-guix@gnu.org; Tue, 04 Sep 2018 08:23:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87pnxtu1uw.fsf@pompo.co> (Alex Sassmannshausen's message of "Tue, 04 Sep 2018 10:02:31 +0200") 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: Alex Sassmannshausen Cc: 26608@debbugs.gnu.org, 22629@debbugs.gnu.org, 32022@debbugs.gnu.org Hi Alex, Alex Sassmannshausen skribis: > So the example you provided is a user-defined policy to install the > latest version of Guix that is downloadable using substitutes (if guix > publish has published those already). > > As you say, in a similar vein, the end user could for themselves define > a policy that searches for a commit containing a specific successful > build, or a set of specific successful builds. Exactly. >> As I imagine it, the cost would be a few HTTP queries to the Cuirass >> API. I should try to come up with an example to better explain what I >> had in mind! > > Your example helps visualize this, thanks. > > Your example depends on there being a jobset that comprises the set of > packages you are interested in testing. Yes, and it=E2=80=99s hacky in that the substitute server and jobset names = are hard-coded, but you get the idea. > I imagine it is possible to do the same for an individual package / job. Yes. > The situation would be different if the end user wanted to perform a > similar operation for an arbitrary set of packages on their end. It would be quite similar: you would query the set of builds of an evaluation of the =E2=80=9Cguix-modular=E2=80=9D jobset and check whether t= he packages of interest were built. >> What I typically do is =E2=80=9Cguix pull && guix package -n -u=E2=80=9D= . Then I look >> at things that would be built; if, say, LibreOffice is among them, I >> wait for a little while and try again later, until I can get enough >> substitutes. That usually works okay, but it fails if it turns out that >> one of the dependencies fails to build: substitutes never become >> available in that case. > > Interesting. Do you think this kind of thing might be useful to have in > the Guix manual? Like, in a section about a "typical" desktop end-user > might manage their system day to day? It would make sense to have such a section I guess. However, before teaching users how to work around deficiencies of our infrastructure our processes ;-), I=E2=80=99d like us to improve them much as possible. I=E2= =80=99m sure we have room for improvement for instance in Cuirass. Thanks, Ludo=E2=80=99.