Your message dated Tue, 10 May 2016 15:45:56 +1200
with message-id <[email protected]>
and subject line Re: Bug#760695: tinc-gui: Please update to use wxpython3.0
has caused the Debian Bug report #760695,
regarding tinc-gui: Please update to use wxpython3.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
760695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760695
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tinc-gui
Version: 1.1~pre9-1
Severity: wishlist
User: [email protected]
Usertags: wxpy3.0

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.
This transition is already underway, and is being tracked by the release
team here:

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

I noticed that there's a newer version of tinc in experimental, with a
new tinc-gui binary package which depends on python-wxgtk2.8.  I thought
it was useful to file a wishlist bug about this, mostly to give you a heads
up in case the plan is to get this into jessie.

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

--- End Message ---
--- Begin Message ---
Control: fixed -1 1.1~pre12-1

This was fixed by the most recent upload to experimental:

Changes:
 tinc (1.1~pre12-1) experimental; urgency=medium
 .
   * New upstream release.
   * Bump Standards-Version.
   * Depend on python-wxgtk3.0 for the GUI.
   * Use dh --with python2.
   * Add Build-Depends for dh-python.
   * Update links in debian/control and debian/copyright.

Cheers,
    Olly

--- End Message ---

Reply via email to