Hello Tanguy. (just for reference: xmpppy - original project, python-xmpp - package for Debian that contains it) Yes, development of xmpppy was stalled long ago and it is in maintence mode right now by Norman Rasmussen. Support for package python-xmpp was stalled even earlier. At the time I last checked the dependency chain was like this:
1) update of python-xmpp breaks jabber-irc package as there are some minor, yet incompatible changes. 2) jabber-irc has both a newer version and oneliner fix and either of these reenables it to work with python-xmpp. However by some reason (do not remember what) there was preference to newer version and ... 3) newer jabber-irc required update to python-irclib. Since I am not a DD - I was not able to upload a newer version of python-irclib and nobody agreed. So the process stalled. So I will be glad if you do this work for me. I guess you will need to make sure that your actions either keep jabber-irc in working state or drop it, but not leave it broken. I see these steps as good ones: 1) You can just try installing newest version of python-irclib, package newest python-xmpp and jabber-irc and fix whatever pokes out to make them work. Then upload the result. Not sure if you'll need to upload python-irclib, probably not as it had some updates already. I can help with this. 2) There is also project named xmpppony. it is a fork of xmpppy with some serious improvements like file transfer. Authors of xmpppony declare API compartibility (I tried downloading their source and looking at it - this statement looks like true). They also explicitly expressed no objections of merging their work back to upstream (xmpppy). So you could consider publishing their version as, say, python-xmpp v0.6 or dropping a python-xmpp package and publishing something like python-xmpppony that provides python-xmpp. I would advise to start with previous step though as replacement with xmpppony is more intrusive and will require more work. Regards Alexey. 2010/8/21 Tanguy Ortolo <[email protected] <tanguy%[email protected]> > > Hello Alexey, > > Le vendredi 06 août 2010, Nicolas Maître a écrit : > > Please, could you update the package to the latst available version, > > namely xmpppy 0.5.0rc1. > > Il looks like you are both the upstream author and the maintainer of the > Debian package. When I look the the different versions available: > * last upstream is 0.5.0rc1, 2009/04/07 (more than a year ago); > * last in Debian is 0.4.1, 2007/12/15 (almost three years ago). > > So I would say that the upstream development of xmppy aka python-xmpp is > stalled, and that the Debian package is stalled too, and outdated. > > Unfortunately, there are softwares that depend on python-xmpp (let me > call it like that, as it provides a Python module called xmpp). > > So, would it be useful if I took over the maintenance of the Debian > package? I would not offer to develop the library itself, though, only > to update the Debian package. > > Regards, > > -- > Tanguy Ortolo > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iQIcBAEBCgAGBQJMb8M9AAoJENbvpqxLENhHDMwP/2IWqhlqLjezawcnZBtCV+Oh > oyR4k9+rPDGzWFFKNZevoyqSjMYCUOl5JV1tmlsHjPLNscBkHHjnXcwwhDVOZwPe > 2v+gvFrkynW7PbTEKw8nkYzjZ/7vnDwz0Qt1z6MXMU5RI+xKIWTA0p+++m6P+iR1 > FJ+qtdwPrKqjCcw+1RR8KahsupDJZbfpFYE+bEBXR5X0+fZ+4gzmEnPvJLraxdfL > G3KANV2jG2mwgBm3fuQ9gsF19O3vH/xHZgkv1y1ncAQuKdvvYAnniJfRRIyhfOWM > PPz6aIcWWSbwqBahyHKaU0Ti5phLwkfLddt/eyJSdiXUeek+czhfefKTd0wyN6TW > jRDrLeTNJjK5x2yDdM1Ny+X8pZsERXx7SAHse+Ra/E4whLU3hlAsJDGEKIQoUAY4 > Zi53r9RJzsyWKbauS8P8U7wS219pqawTV6CT44D6deDoM2UQOrjiBc9ID1tH9WRk > S59VTi7BvYSS6PERfy4PqlGuuoxZMPrSwOMlg38i4rtBxQYx6S1gUbivxjE+h/Pu > gCHTgSBLNQbmU5d6DMWfqS620yUhLTaiHfpJfrr2zAJi3X6tt8U/XHfUmLX5OGcP > +OwItL64nNyiPGnP0w0BrqjSyW21UMfeTW8APr2EFbCC+v0pfP+KgBqUPjA9zMRq > v2LwSf38lSPQuhvusx8a > =FV03 > -----END PGP SIGNATURE----- > >
