From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id sJnMOXCO/F9PaQAA0tVLHw (envelope-from ) for ; Mon, 11 Jan 2021 17:44:16 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id WEaaNXCO/F+jDAAAB5/wlQ (envelope-from ) for ; Mon, 11 Jan 2021 17:44:16 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 31D2B9402A8 for ; Mon, 11 Jan 2021 17:44:16 +0000 (UTC) Received: from localhost ([::1]:34794 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kz1El-00045d-4b for larch@yhetil.org; Mon, 11 Jan 2021 12:44:15 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:55964) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kz1DU-0002l4-JZ for help-guix@gnu.org; Mon, 11 Jan 2021 12:42:56 -0500 Received: from mail-wr1-x42b.google.com ([2a00:1450:4864:20::42b]:37310) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kz1DR-0003xS-Ux for help-guix@gnu.org; Mon, 11 Jan 2021 12:42:56 -0500 Received: by mail-wr1-x42b.google.com with SMTP id i9so658284wrc.4 for ; Mon, 11 Jan 2021 09:42:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version:content-transfer-encoding; bh=Yaek5jWxq6rVkW8h1s8G4dG4KqQIC7V3nrtBC2ax+Co=; b=jra1nW4yWU3sqzwcwArimbYdBlHeway0KWzaI4ZGYhpJ3WW/bZkhmv3XJxRXGJBGnF gzPc1raV/5KFtQVXomkebg4XayuWUKcZmIvDXTwhtkyoKHuOEsKIRyk9d9XB7eL2kz5J tfzBqbRbQP9ra+F56Y33HxDZ6mfH/Tny3c4CdJ2fu2dap56mYvb1R86Lh33umw5+sOHR ELu+75J5oLNP5XhudBPRlvtkJl+UsezAgKfHl1xmu00uUISxAolJL4pR8b/vvP7j1fRA A3n+aIgRSSRn7VDp2892gtLS0mQBWEW2R22d1p5YzMgRf7nWYBHeYlO31+waN/HmPxKd rcsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version:content-transfer-encoding; bh=Yaek5jWxq6rVkW8h1s8G4dG4KqQIC7V3nrtBC2ax+Co=; b=F7Z2d8cR953nTxUZAGFDesKiw9nh+0PdNMXMXfMrZP5XwL++ByM/uLi9ySB64mGJ3h RiadVfDy1HTdxCFM4KPo5LW8jpIdK3kmiOQnbQvt+8vFezQD8d2BUZQrqrNeXSXSPDEx Xk/kzsnlDrhjoZbC85Cryu49sRgAtDM4gSA2XnRYSFdvR/o5sqXj1H1cpfXRPzDl0V12 uEvsh9LvV9t6lrwsxnzdk8RulTRX+/G61t/ILvL4DI+Cyf3ia11TG2SWKE45rzWWVDyc RdT6l5YHf4revVMTv8gIe7sp4mGwg/NBe0AzNDMCvc8sz/RLdXwiofiy+Oip+YlBCIFL lY+Q== X-Gm-Message-State: AOAM532BVRPTIPGf698wGFKF20VUOIBlKXf9Dcf+jq9vuNBcQeiSRAg8 GMy4/4z08znRWIwFmLlxuqrgI19RNoVvAw== X-Google-Smtp-Source: ABdhPJzZMAG1VHsuhhxWSCczBKdwTQ7SjeAGXhdrSAC32AXdU4gEgPFpgTkp204vBelB/pEpRcXLOg== X-Received: by 2002:adf:c403:: with SMTP id v3mr244126wrf.55.1610386971047; Mon, 11 Jan 2021 09:42:51 -0800 (PST) Received: from lili ([2a01:e0a:59b:9120:65d2:2476:f637:db1e]) by smtp.gmail.com with ESMTPSA id h15sm432109wru.4.2021.01.11.09.42.50 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 11 Jan 2021 09:42:50 -0800 (PST) From: zimoun To: Phil Subject: Re: Channel details of profile generation In-Reply-To: <85h7nqqlnv.fsf@beadling.co.uk> References: <857dp1yg0f.fsf@beadling.co.uk> <86o8ibs95q.fsf@gmail.com> <85mtxor4pq.fsf@beadling.co.uk> <85h7nqqlnv.fsf@beadling.co.uk> Date: Mon, 11 Jan 2021 18:34:38 +0100 Message-ID: <86a6tftm1d.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2a00:1450:4864:20::42b; envelope-from=zimon.toutoune@gmail.com; helo=mail-wr1-x42b.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: help-guix Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: "Help-Guix" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -3.05 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=jra1nW4y; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of help-guix-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=help-guix-bounces@gnu.org X-Migadu-Queue-Id: 31D2B9402A8 X-Spam-Score: -3.05 X-Migadu-Scanner: scn1.migadu.com X-TUID: jcASxsSQMXZ5 Hi, On Sat, 09 Jan 2021 at 13:34, Phil wrote: > Given a date/time and a profile, it should be possible not only to tell > me what generation of that profile was active at that date/time, but > also the corresponding commit ids on the heads of each channels used to > source the packages. Yes. It is already possible because the information is in the file =E2=80=99/manifest=E2=80=99. However, there is no tooling to do t= hat easily yet. Maybe an option =E2=80=99--export-manifest=E2=80=99 is coming=E2=80= =A6 ;-) http://logs.guix.gnu.org/guix-hpc/2021-01-11.log > So my tool works like this - and, I believe, the output is correct and > methodology sane: > > --8<---------------cut here---------------start------------->8--- > > ubuntu@test-image:~$ guix repl -- profile-generation-on-datetime.scm 2020= -12-24T12:00:00 guix-profiles/py-test-pkg-profile > > Profile Dir: guix-profiles/py-test-pkg-profile-39-link > > \Generation 39 Dec 24 2020 11:24:23\ > > Package/Channel Details: > py-test-pkg 1.53 > URL: https://git.savannah.gnu.org/git/guix.git > Branch: master > Commit: 13d532a91178be7b6919b85685b150f941116dfc > > URL: ssh://git@bbserver:7799/ea/guix-packages.git > Branch: master > Commit: ad21880272356219a9e33888cd0c237c8ece02d3 > > python 3.8.2 > URL: https://git.savannah.gnu.org/git/guix.git > Branch: master > Commit: 13d532a91178be7b6919b85685b150f941116dfc > > --8<---------------cut here---------------end--------------->8--- Cool! > Now, ignoring the date/time logic, all my tool is doing is returning the > Package/Channel Details (via the profile manifest) as per above - when > provided with a profile and a generation number. Yes. > ***This is the crux of my original question - can I get the commit id data > supplied by my script for a given profile/generation, from the command > line using already available guix tools?*** Not yet. > (I think the answer to this is - no you cannot do it from the command lin= e) > > The follow-up question was - if not, is my script's approach sane? It seems. From my understanding after a quick look. > PART 2: > > Separately I, probably incorrectly, thought that I might be able to use s= ome > incantation of 'guix pull -l' to achieve the same ends as my script, > given pull's output does seem to include the channel commit ids. Well, it=E2=80=99s what I have tried to explain. :-) > I can't argue with this - I need to do some more digging here to see why > my use of guix pull is barfing, there are some differences between your > test and mine - for example the use of the ssh protocol in the second > channel, so the 2 tests are not identical, but as you see below I run > into issues replicating even with the guix-science channel. Do you mean issues when replicating my example with only the channels guix and guix-science? > --8<---------------cut here---------------start------------->8--- > $ guix package -m my-manifest-2.scm -p /tmp/test-profile > The following packages will be installed: > python 3.8.2 > python-nose-exclude 0.5.0 > > $ guix package -p /tmp/test-profile -l=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20 > \Generation 1 Jan 09 2021 11:39:07\ > python 3.8.2 out /gnu/store/9h5pjxj879y9rzy04m1v9835l4fblw= 95-python-3.8.2 > > \Generation 2 Jan 09 2021 11:43:58\ (current) > + python-nose-exclude 0.5.0 out /gnu/store/k3n4qxakw4rjjg81sfkaxc= gln5xhaj3r-python-nose-exclude-0.5.0 > > $ guix pull -p /tmp/test-profile -l=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20 > \Generation 1 Jan 09 2021 11:39:07\ > python 3.8.2 > \Generation 2 Jan 09 2021 11:43:58\ (current) > python-nose-exclude 0.5.0 > python 3.8.2 > ^C <-- It's hanging here so I exit with ctrl-c > --8<---------------cut here---------------end--------------->8--- By hanging, do you mean =E2=80=9Cyou were not enough patient=E2=80=9C? or = =E2=80=9Cafter several minutes=E2=80=9D (10-20min), it was not finished yet? > Here's the final bit of the strace from the last output to stdout to the > 'guix pull' hanging: > > --8<---------------cut here---------------start------------->8--- > write(1, " py-test-pkg 1.65-1.e4c466a\n", 30 py-test-pkg 1.65-1.e4c466a [...] > read(14,=20 > --8<---------------cut here---------------end--------------->8--- Thank for the details. Well, does it fail or is it slow? > I'm running out of steam a bit here but both this error in ui.scm@2154 > and the original backtrace I posted ui.scm@2127 come from the > run-guix-command function on attempting a primitive-load of, I assume, > the current guix script. The bracktrace is a fail. But I am not able to reproduce. For your experiment, I do not know if it is failure or slowness. All the best, simon