From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 53883@debbugs.gnu.org
Subject: bug#53883: strange conflicts with guix package -m manifest
Date: Wed, 16 Feb 2022 15:56:42 +0100 [thread overview]
Message-ID: <87iltex3kl.fsf@gnu.org> (raw)
In-Reply-To: <YgMZZKJZX/l+tdeb@jasmine.lan> (Leo Famulari's message of "Tue, 8 Feb 2022 20:31:16 -0500")
Hi,
Leo Famulari <leo@famulari.name> skribis:
> Basically, the python-twine package, as it is now, cannot be installed
> in a profile.
>
> That is because its dependency graph of propagated packages includes
> different versions of python-cffi, and you cannot install both of these
> cffi packages alongside each other in a symlink forest (i.e. a profile).
Any idea how this could be addressed?
There are currently 133 dependents of python-cffi@1.15 (python-cmarkgfm
is the only direct user) and 3,807 dependents of python-cffi@1.14. It’d
be easier if they all depended on 1.14.
Unfortunately we can’t just use 1.14 for python-cmarkgfm:
--8<---------------cut here---------------start------------->8---
$ guix build python-cmarkgfm --with-input=python-cffi@1.15=python-cffi@1.14
[…]
ERROR: Could not find a version that satisfies the requirement cffi>=1.15.0 (from versions: none)
ERROR: No matching distribution found for cffi>=1.15.0
--8<---------------cut here---------------end--------------->8---
Should we downgrade python-cmarkgfm, or relax its requirements? Marius,
WDYT? :-)
Ludo’.
next prev parent reply other threads:[~2022-02-16 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 21:05 bug#53883: strange conflicts with guix package -m manifest Dr. Arne Babenhauserheide
2022-02-09 1:31 ` Leo Famulari
2022-02-16 14:56 ` Ludovic Courtès [this message]
2022-02-16 22:06 ` Marius Bakke
2022-02-17 10:54 ` Ludovic Courtès
2022-02-17 15:36 ` Dr. Arne Babenhauserheide
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=87iltex3kl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=53883@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).