From: Leo Famulari <leo@famulari.name>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Python2-jsonschema fails
Date: Mon, 18 Jan 2016 17:46:00 -0500 [thread overview]
Message-ID: <20160118224600.GA5918@jasmine> (raw)
In-Reply-To: <20160118150334.GA9800@debian.eduroam.u-bordeaux.fr>
On Mon, Jan 18, 2016 at 04:03:34PM +0100, Andreas Enge wrote:
> On Mon, Jan 18, 2016 at 03:53:05PM +0100, Cyril Roelandt wrote:
> > Yes, a bunch of packages will have to be rebuilt, but there is nothing
> > we can do about this, I'm afraid.
>
> I think what Efraim meant was that package-with-python2 does not work when
> dealing with packages depending on python2-jsonschema. They will then not
> depend on python2-jsonschema (built with python2-functools32), but on the
> recursively rewritten (package-with-python2 python-jsonschema), which does
> not include python2-functools32 in its inputs. We already have this rather
> unpleasant problem around the numpy/matplotlib universe.
Shall we open a bug for this? It was discussed in #22013 [0] but that
specific issue was solved and the bug was closed in expectation of a
more general bug report.
>
> A cheating workaround would be to also add python-functools32 to the inputs
> of python-jsonschema, assuming that it would be superfluous, but not
> impossible, that is, not creating a conflict.
This "solution" is already in place throughout python.scm. I don't think
that python-setuptools is really required for many of the python-3
packages that call it as a native-input, but it eases the python-2
translation.
[0]
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22013
>
> Andreas
>
>
next prev parent reply other threads:[~2016-01-18 22:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 10:15 Python2-jsonschema fails Andreas Enge
2016-01-18 12:55 ` Cyril Roelandt
2016-01-18 14:41 ` Efraim Flashner
2016-01-18 14:53 ` Cyril Roelandt
2016-01-18 15:03 ` Andreas Enge
2016-01-18 22:46 ` Leo Famulari [this message]
2016-01-19 8:47 ` Andreas Enge
2016-01-19 9:00 ` Ludovic Courtès
2016-01-18 15:52 ` Efraim Flashner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160118224600.GA5918@jasmine \
--to=leo@famulari.name \
--cc=andreas@enge.fr \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.