From: bo0od <bo0od@riseup.net>
To: Leo Famulari <leo@famulari.name>
Cc: 48166@debbugs.gnu.org
Subject: bug#48166: Dont stop the upgrade process - Better guix handling when Package failed to build
Date: Mon, 3 May 2021 01:00:02 +0000 [thread overview]
Message-ID: <e0b306c2-82bb-438f-cb30-3f9e064e2d96@riseup.net> (raw)
In-Reply-To: <YI8R2C/i+QRKfGI+@jasmine.lan>
> I think you can use `guix package --upgrade . --keep-going`:
Thank you for the hint, sorry i didnt know this command exist.
Currently i cant test this because i dont have a package which has an
error in the building (previous icedove bug should be fixed) to see how
this is going to go.
- First question:
Why this is not default? and what not default should be:
--stop-at-error or --dont-proceed-error ..(or whatever)
- Second question:
Does it show the error at the end or during the upgrade or both (same as
my example before)? So user is aware that one or more of his packages
didnt upgraded.
- If second question is yes then that command can replace
--do-not-upgrade in my previous workaround faster implementation but not
ultimate.
Leo Famulari:
> On Sun, May 02, 2021 at 08:29:31PM +0000, bo0od wrote:
>> Current (manual) solution is:
>>
>> guix package --upgrade . --do-not-upgrade x
>
> I think you can use `guix package --upgrade . --keep-going`:
>
> https://guix.gnu.org/manual/devel/en/html_node/Common-Build-Options.html
>
> --keep-going
> -k
>
> Keep going when some of the derivations fail to build; return only once all the builds have either completed or failed.
>
> The default behavior is to stop as soon as one of the specified derivations has failed.
>
next prev parent reply other threads:[~2021-05-03 1:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 20:29 bug#48166: Dont stop the upgrade process - Better guix handling when Package failed to build bo0od
2021-05-02 20:55 ` Leo Famulari
2021-05-03 1:00 ` bo0od [this message]
2021-05-03 1:50 ` Julien Lepiller
2021-05-03 2:25 ` bo0od
2021-05-04 19:57 ` Ludovic Courtès
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=e0b306c2-82bb-438f-cb30-3f9e064e2d96@riseup.net \
--to=bo0od@riseup.net \
--cc=48166@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.