Created attachment 393296 [details, diff] xmpppy-ssl.patch The attach patch is based on the following: https://github.com/freebsd/freebsd-ports/tree/master/net-im/py-xmpppy/files DEBUG: dispatcher warn Registering protocol "failure" as <class 'xmpp.protocol.Protocol'>(urn:ietf:params:xml:ns:xmpp-tls) DEBUG: socket sent <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/> DEBUG: socket got <proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'/> DEBUG: dispatcher ok Got urn:ietf:params:xml:ns:xmpp-tls/proceed stanza DEBUG: dispatcher ok Dispatching proceed stanza with type-> props->[] id->None DEBUG: tls ok Got starttls proceed response. Switching to TLS/SSL... Traceback (most recent call last): File "./test3.py", line 15, in <module> cl.connect() File "/usr/lib64/python2.7/site-packages/xmpp/client.py", line 205, in connect while not self.TLS.starttls and self.Process(1): pass File "/usr/lib64/python2.7/site-packages/xmpp/dispatcher.py", line 303, in dispatch handler['func'](session,stanza) File "/usr/lib64/python2.7/site-packages/xmpp/transports.py", line 339, in StartTLSHandler self._startSSL() File "/usr/lib64/python2.7/site-packages/xmpp/transports.py", line 318, in _startSSL tcpsock._sslIssuer = tcpsock._sslObj.issuer() AttributeError: '_ssl._SSLSocket' object has no attribute 'issuer'
FYI the upstream seems dead. There is a fork and the original author is ok with it: https://github.com/normanr/xmpppy/issues/16 While it is not clear how reliable the new source is, there is a new release has been tagged on Sep 26, 2014 The "new" URL is below: https://github.com/ArchipelProject/xmpppy v0.5.2
Forgot to say, that the attached patch has been accepted in 0.5.2 fork.
There was a pull request, which was not merged for a while. Now it's merged though!
This gets a bit foggy. A fork or a new repo? A fork generally has a rename of the original. This carries the same name, making for process difficulties rather than technical ones. It would appear that we could simply update HOMEPAGE and SRC_URI to match the new repo in github, however it would be somewhat a forgery, a violation of basic rules pertaining to ownership. But then, would anyone ever notice or be concerned? Either way, upstream being dead is never a good thing. I suggest you get some opinion on how this ought be managed from someone high up like a member of recruiters or such. Doing a switch or repo HOMEPAGE and a bump is easy.
Can we get this fixed already? Right now, the library is non-functional for maybe the most common of its use cases. I'd say it should be either fixed (new repository or not), or masked and subsequently removed.
This is only used by net-im/err, I will CC his maintainer to know what he prefers and if the new fork doesn't break err
commit 2cefed6f6c2557c7e4c9ff72974534fd374c8920 Author: Sergey Popov <pinkbyte@gentoo.org> Date: Tue Nov 10 14:10:10 2015 +0300 dev-python/xmpppy: fix working with SSL fields Suggested-by: Anton Bolshakov <blshkv@pentoo.ch> Gentoo-Bug: 535758 Package-Manager: portage-2.2.23 As current stable is broken, i stabilize new revision immediately
