Bug#757308: grass: Please update to use wxpython3.0
On Wed, Aug 20, 2014 at 05:53:18PM +1200, Hamish wrote: Hamish wrote: grass 6.4.4.packaging is currently (basically) ready in DebianGIS git. Sebastiaan: But not by using git-import-orig. The upstream branch hasn't been updated with the grass_6.4.4.orig.tar.gz contents. it was done in the master branch, http://git.linuxminded.nl/?p=pkg-grass/grass;a=commit;h=d183a32b883dbad88e0d751d030e177dd90926a0 tagging is currently incomplete, but known todo and discussed privately. ... Do you mind to discuss NOT privately? You should run lintian showing all tags after your build to get an idea of what is left to fix before I would consider an upload. er, you really think we don't do that and know exactly what they are? We've been busy packaging this software for more than a dozen years! Not masking false positives and real but won't-fix in this major version lintian issues is not a bug IMHO. Bas, the grass package has a long list of lintian issues due mainly to specific choices of upstream team and historical reasons. It is quite pointless trying to respect the full policy by patching at every new release, and it would be also an heavy job (with no hopes of being accepted upstream for merging). This is well expected for such a scientific program born in the 80s and having a very conservative and tiny development team. No doubt the main rules file could use a bit of a refresh here and there (supporting 'make -j' would be nice), but let's continue this conversation on the DebainGIS list, not in a ticket about transitioning to wxpython3.0. I don't understand *why* the d-gis repo is not already up-to-date with an appropriate branching and tagging for the proper support. It is quite annoying working with yet-another-git-archive. -- Francesco P. Lovergine ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#757308: grass: Please update to use wxpython3.0
Hi Hamish, On Wed, Aug 20, 2014 at 03:35:36PM +1200, Hamish B wrote: If there are parts of the patch suitable for upstream I would be happy to commit them, just be aware that changes (even debian/patches/) should be compatible back to at least squeeze and Ubuntu 10.04 LTS, since we aim for wide cross-platform compatibility. i.e. backports are pretty trivial right now, and they should stay that way. All the changes in debian/patches/wxpy3.0-compat.patch in the debdiff I attached should be suitable for upstream I think - they remain compatible with wxpython 2.8, and there's already a check in there that the wxPython version is at least 2.8.1.1, so compatibility with 2.6 isn't a concern. Cheers, Olly ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#757308: grass: Please update to use wxpython3.0
Hi, grass 6.4.4.packaging is currently (basically) ready in DebianGIS git. Frankie is just returned, hopefully refreshed, and so with luck that will be reviewed and uploaded in the very near future. If there are parts of the patch suitable for upstream I would be happy to commit them, just be aware that changes (even debian/patches/) should be compatible back to at least squeeze and Ubuntu 10.04 LTS, since we aim for wide cross-platform compatibility. i.e. backports are pretty trivial right now, and they should stay that way. thanks, Hamish ps- grass64 and grass70 deb packages can co-exist (I'm already doing that), and like Octave, for a time it will be good for Debian to ship both versions. ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#757308: grass: Please update to use wxpython3.0
On 08/20/2014 05:35 AM, Hamish B wrote: Hi, grass 6.4.4.packaging is currently (basically) ready in DebianGIS git. But not by using git-import-orig. The upstream branch hasn't been updated with the grass_6.4.4.orig.tar.gz contents. Nor is there a pristine-tar branch. There are still lintian errors and lesser issues, some of which are easily fixed by updating the control files. You should run lintian showing all tags after your build to get an idea of what is left to fix before I would consider an upload. Frankie is just returned, hopefully refreshed, and so with luck that will be reviewed and uploaded in the very near future. Please don't upload before more fixes can be committed to the repo on git.d.o. I'm currently working on fixing as much of these issues as I can, have a look at the current progress at: http://git.linuxminded.nl/?p=pkg-grass/grass The minimal dh rules changes are a bit invasive, but will ease policy compliance and allows easy use of additional debhelper modules such as autotools_dev and autoreconf. If there are parts of the patch suitable for upstream I would be happy to commit them, just be aware that changes (even debian/patches/) should be compatible back to at least squeeze and Ubuntu 10.04 LTS, since we aim for wide cross-platform compatibility. i.e. backports are pretty trivial right now, and they should stay that way. Would you care to test my recent changes on the ancient distributions (squeeze and Ubuntu 10.04). I personally don't want to support those backports as they limit progress. thanks, Hamish ps- grass64 and grass70 deb packages can co-exist (I'm already doing that), and like Octave, for a time it will be good for Debian to ship both versions. Have you thought about which branches to use for grass64 and grass70? Kind Regards, Bas -- GPG Key ID: 4096R/E88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#757308: grass: Please update to use wxpython3.0
Hamish wrote: grass 6.4.4.packaging is currently (basically) ready in DebianGIS git. Sebastiaan: But not by using git-import-orig. The upstream branch hasn't been updated with the grass_6.4.4.orig.tar.gz contents. it was done in the master branch, http://git.linuxminded.nl/?p=pkg-grass/grass;a=commit;h=d183a32b883dbad88e0d751d030e177dd90926a0 tagging is currently incomplete, but known todo and discussed privately. ... You should run lintian showing all tags after your build to get an idea of what is left to fix before I would consider an upload. er, you really think we don't do that and know exactly what they are? We've been busy packaging this software for more than a dozen years! Not masking false positives and real but won't-fix in this major version lintian issues is not a bug IMHO. No doubt the main rules file could use a bit of a refresh here and there (supporting 'make -j' would be nice), but let's continue this conversation on the DebainGIS list, not in a ticket about transitioning to wxpython3.0. regards, Hamish ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#757308: grass: Please update to use wxpython3.0
On Thu, Aug 07, 2014 at 10:52:42AM +0200, Sebastiaan Couwenberg wrote: On 08/07/2014 06:56 AM, Olly Betts wrote: It looks like grass 7.0.0 will be compatible with wxPython 3.0 - I see in http://trac.osgeo.org/grass/wiki/Release/7.0.0beta-News the entry: | wxPython 3 compatibility fixes So updating the package to this version seems the simplest fix. In theory this is a good idea. But updating from grass 6.4.3 to 7.0.0 will require a transition, which we are unlikely to get in shape before the freeze in November. Ah, I didn't appreciate there were rdeps which would need to be updated for this too. Updating from grass 6.4.3 to 6.4.4 is more in the realm of possibilities, so we'll need to look into backporting the wxPython 3.0 changes to that. I've been working on a script to assist updating code to work with wxPython3, which might be helpful here if the python code in grass has changed a lot between 6.4.x and 7.0.0 such that backporting the changes is difficult: http://anonscm.debian.org/gitweb/?p=collab-maint/wx-migration-tools.git;a=summary I tried it on the 6.4.3 package, and with a bit of manual tweaking the startup wizard works, but the GUI after that doesn't. I'll send the debdiff of that in case it's useful. Cheers, Olly ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#757308: grass: Please update to use wxpython3.0
On Thu, Aug 07, 2014 at 03:46:15PM +0200, Andreas Tille wrote: just a metacomment: Due to the wxPython issue several packages get RC bugs filed which in several cases leads to the fact that these are simply removed from testing and either create a lot of work or will be lost for the Jessie release. All the bugs I've filed for the wxpython3.0 transition are currently severity important (as recommended here: https://wiki.debian.org/Teams/ReleaseTeam/Transitions), which means none are RC. Are you actually talking about wxWidgets? The bugs for the wxwidgets3.0 transition are mostly RC currently, as most have been filed for some time. But the testing autoremoval takes into account whether there's activity on the bug before removing, as documented here: https://lists.debian.org/debian-devel-announce/2013/11/msg7.html I've just looked through the packages which have been auto-removed so far, and most of these bugs have had no response from the maintainer (even when I've included a patch - e.g. #749870 and #751552), or the maintainer has explicitly been OK with the package being removed from testing. It seems to me the big issue here is really that we have a lot of maintainers who don't respond to bugs in their packages. I'm intending to do a pass over the packages which are still using wxwidgets2.8 and try to get as many as possible moved over. My aim here is to migrate Debian to wxwidgets3.0 rather than to remove any package that stands in the way of removing wxwidgets2.8. If you're alluding to #750910 particularly, the issue there was that there's a significantly newer upstream version, and so trying to port the current package to wx3 seemed a bad approach. You'd indicated that the maintainers were going to look at updating, so I left it at that. IMHO this is bad timing to get a predependency for several applications removed quite close to a release date. I left wxpython3.0 until later because it released a few months after wxwidgets3.0, and I expect fewer problems (e.g. the Unicode handling changes cause FTBFS for some C++ applications, but aren't a problem for Python apps). The packages I've looked at so far seem to mostly bear this out. I would certainly rather have started the wxpython3.0 work sooner, but I'm the only active wx maintainer in recent times (though Gianfranco Costamagna has started to get involved recently), and I've been busy with the wxwidgets3.0 transition - there's only so much I can do at once. But that's also the reason why we need to try to eliminate wxwidgets2.8 from jessie - I just don't have the time to maintain packages of such a large upstream project which the upstream maintainers are no longer interested in. Nobody else in Debian seems interested in actually helping to maintain 2.8, and the alternative is to have unmaintained packages of such a large, complex and widely used piece of software. Cheers, Olly ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#757308: grass: Please update to use wxpython3.0
Hi Olly, On Mon, Aug 11, 2014 at 08:07:09AM +0100, Olly Betts wrote: On Thu, Aug 07, 2014 at 03:46:15PM +0200, Andreas Tille wrote: just a metacomment: Due to the wxPython issue several packages get RC bugs filed which in several cases leads to the fact that these are simply removed from testing and either create a lot of work or will be lost for the Jessie release. All the bugs I've filed for the wxpython3.0 transition are currently severity important (as recommended here: https://wiki.debian.org/Teams/ReleaseTeam/Transitions), which means none are RC. Ahh, sorry. I considered them RC as well. I've just looked through the packages which have been auto-removed so far, and most of these bugs have had no response from the maintainer (even when I've included a patch - e.g. #749870 and #751552), or the maintainer has explicitly been OK with the package being removed from testing. Uhmmm, good we talked about this. I think time is ripe to team hijack ctsim. Kevin M. Rosenberg is MIA / unresponsive regarding Debian Med team maintenance offers since a long time. So he was warned. I'll care about ctsim (#751552) in the next couple of days. It seems to me the big issue here is really that we have a lot of maintainers who don't respond to bugs in their packages. I perfectly agree that this is the most frustrating issue for migrations. I'm intending to do a pass over the packages which are still using wxwidgets2.8 and try to get as many as possible moved over. My aim here is to migrate Debian to wxwidgets3.0 rather than to remove any package that stands in the way of removing wxwidgets2.8. Thanks for your intense work on this. That's really welcome. If you're alluding to #750910 particularly, the issue there was that there's a significantly newer upstream version, and so trying to port the current package to wx3 seemed a bad approach. You'd indicated that the maintainers were going to look at updating, so I left it at that. I did not had this particular bug in mind (even if we need to care for it in Debian Med team - to bad that the people who touched the package before did not responded yet). When I wrote my last mail I had this problem of gnumed-client[1] in mind. IMHO this is bad timing to get a predependency for several applications removed quite close to a release date. I left wxpython3.0 until later because it released a few months after wxwidgets3.0, and I expect fewer problems (e.g. the Unicode handling changes cause FTBFS for some C++ applications, but aren't a problem for Python apps). The packages I've looked at so far seem to mostly bear this out. I would certainly rather have started the wxpython3.0 work sooner, but I'm the only active wx maintainer in recent times (though Gianfranco Costamagna has started to get involved recently), and I've been busy with the wxwidgets3.0 transition - there's only so much I can do at once. That's fine. I hope my mail was not sounding to frustrated (I guess you get a lot of unfriendly response and I did not wanted to add to this set, really). Your work id really appreciated. May be you could ask for some help on wxpython3.0 on some relevant lists to also get this one in right in time? But that's also the reason why we need to try to eliminate wxwidgets2.8 from jessie - I just don't have the time to maintain packages of such a large upstream project which the upstream maintainers are no longer interested in. +1 Nobody else in Debian seems interested in actually helping to maintain 2.8, and the alternative is to have unmaintained packages of such a large, complex and widely used piece of software. Luckily I managed to upload treeviewx yesterday and I will have a look into ctsim and sitplus soon. Hope this will help your effort. Kind regards Andreas. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707341#36 -- http://fam-tille.de ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#757308: grass: Please update to use wxpython3.0
On Mon, Aug 11, 2014 at 09:45:19AM +0200, Andreas Tille wrote: On Mon, Aug 11, 2014 at 08:07:09AM +0100, Olly Betts wrote: I've just looked through the packages which have been auto-removed so far, and most of these bugs have had no response from the maintainer (even when I've included a patch - e.g. #749870 and #751552), or the maintainer has explicitly been OK with the package being removed from testing. Uhmmm, good we talked about this. I think time is ripe to team hijack ctsim. Kevin M. Rosenberg is MIA / unresponsive regarding Debian Med team maintenance offers since a long time. So he was warned. I'll care about ctsim (#751552) in the next couple of days. That's one of those packages which I'm reluctant to NMU as I don't have suitable test data, and I don't know much about the field they're used in, so even with suitable test data I'm not sure how well I could test an updated package. So I'm particularly glad to see it taken care of. If you're alluding to #750910 particularly, the issue there was that there's a significantly newer upstream version, and so trying to port the current package to wx3 seemed a bad approach. You'd indicated that the maintainers were going to look at updating, so I left it at that. I did not had this particular bug in mind (even if we need to care for it in Debian Med team - to bad that the people who touched the package before did not responded yet). When I wrote my last mail I had this problem of gnumed-client[1] in mind. That's an unfortunate situation, but there just isn't a release of wxPython which supports Python 3 yet. However, that's orthogonal to the wxPython 2.8-3.0 transition - if gnumed-client remained using wxPython 2.8, it would still be stuck in the same situation. The essential problem is simply that gnumed-client has one dependency which is dropping python2 support and another which doesn't yet have python3 support. I've not looked at what gnumed-client uses python-uno for, but if it is just doing document conversion, then LO 4.3 has a libreofficekit API (it was actually in 4.2 as liblibreoffice, but 4.3 is more solid) which provides access to document conversion with significantly less overhead than via uno: https://github.com/xrmx/pylokit Otherwise, the only short-term solution which I can think of is for gnumed-client to add a python2 facade to access python3.3-uno, e.g. serialising function calls over a pipe. I don't know how feasible that would be though. I would certainly rather have started the wxpython3.0 work sooner, but I'm the only active wx maintainer in recent times (though Gianfranco Costamagna has started to get involved recently), and I've been busy with the wxwidgets3.0 transition - there's only so much I can do at once. That's fine. I hope my mail was not sounding to frustrated (I guess you get a lot of unfriendly response and I did not wanted to add to this set, really). Your work id really appreciated. May be you could ask for some help on wxpython3.0 on some relevant lists to also get this one in right in time? I'd certainly be happy with fewer unfriendly responses, but there really haven't been a lot. I have a script in the works to aid with porting to wxPython 3.0 by updating for a few changes to constant and method names, based on experience so far and the (sadly rather vague in places) list of changes upstream provide. Once that's in a sane state, my plan was to send a note to appropriate lists. Luckily I managed to upload treeviewx yesterday and I will have a look into ctsim and sitplus soon. Hope this will help your effort. Yes, much appreciated. Cheers, Olly ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#757308: grass: Please update to use wxpython3.0
Hi Olly, On 08/07/2014 06:56 AM, Olly Betts wrote: It looks like grass 7.0.0 will be compatible with wxPython 3.0 - I see in http://trac.osgeo.org/grass/wiki/Release/7.0.0beta-News the entry: | wxPython 3 compatibility fixes So updating the package to this version seems the simplest fix. In theory this is a good idea. But updating from grass 6.4.3 to 7.0.0 will require a transition, which we are unlikely to get in shape before the freeze in November. Updating from grass 6.4.3 to 6.4.4 is more in the realm of possibilities, so we'll need to look into backporting the wxPython 3.0 changes to that. Kind Regards, Bas -- GPG Key ID: 4096R/E88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#757308: grass: Please update to use wxpython3.0
Hi, just a metacomment: Due to the wxPython issue several packages get RC bugs filed which in several cases leads to the fact that these are simply removed from testing and either create a lot of work or will be lost for the Jessie release. IMHO this is bad timing to get a predependency for several applications removed quite close to a release date. Kind regards Andreas. On Thu, Aug 07, 2014 at 10:52:42AM +0200, Sebastiaan Couwenberg wrote: Hi Olly, On 08/07/2014 06:56 AM, Olly Betts wrote: It looks like grass 7.0.0 will be compatible with wxPython 3.0 - I see in http://trac.osgeo.org/grass/wiki/Release/7.0.0beta-News the entry: | wxPython 3 compatibility fixes So updating the package to this version seems the simplest fix. In theory this is a good idea. But updating from grass 6.4.3 to 7.0.0 will require a transition, which we are unlikely to get in shape before the freeze in November. Updating from grass 6.4.3 to 6.4.4 is more in the realm of possibilities, so we'll need to look into backporting the wxPython 3.0 changes to that. Kind Regards, Bas -- GPG Key ID: 4096R/E88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel -- http://fam-tille.de ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#757308: grass: Please update to use wxpython3.0
Package: grass Version: 6.4.3-3 Severity: important Tags: patch sid jessie User: freewx-ma...@lists.alioth.debian.org Usertags: wx3.0 wxpy3.0 Control: block 748169 by -1 Control: block 755757 by -1 We're aiming to migrate the archive to using wxpython3.0 instead of wxwidgets2.8, and hope to drop wxwidgets2.8 before jessie is released. It looks like grass 7.0.0 will be compatible with wxPython 3.0 - I see in http://trac.osgeo.org/grass/wiki/Release/7.0.0beta-News the entry: | wxPython 3 compatibility fixes So updating the package to this version seems the simplest fix. Cheers, Olly ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
