Source: multiget Version: 1.2.0-3.1 Severity: important User: freewx-ma...@lists.alioth.debian.org Usertags: wx3.0 Control: block 748169 by -1
Dear maintainer, We're aiming to migrate the archive to using wxwidgets3.0 instead of wxwidgets2.8, and intend to drop wxwidgets2.8 before jessie is released. I've test built multiget with the BD updated to use libwxgtk3.0-dev, and it fails due to API changes in wx, so upstream changes will be required. However, it looks like upstream is no longer active - there hasn't been a new upstream release since multiget was first uploaded to Debian. I wonder if removing multiget would be best, especially since there are several other graphical download managers in Debian. But if you want to take on maintaining the upstream code too, you may find wx upstream's overview of changes since wx2.8 useful: http://docs.wxwidgets.org/3.0/overview_changes_since28.html One of the most common reasons for packages failing to build seems to be that wx3.0 drops compatibility with things which were deprecated in wx2.8 (so for example you now must use wxFD_SAVE not wxSAVE). Updating these should remain compatible with wx2.8, so shouldn't block pushing fixes upstream even if your upstream still cares about supporting wx2.8. Another thing to be aware of is that wx3.0 turns on "WXDEBUG" mode by default, and some applications throw up a lot of assertion failed dialogs due to using the wx API in invalid ways. If you compile your package with -DNDEBUG then such assertions aren't checked, and the same fallbacks which were quietly used in wx2.8 are used instead. If you hit any problems with getting packages working with wxwidgets3.0 which you can't overcome, let me know and I'll try to help. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
