all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Andy Tai <atai@atai.org>
Cc: help-guix@gnu.org
Subject: Re: two questions on guix upgrade
Date: Tue, 16 Mar 2021 16:43:24 -0400	[thread overview]
Message-ID: <YFEYbL+JVYUA5HRu@jasmine.lan> (raw)
In-Reply-To: <CAJsg1E-rcvYobTrQxpjVS=1ROW9A1RLR-B10vyVA=f=waqawZQ@mail.gmail.com>

On Tue, Mar 16, 2021 at 12:47:33PM -0700, Andy Tai wrote:
> 1. Is there a way to tolerate errors in single package upgrade and keep the
> others going?   right now I have opencv installed and opencv build now is
> broken, so if I do the above command as is the whole 'package -u' command
> would fail unless I explicitly exclude opencv from the update step.

You can use the --keep-going or --do-not-upgrade options, depending on
your needs.

> 2. is there a way to exclude packages that require local build?  I use a VM
> with just 4 Gb of RAM running the guix distribution and the above command
> may fail when upgrading and certain packages with no substitutes yet
> available would be build locally and because of the low amount of RAM the
> build steps would fail, again making the whole command fail.   It would be
> ideal to have an option to just skip packages that would be built locally.

No, sorry, this isn't possible (yet?). Guix is a build-from-source
distro with transparent substitution of precompiled binaries, so it's
not simple to "only substitute".

You can use the `guix weather` command to check in advance which
substitute are available, and then use --do-not-upgrade accordingly.


  reply	other threads:[~2021-03-16 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 19:47 two questions on guix upgrade Andy Tai
2021-03-16 20:43 ` Leo Famulari [this message]
2021-03-16 21:19 ` Andreas Enge

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=YFEYbL+JVYUA5HRu@jasmine.lan \
    --to=leo@famulari.name \
    --cc=atai@atai.org \
    --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.