Bug#774948: [tryton-debian] Bug#783029: [py3porters-devel] Packaging of suds-jurko
* Lionel Elie Mamane: Re: [tryton-debian] Bug#783029: [py3porters-devel] Packaging of suds-jurko (Tue, 28 Apr 2015 16:32:23 +0200): CCed 774...@bugs.debian.org for reference Hello Lionel, On Tue, Apr 28, 2015 at 03:27:12PM +0200, Mathias Behrle wrote: * Lionel Elie Mamane: [tryton-debian] suds in Debian (Tue, 28 Apr 2015 13:24:25 +0200): I just uploaded the jurko fork of suds (the latter you are maintainer of in Debian) to Debian. I am quite surprised to hear that. Your package even doesn't seem to close an ITP bug. Could you please provide the link to your packaging sources? https://people.debian.org/~lmamane/suds/ You don't have permission to access /~lmamane/suds/suds-jurko_0.6-2.dsc on this server. The killer feature for me was compatibility with Python 3. It installs as python module suds, for drop-in replacement of suds. The killer feature of suds-jurko those days may turn out to be that it tends to be as unmaintained as the original suds. sigh For now, the Python2 package of suds-jurko provides and conflicts with python-suds (your package). Let me know whether you think something more soft, like e.g. collaborating through update-alternatives, would be more appropriate. Sorry, coordinating before uploading to NEW would have been much more appropriate, (...). Before commenting further I would like to hear about your motivations: My motivation is purely having a working suds for Python3 so that I can use stdnum.eu.vat.check_vies in Python3 (see https://bugs.debian.org/774948 ). If my work is useful to others, then I'm happy to share it, if not I'll keep it is a local package for me. - Are you aware of the work in progress at [1]? No. - Are you aware of the planning to prepare suds-jurko as a drop-in replacement for suds with coordinating to migrate also the project at pypi [2][3]? No. Since you seem to have good not-too-long-term plans, I'm happy if we ask ftpmaster to reject my upload to make way for your plans. The current state is: - suds (as the original package from fedora) has a dead upstream - suds-jurko (fork of the original package ported to py3) meanwhile seems to have a dead (or at least overloaded and unresponsive) upstream, too. Last release: 2014-01-24 Last commit: 2014-12-25 - pysimplesoap[0] seems to be a promising and maintained project. My personal plans are: - Wait some weeks (say until end of May), if either there will be some feedback or some revivification on the project. - In case the project shows activity from maintainer side I would take it and do a drop in for current suds. - In case there will be no activity, I won't step in as the quasi upstream of suds-jurko. I would inform the rdepends of python-suds to consider the usage of pysimplesoap. Indeed, if you still want to take over maintenance of suds-jurko then under this circumstances I will be happy to inform the rdepends to use your package and to take off python-suds from the archive. I think - provided pysimplesoap qualifies as a replacement for suds and suds-jurko remains in the current state - it makes more sense to put work on patches for the rdepends of python-suds to use pysimplesoap than to introduce another unmaintained package in the archive. At least I personally don't feel to have the continuing ability and to take the responsibility to beat another dead horse. If you want then to take over, that's fine for me. Until that decision I ask you indeed to wait with your package (i.e. to ask ftp-masters to not consider it for the moment). As always I am open to suggests, those are just my current feelings and plans. Cheers, Mathias [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782970 -- Mathias Behrle PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6 pgp_GmHXaiD94.pgp Description: Digitale Signatur von OpenPGP
Bug#774948: [tryton-debian] Bug#783029: [py3porters-devel] Packaging of suds-jurko
On Wed, Apr 29, 2015 at 11:46:01AM +0200, Mathias Behrle wrote: * Lionel Elie Mamane: Re: [tryton-debian] Bug#783029: [py3porters-devel] Packaging of suds-jurko (Tue, 28 Apr 2015 16:32:23 +0200): On Tue, Apr 28, 2015 at 03:27:12PM +0200, Mathias Behrle wrote: * Lionel Elie Mamane: [tryton-debian] suds in Debian (Tue, 28 Apr 2015 13:24:25 +0200): I just uploaded the jurko fork of suds (the latter you are maintainer of in Debian) to Debian. I am quite surprised to hear that. Your package even doesn't seem to close an ITP bug. Could you please provide the link to your packaging sources? https://people.debian.org/~lmamane/suds/ You don't have permission to access /~lmamane/suds/suds-jurko_0.6-2.dsc on this server. Fixed. Sorry, coordinating before uploading to NEW would have been much more appropriate, (...). Before commenting further I would like to hear about your motivations: My motivation is purely having a working suds for Python3 so that I can use stdnum.eu.vat.check_vies in Python3 (see https://bugs.debian.org/774948 ). If my work is useful to others, then I'm happy to share it, if not I'll keep it is a local package for me. Since you seem to have good not-too-long-term plans, I'm happy if we ask ftpmaster to reject my upload to make way for your plans. The current state is: - pysimplesoap[0] seems to be a promising and maintained project. I think - provided pysimplesoap qualifies as a replacement for suds It seems to present a different API, though? (...) I ask you indeed to wait with your package (i.e. to ask ftp-masters to not consider it for the moment). I just asked them to reject it. -- Lionel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774948: [tryton-debian] Bug#783029: [py3porters-devel] Packaging of suds-jurko
On Wed, Apr 29, 2015 at 6:21 AM, Lionel Elie Mamane lio...@mamane.lu wrote: On Wed, Apr 29, 2015 at 11:46:01AM +0200, Mathias Behrle wrote: * Lionel Elie Mamane: Re: [tryton-debian] Bug#783029: [py3porters-devel] Packaging of suds-jurko (Tue, 28 Apr 2015 16:32:23 +0200): On Tue, Apr 28, 2015 at 03:27:12PM +0200, Mathias Behrle wrote: * Lionel Elie Mamane: [tryton-debian] suds in Debian (Tue, 28 Apr 2015 13:24:25 +0200): I just uploaded the jurko fork of suds (the latter you are maintainer of in Debian) to Debian. I am quite surprised to hear that. Your package even doesn't seem to close an ITP bug. Could you please provide the link to your packaging sources? https://people.debian.org/~lmamane/suds/ You don't have permission to access /~lmamane/suds/suds-jurko_0.6-2.dsc on this server. Fixed. Sorry, coordinating before uploading to NEW would have been much more appropriate, (...). Before commenting further I would like to hear about your motivations: My motivation is purely having a working suds for Python3 so that I can use stdnum.eu.vat.check_vies in Python3 (see https://bugs.debian.org/774948 ). If my work is useful to others, then I'm happy to share it, if not I'll keep it is a local package for me. Since you seem to have good not-too-long-term plans, I'm happy if we ask ftpmaster to reject my upload to make way for your plans. The current state is: - pysimplesoap[0] seems to be a promising and maintained project. I think - provided pysimplesoap qualifies as a replacement for suds It seems to present a different API, though? (...) I ask you indeed to wait with your package (i.e. to ask ftp-masters to not consider it for the moment). I just asked them to reject it. Reject preformed. 3 Paul -- Lionel -- :wq -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783029: [tryton-debian] Bug#783029: [py3porters-devel] Packaging of suds-jurko
On Tue, Apr 28, 2015 at 04:32:23PM +0200, Lionel Elie Mamane wrote: On Tue, Apr 28, 2015 at 03:27:12PM +0200, Mathias Behrle wrote: * Lionel Elie Mamane: [tryton-debian] suds in Debian (Tue, 28 Apr 2015 13:24:25 +0200): I just uploaded the jurko fork of suds (the latter you are maintainer of in Debian) to Debian. Before commenting further I would like to hear about your motivations: My motivation is purely having a working suds for Python3 so that I can use stdnum.eu.vat.check_vies in Python3 (see https://bugs.debian.org/774948 ). If my work is useful to others, then I'm happy to share it, if not I'll keep it is a local package for me. I mean: if not, I'll keep it is a local package for me in the immediate future and happily switch back to your suds-in-Debian when it works with Python3. -- Lionel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783029: [tryton-debian] Bug#783029: [py3porters-devel] Packaging of suds-jurko
On Tue, Apr 28, 2015 at 03:27:12PM +0200, Mathias Behrle wrote: * Lionel Elie Mamane: [tryton-debian] suds in Debian (Tue, 28 Apr 2015 13:24:25 +0200): I just uploaded the jurko fork of suds (the latter you are maintainer of in Debian) to Debian. I am quite surprised to hear that. Your package even doesn't seem to close an ITP bug. Could you please provide the link to your packaging sources? https://people.debian.org/~lmamane/suds/ The killer feature for me was compatibility with Python 3. It installs as python module suds, for drop-in replacement of suds. The killer feature of suds-jurko those days may turn out to be that it tends to be as unmaintained as the original suds. sigh For now, the Python2 package of suds-jurko provides and conflicts with python-suds (your package). Let me know whether you think something more soft, like e.g. collaborating through update-alternatives, would be more appropriate. Sorry, coordinating before uploading to NEW would have been much more appropriate, (...). Before commenting further I would like to hear about your motivations: My motivation is purely having a working suds for Python3 so that I can use stdnum.eu.vat.check_vies in Python3 (see https://bugs.debian.org/774948 ). If my work is useful to others, then I'm happy to share it, if not I'll keep it is a local package for me. - Are you aware of the work in progress at [1]? No. - Are you aware of the planning to prepare suds-jurko as a drop-in replacement for suds with coordinating to migrate also the project at pypi [2][3]? No. Since you seem to have good not-too-long-term plans, I'm happy if we ask ftpmaster to reject my upload to make way for your plans. -- Lionel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783029: [tryton-debian] Bug#783029: [py3porters-devel] Packaging of suds-jurko
* Lionel Elie Mamane: [tryton-debian] suds in Debian (Tue, 28 Apr 2015 13:24:25 +0200): Hello Lionel, I just uploaded the jurko fork of suds (the latter you are maintainer of in Debian) to Debian. I am quite surprised to hear that. Your package even doesn't seem to close an ITP bug. Could you please provide the link to your packaging sources? The killer feature for me was compatibility with Python 3. It installs as python module suds, for drop-in replacement of suds. The killer feature of suds-jurko those days may turn out to be that it tends to be as unmaintained as the original suds. I am trying to contact (again) the maintainer (Jurko) since some days, with no success so far[0]. For now, the Python2 package of suds-jurko provides and conflicts with python-suds (your package). Let me know whether you think something more soft, like e.g. collaborating through update-alternatives, would be more appropriate. Sorry, coordinating before uploading to NEW would have been much more appropriate, not talking afterwards about update-alternatives. Before commenting further I would like to hear about your motivations: - Are you aware of the work in progress at [1]? - Are you aware of the planning to prepare suds-jurko as a drop-in replacement for suds with coordinating to migrate also the project at pypi [2][3]? Cheers, Mathias [0] http://lists.alioth.debian.org/pipermail/tryton-debian/2015-April/004511.html [1] https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=tryton/suds.git;a=shortlog;h=refs/heads/py3-drop_in_suds_jurko-WIP [2] http://lists.alioth.debian.org/pipermail/tryton-debian/2014-July/002540.html [3] http://lists.alioth.debian.org/pipermail/tryton-debian/2014-July/002542.html -- Mathias Behrle PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6 pgpDwpL2CoBfv.pgp Description: Digitale Signatur von OpenPGP
Bug#783029: [py3porters-devel] Packaging of suds-jurko
Forwarding the following mail to py3porters-devel and 783...@bugs.debian.org to keep the information at their due place. weitergeleitete Nachricht: Datum: Tue, 28 Apr 2015 13:24:25 +0200 Von: Lionel Elie Mamane lio...@mamane.lu An: Debian Tryton Maintainers maintain...@debian.tryton.org Betreff: [tryton-debian] suds in Debian Hi, I just uploaded the jurko fork of suds (the latter you are maintainer of in Debian) to Debian. The killer feature for me was compatibility with Python 3. It installs as python module suds, for drop-in replacement of suds. For now, the Python2 package of suds-jurko provides and conflicts with python-suds (your package). Let me know whether you think something more soft, like e.g. collaborating through update-alternatives, would be more appropriate. Best Regards, thanks for maintaining python-suds in Debian, have fun, -- Lionel ___ tryton-debian mailing list tryton-deb...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/tryton-debian -- Mathias Behrle PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6* Paul Tagliamonte: Bug#783029: [py3porters-devel] Packaging of suds-jurko (Wed, 22 Apr 2015 11:33:15 -0400): pgpr9YTQWG_Yi.pgp Description: Digitale Signatur von OpenPGP
Bug#783029: [py3porters-devel] Packaging of suds-jurko
On Wed, Apr 22, 2015 at 11:07:49AM +0200, Mathias Behrle wrote: The situation with suds-jurko for sure is not worse, but the problem is more generally to get more or keep unmaintained software in the archive. Entirely sane point of view. My thoughts: - When providing a quite unmaintained suds(-jurko) we will have to maintain the evtl. necessary patches there. So it boils down a little bit, where the patches go: to python-suds or to evtl. rdepends. - When not providing a python3-suds package, the pressure on rdepends is slightly higher to consider using another well maintained SOAP client providing python3 support. Soon we will be at the beginning of a new release cycle, so there will be quite some time for rdepends to adapt. So, I agree with you, but I also think our tradeoff doing such huge patches to upstream software in Debian is not worth it. I'd rather tolerate this, and centrally manage all of that effort (e.g. rather then major patches to 10 apps, maintain minor patches to 1 library) Of course, this also means that it's *your* time, not *my* time, and I have no right to have you do any work at all, so this is entirely up to you. So my reservation with providing a python3-suds as a stop gap is, that this will rather fix unsane conditions than moving forward. We can always file bugs and get our peers to talk with their upstreams about porting to a better backend. I surely won't get in the way of my Debian fellows, if I am told that it is considered useful to have suds-jurko under the actual circumstances in the archive. While trying to contact Jurko once more I will be glad to hear your opinions. AFAIR the work already done[0] and dating from July last year resulted in a functional package, so usually there shouldn't big drawbacks in getting this done provided there weren't any API changes in the meantime (which I don't expect). :+1: Looking forward to working with you, Mathias! Paul -- .''`. Paul Tagliamonte paul...@debian.org | Proud Debian Developer : :' : 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `. `'` http://people.debian.org/~paultag `- http://people.debian.org/~paultag/conduct-statement.txt signature.asc Description: Digital signature
Bug#783029: [py3porters-devel] Packaging of suds-jurko
* Paul Tagliamonte: Re: [py3porters-devel] Packaging of suds-jurko (Tue, 21 Apr 2015 17:58:45 -0400): On Tue, Apr 21, 2015 at 11:53:08PM +0200, Mathias Behrle wrote: Hi together, Heyya, Mathias! Hi Paul, My concerns so far are not for backward incompatibility, but for a rather reliably maintained upstream. I was in regluar contact with jurko, who said to suffer from shortages in ressources. So for now it can be seen, that the project receives a lot of public attention (issues, pull requests)and is widely used[0], but the last commit dates from last year[1] and development seems to stagnate. Do you see this as a worse issue than suds itself (suds upstream) also going unmaintained? The situation with suds-jurko for sure is not worse, but the problem is more generally to get more or keep unmaintained software in the archive. So from my side I am still hesitating and will wait further with pushing suds-jurko as a replacement for python-suds. Is there a downside to shipping it? Are there regressions? I only see it as a step forward from the archive, not a step back, do you agree? If so, why not use it as a stop gap? My thoughts: - When providing a quite unmaintained suds(-jurko) we will have to maintain the evtl. necessary patches there. So it boils down a little bit, where the patches go: to python-suds or to evtl. rdepends. - When not providing a python3-suds package, the pressure on rdepends is slightly higher to consider using another well maintained SOAP client providing python3 support. Soon we will be at the beginning of a new release cycle, so there will be quite some time for rdepends to adapt. So my reservation with providing a python3-suds as a stop gap is, that this will rather fix unsane conditions than moving forward. If pysimplesoap [2][3] proves to be a well maintained project providing all necessary features, it should be the preferable target for a Python2/Python3 SOAP client. Sure, for upstreams that are willing to accept a port to a new library, I guess I'm wondering what we'll do for upstreams that have roughly Python 3 compatable code, but with suds; I'd hate to overhaul their code in a debian/patches/ patch to change a library they use unless we need to I surely won't get in the way of my Debian fellows, if I am told that it is considered useful to have suds-jurko under the actual circumstances in the archive. While trying to contact Jurko once more I will be glad to hear your opinions. AFAIR the work already done[0] and dating from July last year resulted in a functional package, so usually there shouldn't big drawbacks in getting this done provided there weren't any API changes in the meantime (which I don't expect). Cheers, Mathias [0] https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=tryton/suds.git;a=shortlog;h=refs/heads/py3-drop_in_suds_jurko-WIP -- Mathias Behrle PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6 pgpFNsp3B773w.pgp Description: Digitale Signatur von OpenPGP
Bug#783029: [py3porters-devel] Packaging of suds-jurko
On Tue, Apr 21, 2015 at 11:53:08PM +0200, Mathias Behrle wrote: Hi together, Heyya, Mathias! My concerns so far are not for backward incompatibility, but for a rather reliably maintained upstream. I was in regluar contact with jurko, who said to suffer from shortages in ressources. So for now it can be seen, that the project receives a lot of public attention (issues, pull requests)and is widely used[0], but the last commit dates from last year[1] and development seems to stagnate. Do you see this as a worse issue than suds itself (suds upstream) also going unmaintained? So from my side I am still hesitating and will wait further with pushing suds-jurko as a replacement for python-suds. Is there a downside to shipping it? Are there regressions? I only see it as a step forward from the archive, not a step back, do you agree? If so, why not use it as a stop gap? If pysimplesoap [2][3] proves to be a well maintained project providing all necessary features, it should be the preferable target for a Python2/Python3 SOAP client. Sure, for upstreams that are willing to accept a port to a new library, I guess I'm wondering what we'll do for upstreams that have roughly Python 3 compatable code, but with suds; I'd hate to overhaul their code in a debian/patches/ patch to change a library they use unless we need to Best, Mathias Cheers, Paul -- .''`. Paul Tagliamonte paul...@debian.org | Proud Debian Developer : :' : 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `. `'` http://people.debian.org/~paultag `- http://people.debian.org/~paultag/conduct-statement.txt signature.asc Description: Digital signature
