From: zimoun <zimon.toutoune@gmail.com>
To: Saku Laesvuori <saku@laesvuori.fi>, help-guix@gnu.org
Subject: Re: Substitute not being used
Date: Thu, 18 Aug 2022 12:43:07 +0200 [thread overview]
Message-ID: <87lerl7ryc.fsf@gmail.com> (raw)
In-Reply-To: <20220725180100.x6gfih3xx6gbcq77@X-kone>
Hi,
On lun., 25 juil. 2022 at 21:42, Saku Laesvuori <saku@laesvuori.fi> wrote:
> I'm trying to install telegram-desktop and I *think* guix should be able
> to substitute it, but instead it tries to build it. (which then
> consistently fails, which is why I started looking into it)
Do you have allowed substitutes?
> $ guix describe
> Generation 11 Jul 25 2022 10:15:41 (current)
> guix 2367469
> repository URL: https://git.savannah.gnu.org/git/guix.git
> commit: 236746900f062b34c857c4aab21709bcf1448ac7
>
> There is a build for telegram-desktop for x86_64-linux
> (https://ci.guix.gnu.org/build/1119886/details) that is part of an
> evaluation on the same commit that my guix is on.
--8<---------------cut here---------------start------------->8---
$ guix time-machine --commit=2367469 -- weather telegram-desktop
computing 1 package derivations for x86_64-linux...
looking for 1 store items on https://ci.guix.gnu.org...
https://ci.guix.gnu.org
100.0% substitutes available (1 out of 1)
at least 44,6 MiB of nars (compressed)
100,2 MiB on disk (uncompressed)
at least 1 000 queued builds
powerpc64le-linux: 990 (99.0%)
i686-linux: 6 (.6%)
x86_64-linux: 4 (.4%)
build rate: 28.06 builds per hour
x86_64-linux: 11.92 builds per hour
aarch64-linux: 7.26 builds per hour
i686-linux: 5.42 builds per hour
powerpc64le-linux: 6.34 builds per hour
looking for 1 store items on https://bordeaux.guix.gnu.org...
https://bordeaux.guix.gnu.org
100.0% substitutes available (1 out of 1)
21,6 MiB of nars (compressed)
100,2 MiB on disk (uncompressed)
(continuous integration information unavailable)
--8<---------------cut here---------------end--------------->8---
> One confusing thing I've noticed while looking into this is that when
> guix starts building telegram-desktop it says it's building
>
> /gnu/store/aqhqhza58lzkvzxrspzbf8v9ssqvkxri-telegram-desktop-2.9.3.drv
>
> but the derivation on ci.guix.gnu.org is
>
> /gnu/store/gz50dz1rfaik7s33d22r2lmyzwd7f7bm-telegram-desktop-2.9.3.drv
>
> Can someone explain what's happening here and what I have misunderstood?
--8<---------------cut here---------------start------------->8---
$ guix time-machine --commit=2367469 -- build telegram-desktop -n -d
The following derivation would be built:
/gnu/store/aqhqhza58lzkvzxrspzbf8v9ssqvkxri-telegram-desktop-2.9.3.drv
$ guix time-machine --commit=2367469 -- build telegram-desktop -n -d --no-grafts
/gnu/store/gz50dz1rfaik7s33d22r2lmyzwd7f7bm-telegram-desktop-2.9.3.drv
--8<---------------cut here---------------end--------------->8---
However, as you noticed, the ungrafted version seems substituable and
not the grafted one.
I agree it is confusing that “guix weather” reports an avaibility when
it is not the case for “guix build”. Maybe, it can be considered as a
bug.
Cheers,
simon
next prev parent reply other threads:[~2022-08-18 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 18:42 Substitute not being used Saku Laesvuori
2022-07-25 22:12 ` Csepp
2022-08-18 18:14 ` Tobias Geerinckx-Rice
2022-08-18 10:43 ` zimoun [this message]
2022-08-19 7:59 ` Saku Laesvuori
-- strict thread matches above, loose matches on Subject: below --
2022-07-26 1:29 Nathan Dehnel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lerl7ryc.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=saku@laesvuori.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).