From: Emmanuel Medernach <emmanuel.medernach@gmail.com>
To: help-guix <help-guix@gnu.org>
Subject: Re: Local definitions and Virtual machine image
Date: Fri, 5 Jun 2020 16:54:20 +0200 [thread overview]
Message-ID: <CAC_pKx8XmO2V23anxW6zcDTPXwmBtUOayGU0SxhtyKi8H75YLQ@mail.gmail.com> (raw)
In-Reply-To: <87k10ouqa7.fsf@gnu.org>
On Wed, Jun 3, 2020 at 5:23 PM Marius Bakke <marius@gnu.org> wrote:
>
> 'guix package -I' only lists packages that are installed to the user
> profile. Use 'guix package -p /run/current-system/profile -I' to see
> system-installed packages.
>
>
Thanks it works
> The reason 'guix build foo' gives a different result is because you have
> not run 'guix pull', so you are using the "guix snapshot" from
> gnu/packages/package-management.scm, which is on a fixed commit.
>
> Whereas when you built the VM, you were likely using a newer version of
> Guix.
>
>
I pulled the same commit on the VM that the one obtained
with "guix describe" but it still recompiles my local
packages with "guix build". Did I forget something ?
> There are a couple of ways around this. One is to run 'make
> update-guix-package' in the Guix source tree to update the Guix
> snapshot, and use './pre-inst-env' when generating the VM. It requires
> a Guix development setup though.
>
> Another is to look at the commit that was used to generate the VM in
> /run/current-system/provenance and run 'guix pull --commit=that-commit'.
>
> Perhaps 'guix system vm-image' could learn a '--update-guix-snapshot' to
> automatically update the "system guix". Someone would have to implement
> it first though. :-)
>
>
Ok, Thanks for your help
Best regards,
Emmanuel
next prev parent reply other threads:[~2020-06-05 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 12:17 Local definitions and Virtual machine image Emmanuel Medernach
2020-06-03 15:23 ` Marius Bakke
2020-06-05 14:54 ` Emmanuel Medernach [this message]
2020-06-05 15:12 ` Emmanuel Medernach
2020-07-25 15:12 ` Marius Bakke
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=CAC_pKx8XmO2V23anxW6zcDTPXwmBtUOayGU0SxhtyKi8H75YLQ@mail.gmail.com \
--to=emmanuel.medernach@gmail.com \
--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.
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).