From: Leo Famulari <leo@famulari.name>
To: 22437@debbugs.gnu.org
Subject: bug#22437: Problems with non-auto-translated python-2 package variants
Date: Fri, 22 Jan 2016 14:52:42 -0500 [thread overview]
Message-ID: <20160122195242.GA26196@jasmine> (raw)
Python-2 variants of python-3 packages that are not automatically
translated by package-with-python2 are not used by auto-translated
python-2 packages.
For example, python2-cryptography requires python2-ipaddress. This is
not required by python-cryptography:
http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/python.scm#n5838
Python-oauthlib requires python-cryptography, and thus cannot be
translated wholly by package-with-python2. Package-with-python2 fails to
refer to the "hand-made" python2-cryptography that includes
python2-ipaddress, and insteads attempts to generate it automatically.
This results in a failed build of python2-cryptopgraphy because
python2-ipaddress is not being provided. The solution is to remove
python-cryptography from python2-oauthlib and provide
python2-cryptography "by hand":
http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/python.scm#n2333
This is especially annoying when a python-2 variant needs to refer to
more than one of these "hand-made" python-2 packages:
http://lists.gnu.org/archive/html/guix-devel/2015-12/msg00921.html
There are many python-3 packages that include python-setuptools, even
though they build without it. I assume this is to easily take advantage
of package-with-python2.
Some context:
bug: python2 versions of packages failing as inputs
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22013
guix-devel: Python2-jsonschema fails:
http://lists.gnu.org/archive/html/guix-devel/2016-01/msg00604.html
guix-devel: Split acme into both Python variants
http://lists.gnu.org/archive/html/guix-devel/2015-12/msg00921.html
reply other threads:[~2016-01-22 19:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160122195242.GA26196@jasmine \
--to=leo@famulari.name \
--cc=22437@debbugs.gnu.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).