From: Leo Famulari <leo@famulari.name>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Ricardo Wurmus <rekado@elephly.net>, 52906@debbugs.gnu.org
Subject: bug#52906: python-biopython conflicts with python-numpy
Date: Thu, 30 Dec 2021 18:55:19 -0500 [thread overview]
Message-ID: <Yc5G5xmpO0Z/5fKR@jasmine.lan> (raw)
In-Reply-To: <86o84xpzhv.fsf@gmail.com>
On Thu, Dec 30, 2021 at 10:13:48PM +0100, zimoun wrote:
> $ guix package -m /tmp/manifest.scm -p /tmp/fail
> The following packages will be installed:
> python-biopython 1.76
> python-numpy 1.21.3
>
> guix package: error: profile contains conflicting entries for python-numpy
> guix package: error: first entry: python-numpy@1.21.3 /gnu/store/ggrkk9l67fjn1cj7alr8vx40xv08a6h0-python-numpy-1.21.3
> guix package: error: second entry: python-numpy@1.20.3 /gnu/store/wgsmkn68q8h178sqc7ywjcdr330z9rb6-python-numpy-1.20.3
> guix package: error: ... propagated from python-biopython@1.76
> hint: Try upgrading both `python-numpy' and `python-biopython', or remove one of
> them from the profile.
> --8<---------------cut here---------------end--------------->8---
See also <https://issues.guix.gnu.org/52859>,
"tests/guix-pack-relocatable fails / numpy propagation collision".
> I propose to refer as name “python-numpy” the symbol python-numpy which
> leads to a consistent scientific Python stack. And to refer as name
> “python-numpy-next” the symbol python-numpy-next.
Agreed, the stack should be kept consistent.
next prev parent reply other threads:[~2021-12-30 23:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 21:13 bug#52906: python-biopython conflicts with python-numpy zimoun
2021-12-30 23:55 ` Leo Famulari [this message]
2021-12-31 10:14 ` Ricardo Wurmus
2021-12-31 10:51 ` zimoun
2021-12-31 12:43 ` Ricardo Wurmus
2021-12-31 13:16 ` zimoun
2021-12-31 20:18 ` Ricardo Wurmus
2021-12-31 12:50 ` Ricardo Wurmus
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=Yc5G5xmpO0Z/5fKR@jasmine.lan \
--to=leo@famulari.name \
--cc=52906@debbugs.gnu.org \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@gmail.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.
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).