Arch Linux

Upstream report (no response for now): https://github.com/pycurl/pycurl/issues/652

freswa,

No. What. How is "it is utterly broken because upstream doesn't support python2 anymore" closed as an upstream issue for a high-severity "this package makes zero sense to be packaged as-is" ticket?

If we continue to package python2-pycurl in the official repos and upstream won't support it, we must hold it back to the final python2-compatible release.

It is only required by one other package: python2-tornado (optional)

So dropping it to the AUR is another option as suggested in  FS#67933 , though then we might be unable to properly test python2-tornado (needed in turn by salt, yikes, but we're blocked on  FS#61129  for that).

salt uses pycurl for proxy support [1].

[1] https://github.com/saltstack/salt/blob/v2019.2.4/salt/utils/http.py#L522
Edit:

Would demize update salt to python3 if tornado4 was split out and someone else maintained it?
Or must it be tornado5/6 that is used? If so must the tornado5/6 support be official? ( Meaning local patches to add tornado5/6 support would not be acceptable. )

[2] https://bugs.archlinux.org/task/61129#comment184838
[3] https://bugs.archlinux.org/task/61129#comment187735

Edit2:

Consider adding -z,defs to LDFLAGS to make libraries linking to undefined functions a build time error.

I would also suggest to hold back to 7.43.0.5-1, at least until a decision has been taken