[opensuse-factory] python ssl module
Why is the python ssl module not provided by the python module any more? It seems to have vanished after a recent version upgrade and there isn't even an explanation in the changelog. This currently causes build failures for offlineimap. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 06/27/2013 06:06 PM, Guido Berhoerster wrote:
Why is the python ssl module not provided by the python module any more? It seems to have vanished after a recent version upgrade and there isn't even an explanation in the changelog. This currently causes build failures for offlineimap.
Huh? saschpe@bort:packaging/openSUSE:Factory/python% rpm -qlp binaries/python-2.7.5-1.1.x86_64.rpm| grep ssl /usr/lib64/python2.7/lib-dynload/_ssl.so /usr/lib64/python2.7/ssl.py You also need to "BuildRequires: python" next to "BuildRequires: python-devel" to get access to the ssl module (same for tkinter and some more remote ones). It's not pulled in due to some bootstrapping issues. Ask Jan Matejek if you want more details or if that couldn't be solved otherwise :-) -- Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Sascha Peilicke <speilicke@suse.com> [2013-06-28 10:01]:
On 06/27/2013 06:06 PM, Guido Berhoerster wrote:
Why is the python ssl module not provided by the python module any more? It seems to have vanished after a recent version upgrade and there isn't even an explanation in the changelog. This currently causes build failures for offlineimap.
Huh?
saschpe@bort:packaging/openSUSE:Factory/python% rpm -qlp binaries/python-2.7.5-1.1.x86_64.rpm| grep ssl /usr/lib64/python2.7/lib-dynload/_ssl.so /usr/lib64/python2.7/ssl.py
You also need to "BuildRequires: python" next to "BuildRequires: python-devel" to get access to the ssl module (same for tkinter and some more remote ones). It's not pulled in due to some bootstrapping issues. Ask Jan Matejek if you want more details or if that couldn't be solved otherwise :-)
I have %py_requires which introduces a build dependency on /usr/bin/python and thus python-base and a build dependency on python-devel. The python packaging guidelines suggest "…in all cases, use BuildRequires: python-devel", and not even %py_requires -d results in a build dependency on python any more, this is confusing to say the least. Can this dependency please be added back to python-devel? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 06/28/2013 11:24 AM, Guido Berhoerster wrote:
* Sascha Peilicke <speilicke@suse.com> [2013-06-28 10:01]:
On 06/27/2013 06:06 PM, Guido Berhoerster wrote:
Why is the python ssl module not provided by the python module any more? It seems to have vanished after a recent version upgrade and there isn't even an explanation in the changelog. This currently causes build failures for offlineimap.
Huh?
saschpe@bort:packaging/openSUSE:Factory/python% rpm -qlp binaries/python-2.7.5-1.1.x86_64.rpm| grep ssl /usr/lib64/python2.7/lib-dynload/_ssl.so /usr/lib64/python2.7/ssl.py
You also need to "BuildRequires: python" next to "BuildRequires: python-devel" to get access to the ssl module (same for tkinter and some more remote ones). It's not pulled in due to some bootstrapping issues. Ask Jan Matejek if you want more details or if that couldn't be solved otherwise :-)
I have %py_requires which introduces a build dependency on /usr/bin/python and thus python-base and a build dependency on python-devel.
%py_requires isn't recommended anymore, python-devel also happens to need a python interpreter :-)
The python packaging guidelines suggest "…in all cases, use BuildRequires: python-devel", and not even %py_requires -d results in a build dependency on python any more, this is confusing to say the least.
Mhm, seems like the wiki isn't current. Could you change s/all/most/ and mention the ssl module as a special case for buildrequiring "python"?
Can this dependency please be added back to python-devel?
I can only forward this to Jan, he's the bugowner of python-base. As said, it's a bootstrapping issue workaround. @Jan: But I agree with Guide, it's probably better to build a python-mini package instead and drop the current cludge. -- Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hello, Dne 28.6.2013 11:40, Sascha Peilicke napsal(a):
You also need to "BuildRequires: python" next to "BuildRequires: python-devel" to get access to the ssl module (same for tkinter and some more remote ones). It's not pulled in due to some bootstrapping issues. Ask Jan Matejek if you want more details or if that couldn't be solved otherwise :-)
This did not change with python update; my guess is that some other component pulled in python for you and it no longer does it. BTW, my version of RPM macros says that %py_requires expands to "PreReq: python" (and maybe some version). That seems correct. Maybe the %py_requires macro changed?
Can this dependency please be added back to python-devel?
It was never there. I'll consider adding "Requires: python" to python-devel, but I must first check with autobuild people that this won't cause some badness in distro rebuild. Alternately, we could make python-base depend on openssl and include _ssl in python-base (again, provided it doesn't block the build)
I can only forward this to Jan, he's the bugowner of python-base. As said, it's a bootstrapping issue workaround. @Jan: But I agree with Guide, it's probably better to build a python-mini package instead and drop the current cludge.
I'm not sure what you want to accomplish with that. Our python-mini package is called python-base. If you need python, you require python - requiring python-base is a cheat to get built earlier. But perhaps we should start strongly advising against cheating... m. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlHNXvgACgkQjBrWA+AvBr98OACgkTWZYBsg6CUrLW0kwAAxrQet hwQAn2cXXNZra50S/nLmyI/5CtyCVxB8 =ayHf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Now the %py_requires issue bit me too. Apparently something somewhere changed. any ideas? Dne 28.6.2013 12:01, Jan Matějek napsal(a):
It was never there. I'll consider adding "Requires: python" to python-devel, but I must first check with autobuild people that this won't cause some badness in distro rebuild.
Rudi, Stephan, how about it? What would break if we made python-devel require python? (that is, building with python-devel is possible only after full python is built, with dependencies on ?dbm, Xorg, Tcl/Tk and the like) Are there potential build cycles, or do we have packages with Python C extensions that need to be built sooner than full Python? Packages that need python but don't embed it or build extensions would be unaffected. Thanks for any info. Also, i'm leaving on vacation tomorrow for two weeks. So, Sascha, if we get OK from Coolo and/or Rudi, and you want this change sooner, feel free to do it. Otherwise i'll get to it when i get back. regards m. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlHNeOIACgkQjBrWA+AvBr+KDACghE38ZLSACACXLQtiPpiEUnXK SVUAn3hrzN43WODBHT7fK2MJd+A9LRUY =E51Q -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 28.06.2013 13:52, schrieb Jan Matějek:
Now the %py_requires issue bit me too. Apparently something somewhere changed. any ideas?
Dne 28.6.2013 12:01, Jan Matějek napsal(a):
It was never there. I'll consider adding "Requires: python" to python-devel, but I must first check with autobuild people that this won't cause some badness in distro rebuild.
Rudi, Stephan, how about it? What would break if we made python-devel require python? (that is, building with python-devel is possible only after full python is built, with dependencies on ?dbm, Xorg, Tcl/Tk and the like) Are there potential build cycles, or do we have packages with Python C extensions that need to be built sooner than full Python? The build cycles can easily be work arounded if we put a #!BuildIgnore: python in those packages that turn up as cycling.
Greetings, Stephan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlHNk30ACgkQwFSBhlBjoJZIkwCg2W7yHUn+Prj9ECPHq2tyu2GF 5/gAoIcfuaj5AA7GfZqUHf+kOhvvIbdN =tLaR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Sascha Peilicke <speilicke@suse.com> [2013-06-28 11:41]:
You also need to "BuildRequires: python" next to "BuildRequires: python-devel" to get access to the ssl module (same for tkinter and some more remote ones). It's not pulled in due to some bootstrapping issues. Ask Jan Matejek if you want more details or if that couldn't be solved otherwise :-)
I have %py_requires which introduces a build dependency on /usr/bin/python and thus python-base and a build dependency on python-devel.
%py_requires isn't recommended anymore, python-devel also happens to need a python interpreter :-)
This is also still listed under "Summary of useful rpm macros", should that be removed?
The python packaging guidelines suggest "…in all cases, use BuildRequires: python-devel", and not even %py_requires -d results in a build dependency on python any more, this is confusing to say the least.
Mhm, seems like the wiki isn't current. Could you change s/all/most/ and mention the ssl module as a special case for buildrequiring "python"?
It currently says: In all cases, use BuildRequires: python-devel. Technically BuildRequires: python-base is sufficient for Python-only modules (i.e. no C code), but it increases consistency and doesn't add much overhead. How about: In all cases, use BuildRequires: python-devel. Technically BuildRequires: python-base would be sufficient for Python-only modules, i.e. modules which do not include C code, which do not use the bsddb, sqlite3 or ssl modules, however the use of python-devel ensures consitency without much additional overhead. That is, provided python-devel adds a dependency on python again.
Can this dependency please be added back to python-devel?
I can only forward this to Jan, he's the bugowner of python-base. As said, it's a bootstrapping issue workaround. @Jan: But I agree with Guide, it's probably better to build a python-mini package instead and drop the current cludge.
-- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Guido Berhoerster -
Jan Matějek -
Sascha Peilicke -
Stephan Kulow