unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Diego Nicola Barbato <dnbarbato@posteo.de>
Cc: 27572@debbugs.gnu.org
Subject: bug#27572: simultaneous installation of python2 and python3 fails
Date: Fri, 07 Jul 2017 13:27:01 +0200	[thread overview]
Message-ID: <87tw2obi7u.fsf@gnu.org> (raw)
In-Reply-To: <877ezoivqd.fsf@GlaDOS.home> (Diego Nicola Barbato's message of "Tue, 04 Jul 2017 08:04:10 +0200")

Hello Diego,

Diego Nicola Barbato <dnbarbato@posteo.de> skribis:

> When running the command "guix pull && guix package -i python@2 python"
> instead of installing the latest version of python2 and python3, as it
> used to do until about four weeks ago, guix gives following error
> message (hash values replaced with ...):
>
>   guix package: error: profile contains conflicting entries for python:out
>   guix package: error:   first entry: python@2.7.13:out /gnu/store/...-python-2.7.13
>   guix package: error:   second entry: python@3.5.3:out /gnu/store/...-python-3.5.3

Indeed, Guix now refuses to install two different versions or variants
of the same package since in general they would conflict.

In this particular case, they do not actually conflict, I think, since
python@3 provides executables prefixed by “3” whereas python@2 does not.

Perhaps we should rename “python” to “python2” or something like that?

In the meantime, I recommend using separate profiles for your Python 2
and Python 3 development environments.  Is that a viable option for you?

Thanks,
Ludo’.

  reply	other threads:[~2017-07-07 11:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04  6:04 bug#27572: simultaneous installation of python2 and python3 fails Diego Nicola Barbato
2017-07-07 11:27 ` Ludovic Courtès [this message]
2017-07-10 15:59   ` Diego Nicola Barbato
2017-07-11  9:29     ` 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

  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=87tw2obi7u.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=27572@debbugs.gnu.org \
    --cc=dnbarbato@posteo.de \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).