From: sirgazil <sirgazil@zoho.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel <guix-devel@gnu.org>, help-guix <help-guix@gnu.org>
Subject: Re: core-updates call for testing
Date: Fri, 24 Apr 2020 22:42:13 +0000 [thread overview]
Message-ID: <171ae5b0793.1037b179f7366.8411228349326377247@zoho.com> (raw)
In-Reply-To: <87zhb0eekp.fsf@devup.no>
---- On Fri, 24 Apr 2020 21:52:54 +0000 Marius Bakke <mbakke@fastmail.com> wrote ----
> sirgazil <sirgazil@zoho.com> writes:
>
> > This time, one of my packages in a custom channel failed with "no code for (term ansi-color)" (the package definition: https://gitlab.com/sirgazil/guix-channel-x/-/blob/master/sirgazil-x/packages/guile.scm#L13). This is not a new package in my profile, I've been using it for a long time. Since both error seemed to be related to Guile, I removed all Guile-related packages from my profile and tried upgrading again. This time, the upgrade succeeded.
>
> The reason your custom package failed is because it is using guile-2.2,
> but the dependencies are built with Guile 3.0.
Thanks, I will do that.
next prev parent reply other threads:[~2020-04-24 22:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 23:24 core-updates call for testing Marius Bakke
2020-04-24 3:20 ` sirgazil
2020-04-24 12:58 ` sirgazil
2020-04-24 16:25 ` Marius Bakke
2020-04-24 16:54 ` Gábor Boskovits
2020-04-24 19:29 ` sirgazil
2020-04-24 18:08 ` sirgazil
2020-04-24 21:52 ` Marius Bakke
2020-04-24 22:42 ` sirgazil [this message]
2020-04-24 18:46 ` sirgazil
2020-04-24 14:40 ` Jack Hill
2020-04-24 20:06 ` Jack Hill
2020-04-25 3:02 ` Jack Hill
2020-04-25 13:24 ` sirgazil
2020-04-25 18:13 ` sirgazil
2020-04-29 11:31 ` Ricardo Wurmus
2020-04-25 18:36 ` sirgazil
2020-04-25 21:19 ` Jack Hill
2020-04-25 21:54 ` sirgazil
2020-04-27 22:09 ` Jack Hill
2020-04-29 6:17 ` Ricardo Wurmus
2020-04-25 18:06 ` Leo Famulari
2020-04-28 13:17 ` Marius Bakke
2020-04-28 12:46 ` Efraim Flashner
2020-04-28 13:12 ` Marius Bakke
2020-05-04 14:51 ` Timothy Sample
2020-05-04 15:32 ` 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=171ae5b0793.1037b179f7366.8411228349326377247@zoho.com \
--to=sirgazil@zoho.com \
--cc=guix-devel@gnu.org \
--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).