all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Saku Laesvuori <saku@laesvuori.fi>
To: help-guix@gnu.org
Subject: Substitute not being used
Date: Mon, 25 Jul 2022 21:42:10 +0300	[thread overview]
Message-ID: <20220725180100.x6gfih3xx6gbcq77@X-kone> (raw)

[-- Attachment #1: Type: text/plain, Size: 953 bytes --]

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)

$ 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.

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?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2022-07-25 19:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 18:42 Saku Laesvuori [this message]
2022-07-25 22:12 ` Substitute not being used Csepp
2022-08-18 18:14   ` Tobias Geerinckx-Rice
2022-08-18 10:43 ` zimoun
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220725180100.x6gfih3xx6gbcq77@X-kone \
    --to=saku@laesvuori.fi \
    --cc=help-guix@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.