From: Ricardo Wurmus <rekado@elephly.net>
To: Tanguy Le Carrour <tanguy@bioneland.org>
Cc: guix-devel@gnu.org
Subject: python-distlib vs python-distlib/next
Date: Mon, 21 Jun 2021 12:32:21 +0200 [thread overview]
Message-ID: <87mtrjy0cq.fsf@mdc-berlin.de> (raw)
Hi,
commit ce6efff6eca0ed88cb9538803f5d1252c91a3b5e updated
virtualenv. As part of this change python-distlib was replaced
with python-distlib/next.
This broke the *installation* (not the build) of other packages
such as python-pygenometracks. The reason is that the closure of
python-pygenometracks would include both python-distlib and
python-distlib/next. Guix would then prevent the installation of
python-pygenometracks into user profiles:
> guix package: error: profile contains conflicting entries for
> python-distlib
> guix package: error: first entry: python-distlib@0.3.1
> /gnu/store/mypg42bass5n61liwyq7llrwla4w8bny-python-distlib-0.3.1
> guix package: error: ... propagated from
> python-virtualenv@20.2.1
> guix package: error: ... propagated from python-tox@3.20.0
> guix package: error: ... propagated from
> python-argh@0.26.2-1.dcd3253
> guix package: error: ... propagated from
> python-gffutils@0.9-1.4034c54
> guix package: error: ... propagated from
> python-pygenometracks@3.3
> guix package: error: second entry: python-distlib@0.3.0
> /gnu/store/fwya18dazamh2cjdkgh5wpxi7lqn4fcm-python-distlib-0.3.0
> guix package: error: ... propagated from
> python-sortedcontainers@2.1.0
> guix package: error: ... propagated from
> python-intervaltree@3.0.2
> guix package: error: ... propagated from
> python-pygenometracks@3.3
We can’t easily detect these problems because they only strike at
installation time. This means that we may not do partial upgrades
in the Python world due to the quirks of propagation. There may
be other packages that are broken in a similar fashion right now.
How can we make this more robust and avoid problems like this in
the future?
(I worked around this problem for pygenometracks by removing
python-tox from the propagated inputs of python-argh.)
--
Ricardo
next reply other threads:[~2021-06-21 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 10:32 Ricardo Wurmus [this message]
2021-06-21 11:17 ` python-distlib vs python-distlib/next Leo Prikler
2021-06-23 21:01 ` 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=87mtrjy0cq.fsf@mdc-berlin.de \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=tanguy@bioneland.org \
/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).