Bug#764791: geophar: Please update to use wxpython3.0

2014-10-13 Thread Georges Khaznadar
Dear Olly,

thank you for the bug report.

I apologize : geophar was ready for python-wxgtk3.0, but I did not
upgrade the dependency in the control file (mostly borrowed from the
defunct package wxgeometrie).

I upload the fix shortly!

Best regards,   Georges.

Olly Betts a écrit :
 Source: geophar
 Version: 14.07~dfsg1-1
 Severity: serious
 Justification: blocks the almost complete wxpython3.0 transition
 Tags: sid jessie
 User: freewx-ma...@lists.alioth.debian.org
 Usertags: wxpy3.0
 Control: block 755757 by -1
 
 We've been working on migrating the archive to using wxpython3.0 instead
 of wxwidgets2.8 for a few months, and this process is close to complete,
 so jessie won't be releasing with wxwidgets2.8 - you can see the release
 team's tracker here:
 
 https://release.debian.org/transitions/html/wxpython3.0.html
 
 As I warned you a few weeks ago while geophar was still in NEW, you'll
 need to update it to use wxpython3.0 if you want it to be in jessie.
 
 I've included the template email from the bugs filed for the transition
 which contains information which is likely to be useful for updating to
 wxpython3.0.
 
 The wxPython 3.0 API mostly adds to the wxPython2.8 API.  Many packages
 work with wxPython 3.0 without any changes, but there are a few
 incompatibilities.  For example, wx.Color is no longer supported as
 an alias for wx.Colour, and some constants which were deprecated in 2.8
 have been removed.  All the removed constants I'm aware of were set to 0
 in wxPython 2.8, so removing them is still compatible with 2.8.
 
 To assist updating to wxPython 3.0, I've put together a script which
 will help make the mechanical changes required.  This is in a git repo
 on collab-maint along with a README about using it and updating packages
 for wxPython 3.0 in general:
 
 http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git
 
 The script has some options to control the sorts of changes it makes -
 see the README and --help output for more information - you can view
 the latest version of the README online here:
 
 http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README
 
 I've developed this script by trying to convert 20+ packages.  Please
 try it out on your package - in many cases, it should be enough to get
 your package working (if it doesn't already) - if it does, please upload
 (and close this bug).
 
 If the script doesn't do the job, please let me know (or improve the
 script if you can figure out what it needs to do to get your package
 working).
 
 Another issue you may hit is that wxWidgets 3.0 now defaults to enabling
 its WXDEBUG checks for incorrect API usage, so some applications will
 emit scary sounding assertion failures.  These are unlikely to
 actually be new, just in a default build of 2.8, such incorrect uses
 were handled quietly behind the scenes.  Sometimes these are easy to
 fix, but if not you can easily patch the application to tell wx 3.0 to
 handle them in the same way wx 2.8 does - details of how to do so are in
 the README:
 
 http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README
 
 Cheers,
 Olly
 

-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: Digital signature


Bug#764791: geophar: Please update to use wxpython3.0

2014-10-11 Thread Olly Betts
Source: geophar
Version: 14.07~dfsg1-1
Severity: serious
Justification: blocks the almost complete wxpython3.0 transition
Tags: sid jessie
User: freewx-ma...@lists.alioth.debian.org
Usertags: wxpy3.0
Control: block 755757 by -1

We've been working on migrating the archive to using wxpython3.0 instead
of wxwidgets2.8 for a few months, and this process is close to complete,
so jessie won't be releasing with wxwidgets2.8 - you can see the release
team's tracker here:

https://release.debian.org/transitions/html/wxpython3.0.html

As I warned you a few weeks ago while geophar was still in NEW, you'll
need to update it to use wxpython3.0 if you want it to be in jessie.

I've included the template email from the bugs filed for the transition
which contains information which is likely to be useful for updating to
wxpython3.0.

The wxPython 3.0 API mostly adds to the wxPython2.8 API.  Many packages
work with wxPython 3.0 without any changes, but there are a few
incompatibilities.  For example, wx.Color is no longer supported as
an alias for wx.Colour, and some constants which were deprecated in 2.8
have been removed.  All the removed constants I'm aware of were set to 0
in wxPython 2.8, so removing them is still compatible with 2.8.

To assist updating to wxPython 3.0, I've put together a script which
will help make the mechanical changes required.  This is in a git repo
on collab-maint along with a README about using it and updating packages
for wxPython 3.0 in general:

http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git

The script has some options to control the sorts of changes it makes -
see the README and --help output for more information - you can view
the latest version of the README online here:

http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README

I've developed this script by trying to convert 20+ packages.  Please
try it out on your package - in many cases, it should be enough to get
your package working (if it doesn't already) - if it does, please upload
(and close this bug).

If the script doesn't do the job, please let me know (or improve the
script if you can figure out what it needs to do to get your package
working).

Another issue you may hit is that wxWidgets 3.0 now defaults to enabling
its WXDEBUG checks for incorrect API usage, so some applications will
emit scary sounding assertion failures.  These are unlikely to
actually be new, just in a default build of 2.8, such incorrect uses
were handled quietly behind the scenes.  Sometimes these are easy to
fix, but if not you can easily patch the application to tell wx 3.0 to
handle them in the same way wx 2.8 does - details of how to do so are in
the README:

http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README

Cheers,
Olly


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org