all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: divoplade <d@divoplade.fr>, Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 44452@debbugs.gnu.org
Subject: bug#44452: Clash between guile-3.0 and guile-3.0-latest
Date: Thu, 05 Nov 2020 16:29:02 +0100	[thread overview]
Message-ID: <86lfffg6v5.fsf@gmail.com> (raw)
In-Reply-To: <918222cbe020f41894f5c9c0d69e9d84de2d703b.camel@divoplade.fr>

Hi,

On Thu, 05 Nov 2020 at 15:48, divoplade <d@divoplade.fr> wrote:
> Le jeudi 05 novembre 2020 à 11:29 +0100, Leo Prikler a écrit :
>> guile-3.0 will presumably be updated on the next core-updates merge,
>> where world rebuilds are acceptable, so be a bit patient until then
>> and
>> use guile-3.0-latest, please :)
>
> That's not presumably, that's indeed fixed in core-updates! Sorry, I
> did not see it.

Yes.

> So it will be fixed when core-updates is merged.

And yes.


Somehow, the question are:

 1. Is it a real error for the ending  profile?
 2. If no, does the option ’--allow-collisions’ make sense here?

And ’it’ means uses ’guile-3.0’ instead of ’guile-3.0-latest’ in the
list.


All the best,
simon




  reply	other threads:[~2020-11-05 15:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04 18:47 bug#44452: Clash between guile-3.0 and guile-3.0-latest divoplade
2020-11-04 20:15 ` zimoun
2020-11-05  7:02   ` divoplade
2020-11-05  7:39   ` divoplade
2020-11-05 10:29 ` Leo Prikler
2020-11-05 14:48   ` divoplade
2020-11-05 15:29     ` zimoun [this message]
2020-11-06 10:07 ` Ludovic Courtès
2020-11-06 10:22   ` divoplade
2020-12-01 21:41     ` zimoun
2020-12-01 21:56       ` divoplade
2020-12-01 22:19         ` zimoun
2020-12-02  9:10           ` divoplade
2020-12-02 11:11             ` zimoun
2020-12-02 11:48               ` divoplade
2020-12-02 12:50                 ` zimoun

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=86lfffg6v5.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=44452@debbugs.gnu.org \
    --cc=d@divoplade.fr \
    --cc=leo.prikler@student.tugraz.at \
    /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.