Your message dated Thu, 26 Mar 2015 05:18:36 +0000
with message-id <[email protected]>
and subject line Bug#759068: fixed in pytimechart 1.0.0~rc1-3.1
has caused the Debian Bug report #759068,
regarding pytimechart: 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.)


-- 
759068: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759068
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pytimechart
Version: 1.0.0~rc1-3
Severity: important
Tags: sid jessie
User: [email protected]
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: pytimechart
Source-Version: 1.0.0~rc1-3.1

We believe that the bug you reported is fixed in the latest version of
pytimechart, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Olly Betts <[email protected]> (supplier of updated pytimechart 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 [email protected])


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

Format: 1.8
Date: Thu, 26 Mar 2015 18:01:40 +1300
Source: pytimechart
Binary: pytimechart
Architecture: source all
Version: 1.0.0~rc1-3.1
Distribution: unstable
Urgency: low
Maintainer: Python Applications Packaging Team 
<[email protected]>
Changed-By: Olly Betts <[email protected]>
Description:
 pytimechart - GUI Viewer for Linux kernel traces
Closes: 759068 772507
Changes:
 pytimechart (1.0.0~rc1-3.1) unstable; urgency=low
 .
   * Non-maintainer upload with maintainer's permission.
   * Comment out "workaround bad bg color in ubuntu, with Ambiance theme" as
     this code just segfaults on recent Debian (Closes: #772507), new patch:
     fix-segfault-on-startup.patch
   * Update to use wxPython 3.0 (Closes: #759068), new patch: wx3.patch
Checksums-Sha1:
 02df4c63225002cf01605c30bffc5e905cda2a31 2050 pytimechart_1.0.0~rc1-3.1.dsc
 db301d47e3cd03e1c43a8d5c01dd879b9e696878 6060 
pytimechart_1.0.0~rc1-3.1.debian.tar.xz
 6d7d617a57301da40e9f6c9d23c0feb2a9e6084b 41132 
pytimechart_1.0.0~rc1-3.1_all.deb
Checksums-Sha256:
 93ee7d4db095ac0c3a4c6c12c98aa023411452c982242d19db724fef52e64c62 2050 
pytimechart_1.0.0~rc1-3.1.dsc
 ddbe2ffadcf8eb66d4c6742bb03f9fc4fc4e4eb8b53ae81889945bbb512b72c2 6060 
pytimechart_1.0.0~rc1-3.1.debian.tar.xz
 c65771832f57c99135073cb80706df4f59c1c1462ca01a225ed64e58d67f3f5e 41132 
pytimechart_1.0.0~rc1-3.1_all.deb
Files:
 99be0335e1bc6f1f2a6f13a0c13f2612 2050 python optional 
pytimechart_1.0.0~rc1-3.1.dsc
 c9958de237c2e2f035ee9b4d1dfb0b56 6060 python optional 
pytimechart_1.0.0~rc1-3.1.debian.tar.xz
 8b1ce3210cefb2992bb4ded58d5b39a7 41132 python optional 
pytimechart_1.0.0~rc1-3.1_all.deb

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

iQIcBAEBAgAGBQJVE5RRAAoJEBgUewc7rSsHfNwQALTgry+J7t3xPuzRi7tGfnvo
U8+b596N4B7QYlYtUjmNlhl5QtUjX5BrZAmdQrnGf6xp8qfCNlrZlcQBP2o5hP9s
KpBkV3w328LYfacbt4+8VExNkVT91Kh/OgJkai6OFoVtKapHDjVFrMjG7T99QxPD
euKpJ7yAE5JF4vjwz+2y/9TP4Dmq1nmq61+H/JZutuG7RAHJHDtV/CVYT5kYrECu
s168/XYEQ5tYR0Twc7OdQLRzPkksTTzqU+Q2Ghan+Ewr1Ogh2b00vII9yhobYDL6
nfTiRFreOroszz+dbuOD2VRifpgnh5qHp8Z+FLbd/X82riesx0HnsityKqXti9Qf
fYarPZeqsPkRUu6dumhNk35RKJoqpQ1+Iw16T+qONKnXum7npVMcvEaKsWfrO1P8
U72AessWIGIOpj+xa9AzfagtsxTNtwKmh96lgDz6X4oJXynWT0p2eW5Ls6tIKsFp
rEbIxRw5pJt1X6Y/r1ZLdaZwE7zDSRC7xK6U8qK13GgjT6g91JHPnJjwwc3lDe1H
IjZxL3sGB8eHPkK91oYZSSQ+PXtAfFTfKhIZCHZ8jiyRNGThv75XGp7bqwwIRnxQ
VxIzefqs3Uwb6n/1RCRzHwINWKcLMX2tzSc0W2Cpt1dWlX6MLlj1VeEIubGbWyFg
lFvUNNh6hcLuZ4RuNKbY
=B1OS
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to