Opensuse15.5: unresolvable: nothing provides python311-cffi, nothing provides python311-cryptography
All, The python packaging guidelines call for getting opensuse 15.5 packages to build with python 3.11 I've got roughly 50 packages that use python in security:forensics. Most using the 15.5 repo now build a python311 RPM. But a couple are complaining because python311-cffi.and python311-cryptography packages aren't available in devel:languages:python or devel:languages:python:pytest Can someone take a look and fix those to packages to follow the packaging guidelines? Thanks, Greg
I mean, there's nothing to fix. That's the way it's meant to be. If a python package is built in the repos for 15.5, then these are always python311 packages. So you still have to include devel:languages:Python. I think that's unfortunate too, but I guess that's how it was introduced. Since there were still quite a few packages missing at the beginning, I have a separate Python repo in my home repo. In the meantime there are about 800 packages. It doesn't necessarily make sense to me, but ...... Regards Eric Am 2. August 2023 05:11:18 MESZ schrieb Greg Freemyer <greg.freemyer@gmail.com>:
All,
The python packaging guidelines call for getting opensuse 15.5 packages to build with python 3.11
I've got roughly 50 packages that use python in security:forensics.
Most using the 15.5 repo now build a python311 RPM.
But a couple are complaining because python311-cffi.and python311-cryptography packages aren't available in devel:languages:python or devel:languages:python:pytest
Can someone take a look and fix those to packages to follow the packaging guidelines?
Thanks, Greg
On Wed, Aug 2, 2023 at 10:24 AM Eric Schirra <ecsos@opensuse.org> wrote:
I mean, there's nothing to fix. That's the way it's meant to be. If a python package is built in the repos for 15.5, then these are always python311 packages. So you still have to include devel:languages:Python.
You probably misunderstood the problem. He does include devel:languages:python and devel:languages:python:pytest in his project, but there are some packages that failed to build there. Take as an example python-cffi from security:forensics. It fails to build due to missing prerequisites, one of them is python311-py. devel:languages:python:pytest/python-py in turn fails to build due to missing prerequisites again. One of them is devel:languages:python:pytest/python-apipkg. Which itself fails to build due to missing python311-wheel (and others). Now, python-wheel *is* successfully built in devel:languages:python for Leap 15.5, but devel:languages:python:pytest does not include devel:languages:python in its repository path. The question is why? So the problem is inside of devel:languages:python repositories.
I think that's unfortunate too, but I guess that's how it was introduced. Since there were still quite a few packages missing at the beginning, I have a separate Python repo in my home repo. In the meantime there are about 800 packages. It doesn't necessarily make sense to me, but ......
Regards Eric
Am 2. August 2023 05:11:18 MESZ schrieb Greg Freemyer <greg.freemyer@gmail.com>:
All,
The python packaging guidelines call for getting opensuse 15.5 packages to build with python 3.11
I've got roughly 50 packages that use python in security:forensics.
Most using the 15.5 repo now build a python311 RPM.
But a couple are complaining because python311-cffi.and python311-cryptography packages aren't available in devel:languages:python or devel:languages:python:pytest
Can someone take a look and fix those to packages to follow the packaging guidelines?
Thanks, Greg
That's what I'm saying. Not all packages have the new macro in them and are therefore not built as 311s. And I also said that I find your solution "unfortunate". And I said I have my own repo. You have to include all repos in your repo. And you have to check if the macro is already everywhere. And then you have to deal with people who don't want the new macro. That's why you have your own repo. Everyone has to do it for themselves. Bullshit, but that's the way it's meant to be. And why some Python packages are scattered around.... Regards Eric Am 2. August 2023 09:49:38 MESZ schrieb Andrei Borzenkov <arvidjaar@gmail.com>:
On Wed, Aug 2, 2023 at 10:24 AM Eric Schirra <ecsos@opensuse.org> wrote:
I mean, there's nothing to fix. That's the way it's meant to be. If a python package is built in the repos for 15.5, then these are always python311 packages. So you still have to include devel:languages:Python.
You probably misunderstood the problem.
He does include devel:languages:python and devel:languages:python:pytest in his project, but there are some packages that failed to build there.
Take as an example python-cffi from security:forensics. It fails to build due to missing prerequisites, one of them is python311-py.
devel:languages:python:pytest/python-py in turn fails to build due to missing prerequisites again. One of them is devel:languages:python:pytest/python-apipkg. Which itself fails to build due to missing python311-wheel (and others).
Now, python-wheel *is* successfully built in devel:languages:python for Leap 15.5, but devel:languages:python:pytest does not include devel:languages:python in its repository path. The question is why?
So the problem is inside of devel:languages:python repositories.
I think that's unfortunate too, but I guess that's how it was introduced. Since there were still quite a few packages missing at the beginning, I have a separate Python repo in my home repo. In the meantime there are about 800 packages. It doesn't necessarily make sense to me, but ......
Regards Eric
Am 2. August 2023 05:11:18 MESZ schrieb Greg Freemyer <greg.freemyer@gmail.com>:
All,
The python packaging guidelines call for getting opensuse 15.5 packages to build with python 3.11
I've got roughly 50 packages that use python in security:forensics.
Most using the 15.5 repo now build a python311 RPM.
But a couple are complaining because python311-cffi.and python311-cryptography packages aren't available in devel:languages:python or devel:languages:python:pytest
Can someone take a look and fix those to packages to follow the packaging guidelines?
Thanks, Greg
I want to formally request that the devel:languages:python:pytest opensuse15.5 repo have the devel:languages:python repo added to the path list. That requires no changes to any spec files. How do I make that request? Thanks, Greg On Wed, Aug 2, 2023 at 6:03 AM Eric Schirra <ecsos@opensuse.org> wrote:
That's what I'm saying. Not all packages have the new macro in them and are therefore not built as 311s. And I also said that I find your solution "unfortunate". And I said I have my own repo. You have to include all repos in your repo. And you have to check if the macro is already everywhere. And then you have to deal with people who don't want the new macro. That's why you have your own repo. Everyone has to do it for themselves. Bullshit, but that's the way it's meant to be. And why some Python packages are scattered around....
Regards Eric
Am 2. August 2023 09:49:38 MESZ schrieb Andrei Borzenkov <arvidjaar@gmail.com>:
On Wed, Aug 2, 2023 at 10:24 AM Eric Schirra <ecsos@opensuse.org> wrote:
I mean, there's nothing to fix. That's the way it's meant to be. If a python package is built in the repos for 15.5, then these are always python311 packages. So you still have to include devel:languages:Python.
You probably misunderstood the problem.
He does include devel:languages:python and devel:languages:python:pytest in his project, but there are some packages that failed to build there.
Take as an example python-cffi from security:forensics. It fails to build due to missing prerequisites, one of them is python311-py.
devel:languages:python:pytest/python-py in turn fails to build due to missing prerequisites again. One of them is devel:languages:python:pytest/python-apipkg. Which itself fails to build due to missing python311-wheel (and others).
Now, python-wheel *is* successfully built in devel:languages:python for Leap 15.5, but devel:languages:python:pytest does not include devel:languages:python in its repository path. The question is why?
So the problem is inside of devel:languages:python repositories.
I think that's unfortunate too, but I guess that's how it was introduced. Since there were still quite a few packages missing at the beginning, I have a separate Python repo in my home repo. In the meantime there are about 800 packages. It doesn't necessarily make sense to me, but ......
Regards Eric
Am 2. August 2023 05:11:18 MESZ schrieb Greg Freemyer <greg.freemyer@gmail.com>:
All,
The python packaging guidelines call for getting opensuse 15.5 packages to build with python 3.11
I've got roughly 50 packages that use python in security:forensics.
Most using the 15.5 repo now build a python311 RPM.
But a couple are complaining because python311-cffi.and python311-cryptography packages aren't available in devel:languages:python or devel:languages:python:pytest
Can someone take a look and fix those to packages to follow the packaging guidelines?
Thanks, Greg
Am 02.08.23 um 07:44 schrieb Greg Freemyer:
I want to formally request that the devel:languages:python:pytest opensuse15.5 repo have the devel:languages:python repo added to the path list.
That requires no changes to any spec files.
How do I make that request?
You would ask the maintainers of devel:languages:python:pytest, maybe addtionally post on python@lists.opensuse.org. https://build.opensuse.org/project/users/devel:languages:python:pytest But where does it lead to? You will need the same for every devel project. There are more python packages than just d:l:p and d:l:p:pytest. :numeric is one. Several packages are outside of the d:l:p tree even. As already mentioned, I'd recommend to switch to devel:languages:python:backports in your project path instead and help fixing the unresolvables by submitting SRs to the respective packages in their devel repo so that they propagate through Factory to :backports.
Thanks, Greg
- Ben
On Wed, Aug 2, 2023 at 11:39 AM Ben Greiner <code@bnavigator.de> wrote:
Am 02.08.23 um 07:44 schrieb Greg Freemyer:
I want to formally request that the devel:languages:python:pytest opensuse15.5 repo have the devel:languages:python repo added to the path list.
That requires no changes to any spec files.
How do I make that request?
You would ask the maintainers of devel:languages:python:pytest, maybe addtionally post on python@lists.opensuse.org.
https://build.opensuse.org/project/users/devel:languages:python:pytest
But where does it lead to? You will need the same for every devel project. There are more python packages than just d:l:p and d:l:p:pytest. :numeric is one. Several packages are outside of the d:l:p tree even.
As already mentioned, I'd recommend to switch to devel:languages:python:backports in your project path instead and help fixing the unresolvables by submitting SRs to the respective packages in their devel repo so that they propagate through Factory to :backports.
I've just changed the security:forensics 15.5 repo to only have devel:languages:python:backports in addition to the main repo. 100 packages are now in the build queue. I check in a while and see how far it gets. Thanks, Greg
Hm. I would ask a project manager. But you still have to add the new macro to the spec if it is still missing. Usually the packages in d:l:p are too new to be built for python36. They have to be built with python311. This is what the macro does. And devel:languages:python:Backports should not work, because the packages in it are python36 modules. So they are too old for many current Python programs. Example: calibre, certbot, matrix-synapse and so on. In my personal opinion, the dead Python versions < 3.8 should be deleted completely. And all applications that do not work with Python >= 3.8 should be deleted as well. And Python modules and applications should be offered in the same way as Tumbleweed. Regards Eric Am 2. August 2023 16:44:24 MESZ schrieb Greg Freemyer <greg.freemyer@gmail.com>:
I want to formally request that the devel:languages:python:pytest opensuse15.5 repo have the devel:languages:python repo added to the path list.
That requires no changes to any spec files.
How do I make that request?
Thanks, Greg
On Wed, Aug 2, 2023 at 6:03 AM Eric Schirra <ecsos@opensuse.org> wrote:
That's what I'm saying. Not all packages have the new macro in them and are therefore not built as 311s. And I also said that I find your solution "unfortunate". And I said I have my own repo. You have to include all repos in your repo. And you have to check if the macro is already everywhere. And then you have to deal with people who don't want the new macro. That's why you have your own repo. Everyone has to do it for themselves. Bullshit, but that's the way it's meant to be. And why some Python packages are scattered around....
Regards Eric
Am 2. August 2023 09:49:38 MESZ schrieb Andrei Borzenkov <arvidjaar@gmail.com>:
On Wed, Aug 2, 2023 at 10:24 AM Eric Schirra <ecsos@opensuse.org> wrote:
I mean, there's nothing to fix. That's the way it's meant to be. If a python package is built in the repos for 15.5, then these are always python311 packages. So you still have to include devel:languages:Python.
You probably misunderstood the problem.
He does include devel:languages:python and devel:languages:python:pytest in his project, but there are some packages that failed to build there.
Take as an example python-cffi from security:forensics. It fails to build due to missing prerequisites, one of them is python311-py.
devel:languages:python:pytest/python-py in turn fails to build due to missing prerequisites again. One of them is devel:languages:python:pytest/python-apipkg. Which itself fails to build due to missing python311-wheel (and others).
Now, python-wheel *is* successfully built in devel:languages:python for Leap 15.5, but devel:languages:python:pytest does not include devel:languages:python in its repository path. The question is why?
So the problem is inside of devel:languages:python repositories.
I think that's unfortunate too, but I guess that's how it was introduced. Since there were still quite a few packages missing at the beginning, I have a separate Python repo in my home repo. In the meantime there are about 800 packages. It doesn't necessarily make sense to me, but ......
Regards Eric
Am 2. August 2023 05:11:18 MESZ schrieb Greg Freemyer <greg.freemyer@gmail.com>:
All,
The python packaging guidelines call for getting opensuse 15.5 packages to build with python 3.11
I've got roughly 50 packages that use python in security:forensics.
Most using the 15.5 repo now build a python311 RPM.
But a couple are complaining because python311-cffi.and python311-cryptography packages aren't available in devel:languages:python or devel:languages:python:pytest
Can someone take a look and fix those to packages to follow the packaging guidelines?
Thanks, Greg
On 2023-08-02, 14:44 GMT, Greg Freemyer wrote:
I want to formally request that the devel:languages:python:pytest opensuse15.5 repo have the devel:languages:python repo added to the path list.
It's called Bugzilla, use it. However, as probably closest to being the person deciding on these matters, I have to say that this is not how it is supposed to be. Devel projects are devel projects, and they are meant to be used to develop packages for some released projects (Factory and Leap these days). If you are developing a security package for Factory, then your project should depend ideally on openSUSE:Factory and nothing else. If you develop for Leap (any version), then you should depend on that. Yes, it is mildly inconvenient that python311 packages are still not completely in Leap (so you may temporarily use workaround of depending on d:l:p:backports), but developing against d:l:p and d:l:p:pytest is strongly discouraged and I will not do anything to make it more simple. Best, Matěj -- https://matej.ceplovi.cz/blog/, @mcepl@floss.social GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 To love another person Is to see the face of God. -- yes, incredibly cheesy verse from the screenplay of the movie Les Miserables (2012)
Am 02.08.23 um 00:49 schrieb Andrei Borzenkov:
On Wed, Aug 2, 2023 at 10:24 AM Eric Schirra <ecsos@opensuse.org> wrote:
I mean, there's nothing to fix. That's the way it's meant to be. If a python package is built in the repos for 15.5, then these are always python311 packages. So you still have to include devel:languages:Python. You probably misunderstood the problem.
He does include devel:languages:python and devel:languages:python:pytest in his project, but there are some packages that failed to build there.
Take as an example python-cffi from security:forensics. It fails to build due to missing prerequisites, one of them is python311-py.
devel:languages:python:pytest/python-py in turn fails to build due to missing prerequisites again. One of them is devel:languages:python:pytest/python-apipkg. Which itself fails to build due to missing python311-wheel (and others).
Now, python-wheel *is* successfully built in devel:languages:python for Leap 15.5, but devel:languages:python:pytest does not include devel:languages:python in its repository path. The question is why?
So the problem is inside of devel:languages:python repositories.
The problem is that devel:languages:python and its subprojects (except :backports, see below) are not meant to be in the path of other projects or even as download repositories for user installations. Someone (TM) has to fix the missing packages in SLE15 Updates and only that repository should be used for the 15.5 targets in other devel projects. As a second option, back in May, Dirk Müller suggested to directly use devel:languages:python:backports, which at least has all the python packages from Factory and thus works around the unfortunate split of e.g. d:l:p and d:l:p:backports. However, past discussions on the mailinglist (or factory or packaging), suggested that it is only meant for development and not as a repository path for other projects. The communication from various individuals in the SUSE Python maintainer group is not that consistent, unfortunately.
Am 2. August 2023 05:11:18 MESZ schrieb Greg Freemyer <greg.freemyer@gmail.com>:
All,
The python packaging guidelines call for getting opensuse 15.5 packages to build with python 3.11
I've got roughly 50 packages that use python in security:forensics.
Most using the 15.5 repo now build a python311 RPM.
But a couple are complaining because python311-cffi.and python311-cryptography packages aren't available in devel:languages:python or devel:languages:python:pytest
Can someone take a look and fix those to packages to follow the packaging guidelines?
Thanks, Greg
- Ben
participants (5)
-
Andrei Borzenkov -
Ben Greiner -
Eric Schirra -
Greg Freemyer -
Matěj Cepl