GNU bug report logs - #44452
Clash between guile-3.0 and guile-3.0-latest

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 44452 in the body.
You can then email your comments to 44452 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: divoplade <d <at> divoplade.fr>
To: bug-guix <at> gnu.org
Subject: Clash between guile-3.0 and guile-3.0-latest
Date: Wed, 04 Nov 2020 19:47:22 +0100

Dear guix,

I cannot add the "guile-3.0" package in any system configuration (the
part that reads (packages (append (list ... %base-packages)))). When I
do that, I get:


$ LANG=C guix system docker-image config.scm 
guix system: error: profile contains conflicting entries for guile
guix system: error:   first entry: guile <at> 3.0.2
/gnu/store/18hp7flyb3yid3yp49i6qcdq0sbi5l1n-guile-3.0.2
guix system: error:   second entry: guile <at> 3.0.4
/gnu/store/ah16zr8mmfkqy23rr7jy5a842ca1q9h1-guile-3.0.4
hint: You cannot have two different versions or variants of `guile' in
the same profile.


The fix would be to deprecate guile-3.0-latest as an alias for guile-
3.0, and use the 3.0.4 version in guile-3.0.

Best regards,

divoplade

Message #8 received at 44452 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: divoplade <d <at> divoplade.fr>, 44452 <at> debbugs.gnu.org
Subject: Re: bug#44452: Clash between guile-3.0 and guile-3.0-latest
Date: Wed, 04 Nov 2020 21:15:19 +0100

Dear,

On Wed, 04 Nov 2020 at 19:47, divoplade <d <at> divoplade.fr> wrote:

> $ LANG=C guix system docker-image config.scm 
> guix system: error: profile contains conflicting entries for guile
> guix system: error:   first entry: guile <at> 3.0.2
> /gnu/store/18hp7flyb3yid3yp49i6qcdq0sbi5l1n-guile-3.0.2
> guix system: error:   second entry: guile <at> 3.0.4
> /gnu/store/ah16zr8mmfkqy23rr7jy5a842ca1q9h1-guile-3.0.4
> hint: You cannot have two different versions or variants of `guile' in
> the same profile.

Which packages ’config.scm’ contain?  Other said, what does the conflict
make happen?

I do not know if an option ’--allow-collisions’ makes sense here.


> The fix would be to deprecate guile-3.0-latest as an alias for guile-
> 3.0, and use the 3.0.4 version in guile-3.0.

I have not checked, but this proposal could lead to a world rebuild.


All the best,
simon

Message #11 received at 44452 <at> debbugs.gnu.org (full text, mbox):

From: divoplade <d <at> divoplade.fr>
To: zimoun <zimon.toutoune <at> gmail.com>, 44452 <at> debbugs.gnu.org
Subject: Re: bug#44452: Clash between guile-3.0 and guile-3.0-latest
Date: Thu, 05 Nov 2020 08:02:27 +0100

[Message part 1 (text/plain, inline)]

Hello Simon,

Le mercredi 04 novembre 2020 à 21:15 +0100, zimoun a écrit :
> Which packages ’config.scm’ contain?  Other said, what does the
> conflict
> make happen?

You can try with one of the examples of guix, if you don't want to risk
anything with your config! Here is lightweight-desktop.tmpl, and the
edited lightweight-desktop-with-guile.tmpl. 

If you run 

    guix system docker-image lightweight-desktop-with-guile.tmpl

you get the error.

If you run

    guix system docker-image lightweight-desktop.tmpl

it works.

Also, I must say that the problem also happens with any package that
has guile has a propagated input, but the root of the problem seems to
be guile.

[lightweight-desktop-with-guile.tmpl (text/plain, attachment)]

[lightweight-desktop.tmpl (text/plain, attachment)]

Message #14 received at 44452 <at> debbugs.gnu.org (full text, mbox):

From: divoplade <d <at> divoplade.fr>
To: zimoun <zimon.toutoune <at> gmail.com>, 44452 <at> debbugs.gnu.org
Subject: Re: bug#44452: Clash between guile-3.0 and guile-3.0-latest
Date: Thu, 05 Nov 2020 08:39:57 +0100

[Message part 1 (text/plain, inline)]

Le mercredi 04 novembre 2020 à 21:15 +0100, zimoun a écrit :
> > The fix would be to deprecate guile-3.0-latest as an alias for
> > guile-
> > 3.0, and use the 3.0.4 version in guile-3.0.
> 
> I have not checked, but this proposal could lead to a world rebuild.

With this fix, yes, it leads to a world rebuild, but it was marked in a
TODO anyway. I don't know if it fully solves the problem just yet,
because I'm downloading 400MB of world rebuilding with my connection at
180 KB/s, but I have good hopes!

Best regards,

divoplade

[0001-gnu-upgrade-guile-to-3.0.4.patch (text/x-patch, attachment)]

Message #17 received at 44452 <at> debbugs.gnu.org (full text, mbox):

From: Leo Prikler <leo.prikler <at> student.tugraz.at>
To: d <at> divoplade.fr
Cc: 44452 <at> debbugs.gnu.org
Subject: bug#44452: Clash between guile-3.0 and guile-3.0-latest
Date: Thu, 05 Nov 2020 11:29:20 +0100

Hi divoplade,

It is marked as a TODO exactly because it causes a world rebuild. 
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 :)
(Note, that you should also get guile-3.0-latest from specification-
>package if that is a concern.)

Regards, Leo

Message #20 received at 44452 <at> debbugs.gnu.org (full text, mbox):

From: divoplade <d <at> divoplade.fr>
To: Leo Prikler <leo.prikler <at> student.tugraz.at>
Cc: 44452 <at> debbugs.gnu.org
Subject: Re: bug#44452: Clash between guile-3.0 and guile-3.0-latest
Date: Thu, 05 Nov 2020 15:48:42 +0100

Hi!

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.

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

Message #23 received at 44452 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: divoplade <d <at> divoplade.fr>, Leo Prikler <leo.prikler <at> student.tugraz.at>
Cc: 44452 <at> debbugs.gnu.org
Subject: Re: bug#44452: Clash between guile-3.0 and guile-3.0-latest
Date: Thu, 05 Nov 2020 16:29:02 +0100

Hi,

On Thu, 05 Nov 2020 at 15:48, divoplade <d <at> 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

Message #26 received at 44452 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: divoplade <d <at> divoplade.fr>
Cc: 44452 <at> debbugs.gnu.org
Subject: Re: bug#44452: Clash between guile-3.0 and guile-3.0-latest
Date: Fri, 06 Nov 2020 11:07:09 +0100

Hi,

divoplade <d <at> divoplade.fr> skribis:

> I cannot add the "guile-3.0" package in any system configuration (the
> part that reads (packages (append (list ... %base-packages)))). When I
> do that, I get:

‘%base-packages’ already contains Guile (‘guile-3.0-latest’
specifically) so maybe you just don’t need to do anything?

HTH,
Ludo’.

Message #29 received at 44452 <at> debbugs.gnu.org (full text, mbox):

From: divoplade <d <at> divoplade.fr>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 44452 <at> debbugs.gnu.org
Subject: Re: bug#44452: Clash between guile-3.0 and guile-3.0-latest
Date: Fri, 06 Nov 2020 11:22:33 +0100

Hi!

Le vendredi 06 novembre 2020 à 11:07 +0100, Ludovic Courtès a écrit :
> ‘%base-packages’ already contains Guile (‘guile-3.0-latest’
> specifically) so maybe you just don’t need to do anything?

You're right! I just filtered out guile-3.0-latest from %base-packages
and it works!

Thank you.

divoplade

Message #32 received at 44452 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: divoplade <d <at> divoplade.fr>
Cc: 44452 <at> debbugs.gnu.org
Subject: Re: bug#44452: Clash between guile-3.0 and guile-3.0-latest
Date: Tue, 01 Dec 2020 22:41:41 +0100

Hi,

This bug #44452 is about issue with Guile declaration.

  <http://issues.guix.gnu.org/issue/44452>


On Fri, 06 Nov 2020 at 11:22, divoplade <d <at> divoplade.fr> wrote:
> Le vendredi 06 novembre 2020 à 11:07 +0100, Ludovic Courtès a écrit :

>> ‘%base-packages’ already contains Guile (‘guile-3.0-latest’
>> specifically) so maybe you just don’t need to do anything?
>
> You're right! I just filtered out guile-3.0-latest from %base-packages
> and it works!

What is the status of this bug?  I guess it can be closed, right?


All the best,
simon

Message #35 received at 44452 <at> debbugs.gnu.org (full text, mbox):

From: divoplade <d <at> divoplade.fr>
To: zimoun <zimon.toutoune <at> gmail.com>
Cc: 44452 <at> debbugs.gnu.org
Subject: Re: bug#44452: Clash between guile-3.0 and guile-3.0-latest
Date: Tue, 01 Dec 2020 22:56:55 +0100

Hello,

Le mardi 01 décembre 2020 à 22:41 +0100, zimoun a écrit :
> > > ‘%base-packages’ already contains Guile (‘guile-3.0-latest’
> > > specifically) so maybe you just don’t need to do anything?
> > 
> > You're right! I just filtered out guile-3.0-latest from %base-
> > packages
> > and it works!
> 
> What is the status of this bug?  I guess it can be closed, right?

The problem is there until core-updates is merged. The workaround that
I use appears to work, but I guess it's not something that is intended.

I hope it makes things a little clearer ^^

Message #38 received at 44452 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: divoplade <d <at> divoplade.fr>
Cc: 44452 <at> debbugs.gnu.org
Subject: Re: bug#44452: Clash between guile-3.0 and guile-3.0-latest
Date: Tue, 01 Dec 2020 23:19:35 +0100

Hi,

On Tue, 01 Dec 2020 at 22:56, divoplade <d <at> divoplade.fr> wrote:

> The problem is there until core-updates is merged. The workaround that
> I use appears to work, but I guess it's not something that is intended.

If the problem is fixed in core-updates, then the problem is fixed.  :-)
No need to wait the merge to close this bug.  IMHO.

Moreover, %base-packages already contains Guile (’guile-3.0-latest’),
therefore I am not sure to understand what the bug is about
specifically.  As I said, I do not know if an option
’--allow-collisions’ makes sense here.

Anyway, please do not forget to close it. ;-)

Cheers,
simon

Message #41 received at 44452 <at> debbugs.gnu.org (full text, mbox):

From: divoplade <d <at> divoplade.fr>
To: zimoun <zimon.toutoune <at> gmail.com>
Cc: 44452 <at> debbugs.gnu.org
Subject: Re: bug#44452: Clash between guile-3.0 and guile-3.0-latest
Date: Wed, 02 Dec 2020 10:10:58 +0100

Le mardi 01 décembre 2020 à 23:19 +0100, zimoun a écrit :
> Moreover, %base-packages already contains Guile (’guile-3.0-latest’),
> therefore I am not sure to understand what the bug is about
> specifically.

That's the problem. I need to remove it from %base-packages, otherwise
the packages that propagate guile 3.0.2 can't be installed.

Message #44 received at 44452 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: divoplade <d <at> divoplade.fr>
Cc: 44452 <at> debbugs.gnu.org
Subject: Re: bug#44452: Clash between guile-3.0 and guile-3.0-latest
Date: Wed, 02 Dec 2020 12:11:12 +0100

Hi,

On Wed, 02 Dec 2020 at 10:10, divoplade <d <at> divoplade.fr> wrote:
> Le mardi 01 décembre 2020 à 23:19 +0100, zimoun a écrit :
>> Moreover, %base-packages already contains Guile (’guile-3.0-latest’),
>> therefore I am not sure to understand what the bug is about
>> specifically.
>
> That's the problem. I need to remove it from %base-packages, otherwise
> the packages that propagate guile 3.0.2 can't be installed.

Sorry if I am slow, but I do not see why this use-case should be a bug.
For example,

--8<---------------cut here---------------start------------->8---
$ cat /tmp/manif.scm
(use-modules (gnu packages guile))
(packages->manifest
 (list
  guile-3.0-latest
  guile-3.0))

$ guix package -m /tmp/manif.scm -p /tmp/bug
The following packages will be installed:
   guile 3.0.2
   guile 3.0.4

guix package: error: profile contains conflicting entries for guile
guix package: error:   first entry: guile <at> 3.0.4 /gnu/store/ah16zr8mmfkqy23rr7jy5a842ca1q9h1-guile-3.0.4
guix package: error:   second entry: guile <at> 3.0.2 /gnu/store/18hp7flyb3yid3yp49i6qcdq0sbi5l1n-guile-3.0.2
hint: You cannot have two different versions or variants of `guile' in the same profile.
--8<---------------cut here---------------end--------------->8---

And this appends for any package providing multiversions (gcc, clang,
guile, etc.).  From my understanding, it is a feature. :-)

Using the option ’--allow-collisions’ avoids the error but then the
version you get is the first in the list, which could be prone error.
That’s why I am not convinced it makes sense here.

Said explicitly, if you do not want in your profile the package X
belonging to %base-packages , do not add the %base-packages list. :-) Or
create your custom list (remove the ones you do not want). I do not see
what could done on this side.  The list %base-packages is 40 packages
considered as “kind of minimal” to be able to do minimal stuff.


In one of your message, you were speaking about propagated inputs.
Which is the use-case for the option ’--allow-collisions’, IIUC.  Do you
have examples of such use-cases?  Something where:

--8<---------------cut here---------------start------------->8---
    (packages (append (list
                      pkg-1
                      pkg-2
                      …
                      %base-packages))
--8<---------------cut here---------------end--------------->8---

leads to an error or an unexpected result?


All the best,
simon

Message #47 received at 44452 <at> debbugs.gnu.org (full text, mbox):

From: divoplade <d <at> divoplade.fr>
To: zimoun <zimon.toutoune <at> gmail.com>
Cc: 44452 <at> debbugs.gnu.org
Subject: Re: bug#44452: Clash between guile-3.0 and guile-3.0-latest
Date: Wed, 02 Dec 2020 12:48:38 +0100

Le mercredi 02 décembre 2020 à 12:11 +0100, zimoun a écrit :
> Said explicitly, if you do not want in your profile the package X
> belonging to %base-packages , do not add the %base-packages list. :-) 
> Or
> create your custom list (remove the ones you do not want). I do not
> see
> what could done on this side.  The list %base-packages is 40 packages
> considered as “kind of minimal” to be able to do minimal stuff.

I would disagree on that, it contains guile 3.0.4 instead of 3.0.2.
3.0.4 is not used, and prevents the other guile packages that require
3.0.2. If it contained 3.0.2 instead, I would 100% agree with what you
said there.

But it is fixed in core-updates, so we just need to wait for core-
updates to be merged.

Message #50 received at 44452 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: divoplade <d <at> divoplade.fr>
Cc: 44452 <at> debbugs.gnu.org
Subject: Re: bug#44452: Clash between guile-3.0 and guile-3.0-latest
Date: Wed, 02 Dec 2020 13:50:30 +0100

On Wed, 02 Dec 2020 at 12:48, divoplade <d <at> divoplade.fr> wrote:
> Le mercredi 02 décembre 2020 à 12:11 +0100, zimoun a écrit :
>> Said explicitly, if you do not want in your profile the package X
>> belonging to %base-packages , do not add the %base-packages list. :-) 
>> Or
>> create your custom list (remove the ones you do not want). I do not
>> see
>> what could done on this side.  The list %base-packages is 40 packages
>> considered as “kind of minimal” to be able to do minimal stuff.
>
> I would disagree on that, it contains guile 3.0.4 instead of 3.0.2.
> 3.0.4 is not used, and prevents the other guile packages that require
> 3.0.2. If it contained 3.0.2 instead, I would 100% agree with what you
> said there.

Again, sorry to be slow.  But I really try to understand. :-) I have
been annoyed by such things about different Guile with the website [1].

What I get with 353bdae (pre-1.2) or f4450e8 (post-1.2):

--8<---------------cut here---------------start------------->8---
$ guix install guile -p /tmp/guile
The following package will be installed:
   guile 3.0.4
--8<---------------cut here---------------end--------------->8---

so why are you are saying 3.0.4 is not used when it is the default?


Well, if I understand correctly, your point is the inconsistency between
the default Guile (3.0-latest, i.e., currently 3.0.4) and the Guile
(3.0, i.e., currently 3.0.2) used by most packages in guile-xyz.scm,
especially when there is bytecode difference.  Right?


1:<https://git.savannah.gnu.org/cgit/guix/guix-artwork.git/commit/?id=05e384e811ab58f8d7f37ab92cf9dac416317af5>


All the best,
simon

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.