unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Jack Hill <jackhill@jackhill.us>
To: Marius Bakke <mbakke@fastmail.com>
Cc: help-guix@gnu.org
Subject: Re: Why are these derivations different?
Date: Sat, 8 Jun 2019 22:43:14 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.20.1906082216410.5164@marsh.hcoop.net> (raw)
In-Reply-To: <878sub7qng.fsf@devup.no>

On Sat, 8 Jun 2019, Marius Bakke wrote:

> Jack Hill <jackhill@jackhill.us> writes:
>
>> Hi Guix,
>>
>> I'm trying to copy the store items for ungoogled-chromium from one of my
>> hosts that has many computational resources to another one that does not,
>> so that I do not have to build ungoogled-chromium on the less powerful
>> host.
>>
>> However, even after copying the store items using guix archive --export |
>> guix archive --import, the less powerful host wants to build
>> ungoogled-chromium because the derivations differ (see attachments).
>
> I suspect this has to do with grafts.  Guix is missing a substitute for
> the 'ungrafted' package and fails to realize the grafted derivation.
>
> Exporting with --no-grafts should do the trick.

Marius,

Thanks! That was it.

If you don't mind, I have a few follow up question to help me understand 
how everything works:

How is guix archive --no-grafts different from guix build --no-grafts? Oh, 
or after reading the manual for --no-grafts again, maybe I used the wrong 
incantation (guix build --no-grafts package-name instead of guix build 
package-name --no-grafts)?

What's really going on with --no-grafts. Is it that guix on my less 
powerful host has never seen the the ungoogled-chromium version build 
against the older dependencies, so doesn't accept the older version that 
could be grafted? I guess, I'm not sure exactly what you mean by "fails to 
realize the grafted derivation". Is that a bug?

Sorry, I don't think that question was very clear. It probably means that 
while I think I know what grafts are, I don't know enough about what's 
going on to ask the question properly. I think this all could be summarized 
as, "please explain more."

Many thanks,
Jack

  reply	other threads:[~2019-06-09  2:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-08 14:49 Why are these derivations different? Jack Hill
2019-06-08 20:45 ` Marius Bakke
2019-06-09  2:43   ` Jack Hill [this message]
2019-06-10 11:35     ` Marius Bakke
2019-06-10 17:25       ` Jack Hill

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=alpine.DEB.2.20.1906082216410.5164@marsh.hcoop.net \
    --to=jackhill@jackhill.us \
    --cc=help-guix@gnu.org \
    --cc=mbakke@fastmail.com \
    /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).