Could you please do a Copr impact check? That could help the maintainer gain confidence to release 1.15.0 final on PyPI which we want for https://bugzilla.redhat.com/show_bug.cgi?id=1989081

Exactly what I wanted to do to help upstream with testing. I see that Tomáš is rebuilding the packages in: https://copr.fedorainfracloud.org/coprs/thrnciar/python-cffi/builds/ and there is also a control copr to compare failures, thanks. Let me know if I can help you anyhow.

There are 20 packages failing. I think failures are not connected to this update except of python-assyncssh and python-azure-mgmt-compute. These two are green when I tried scratch build.

@lbalhar, could you please take a look at them?

Will do tomorrow, thanks.

It seems to me that the problem in those two failing packages is transitive because neither of them uses cffi directly. My first candidate for the troublemaker is PyOpenSSL.

Thank you, in that case, I think it should be safe to update cffi to 1.15.0.

Give me some more time please, I'm still investigating. That info will be valuable for upstream.

Upstream tests of pyopenssl work well with release candidate version of cffi, so the problem has to be somewhere else. It seems to me that asyncssh in version 2.7.1 added support for openssl 3 which we have in rawhide so an update might fix that problem.

In the end, it does not seem to be a problem in cffi and I think that we can merge and ship this.