Your message dated Tue, 07 Oct 2014 07:04:05 +0000
with message-id <e1xboox-0002ns...@franck.debian.org>
and subject line Bug#758939: fixed in mayavi2 4.3.1-3.1
has caused the Debian Bug report #758939,
regarding mayavi2: 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 ow...@bugs.debian.org
immediately.)


-- 
758939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mayavi2
Version: 4.3.1-3
Severity: important
Tags: sid jessie
User: freewx-ma...@lists.alioth.debian.org
Usertags: wxpy3.0
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.
This transition is already underway, and is being tracked by the release
team here:

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

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

I'm happy to sponsor uploads for this transition, though if you have an
active sponsor already check with them first - I don't want to tread on
anyone's toes.

Cheers,
    Olly

--- End Message ---
--- Begin Message ---
Source: mayavi2
Source-Version: 4.3.1-3.1

We believe that the bug you reported is fixed in the latest version of
mayavi2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 758...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Olly Betts <o...@survex.com> (supplier of updated mayavi2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Tue, 07 Oct 2014 06:40:35 +0000
Source: mayavi2
Binary: mayavi2
Architecture: source
Version: 4.3.1-3.1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 
<python-apps-t...@lists.alioth.debian.org>
Changed-By: Olly Betts <o...@survex.com>
Description:
 mayavi2    - scientific visualization package for 2-D and 3-D data
Closes: 758939
Changes:
 mayavi2 (4.3.1-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload with maintainer's permission.
   * Update for wxpython3.0 (Closes: #758939):
     + New patch: wxpy3.0-compat.patch
Checksums-Sha1:
 5de8fd6143a9d27068f7e702d59386165618ae0c 2062 mayavi2_4.3.1-3.1.dsc
 0bf29ef26c0022d98283774482838e05c55b2fa1 13836 mayavi2_4.3.1-3.1.debian.tar.xz
Checksums-Sha256:
 41bc754cf50b8952540d1c35795de4e4893c4c60cfa5cdc294129a429f7add59 2062 
mayavi2_4.3.1-3.1.dsc
 38e116bdbe74cb6e3ef7038684b6647f92ad522bdd60dfc98562d93a86b50790 13836 
mayavi2_4.3.1-3.1.debian.tar.xz
Files:
 a206e72c374d49e2c9c371bdf71a4067 2062 science optional mayavi2_4.3.1-3.1.dsc
 de986e471d0789f67d53d1a3a092007a 13836 science optional 
mayavi2_4.3.1-3.1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUM42cAAoJEBgUewc7rSsH/V4QALL0q2846ybJNLbFRiNiLhgp
wa+bx/q81lY0dbsRWO/xKmeT8q9ogh/SgIZd3Dvf8EuOSQLO/U2/BwIIovTLEUMf
X9KQr1qHAc4VfmHw2HCCVsL+2+yWVV6Vvs0hQrR/KaC5TrO/c10syD0Qo+LFy6PQ
KWaoG31HE2y9C7NK0jCpUsMHTt4Q5+eHjnq3J/pPMpG7pPZ9aqBl39p0NpjGTbYV
2NiHwMurbUQ/Ix2Y3oE2rXUyi+L+EmTR8f3ZGixQxAKmh3buJcFikthUXLiENhak
KZmMAtNhrYcTMoYI+ZdE6OsspVclLlqxRV8vPcxsqPONxKNgrjlRWAlUkML2wdfM
zdI5jhMPk3hS6FEdsU9ONjH+aI5E7s22TKcv+6otOY13ayoVSMkp74/3nLhsgEs5
y2MqHxGJnJeV6DwL61FkeXI6ixJv93LuIglQ8vfzOYOx/HqL4tdfEiG7bjL1mc/B
JhMfBRkH2Zav3Tj+0filgAhJvd472Q2kImBDQW3R58AuSWaQ3ljOUERjGP5OlJV0
3VXDCL7sPA0bU4fq47fCArmCPGt6Ns5MTMKY9S9DoGZQTDlMdAbqDa8xKV5SW3wY
7FK0PN38CfgI6ALBa4PuJtVVGjCaNc3uhIEqFohKhTpynoEqJ9D53dbeR4wLu08B
j4dt5DO6OgTsEv8heKLY
=t2gC
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to