From: Luis Felipe <sirgazil@zoho.com>
To: Fenix Lopez <jordila@librebits.info>, help-guix@gnu.org
Subject: Re: Guix home - 'pinning' ?
Date: Tue, 13 Jun 2023 20:02:16 +0000 [thread overview]
Message-ID: <bba0a7d9-514c-b5d6-b8cc-b0f43bf37273@zoho.com> (raw)
In-Reply-To: <f90aa32f-5e79-bc58-d5de-d70154a5d30e@librebits.info>
[-- Attachment #1.1.1: Type: text/plain, Size: 797 bytes --]
Hi Fenix,
El 13/06/23 a las 15:06, Fenix Lopez escribió:
> In order to give some more context , may i add the fact that the
> package in question is not being compiled/derived when entering the
> build phase ? In consquence, the whole 'guix home reconfigure' gets
> stopped...
>
> That's the underlaying reason why i was wondering how to pin that
> 'offending' package.
>
> Umh... leaving package version 'pinning' aside, umh... Is there
> another way to prevent such described scenario ? how to get ' guix
> home reconfigure'
>
> finish the whole process regardless the issue described ?
If I understand correctly, you could add the following option to "guix
home reconfigure":
-k, --keep-going keep going when some of the derivations fail
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2881 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
prev parent reply other threads:[~2023-06-13 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 22:08 Guix home - 'pinning' ? jordila
2023-06-12 16:16 ` Robby Zambito
2023-06-13 15:06 ` Fenix Lopez
2023-06-13 20:02 ` Luis Felipe [this message]
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=bba0a7d9-514c-b5d6-b8cc-b0f43bf37273@zoho.com \
--to=sirgazil@zoho.com \
--cc=help-guix@gnu.org \
--cc=jordila@librebits.info \
/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).