From mboxrd@z Thu Jan 1 00:00:00 1970 From: zimoun Subject: Re: bug#26608: channels.scm supporting substitutes Date: Tue, 3 Dec 2019 22:14:11 +0100 Message-ID: References: <874lxg77l4.fsf@dustycloud.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:35540) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1icFVC-00087S-Sz for help-guix@gnu.org; Tue, 03 Dec 2019 16:14:35 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1icFV6-0005QY-Qg for help-guix@gnu.org; Tue, 03 Dec 2019 16:14:29 -0500 Received: from mail-qv1-xf32.google.com ([2607:f8b0:4864:20::f32]:35311) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1icFV6-00054k-KU for help-guix@gnu.org; Tue, 03 Dec 2019 16:14:28 -0500 Received: by mail-qv1-xf32.google.com with SMTP id d17so2207501qvs.2 for ; Tue, 03 Dec 2019 13:14:24 -0800 (PST) In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Nome Grey Cc: help-guix Hi Nome Thank you for your message. You sent your email to all 3 bugs: 26608@debbugs.gnu.org, 32022@debbugs.gnu.org, 22629@debbugs.gnu.org. It is not a good practise. Instead, it appears to me more appropriate to send to help-guix@gnu.org. First note that these are closed: - 22629 on Sep 2nd 2018 - 32022 on Dec 17th 2018 so what they were proposing now exist in master, I bet. ;-) On Tue, 3 Dec 2019 at 21:40, Nome Grey wrote: > Ludovic posted some channels.scm code in September 2018 supporting using more substitutes. Second, it will help to point exactly where Ludo posted what you are referencing to. Because 22629, 26608 and 32022 are big threads. :-) > Unfortunately his code no longer functions due to an upgrade of guile-json in guix. If you know more or less the date, you can find the commit. And *if* this commit is after the big 0.15 overhaul, you can 1. Guix checkout with "guix pull --commit=" then 2. Git checkout your guix clone to this commit and 3. use "guix environment guix" to spawn an shell with all the dependencies available. And the code you are referencing should work. > Maybe I can learn enough to upgrade it to check the 'guix-master' evaluations to find the latest build of key packages. We'll see. Third, please describe what you are trying to achieve. All the best, simon