Source: freqtweak Version: 0.7.2-4 Severity: important Tags: sid jessie User: [email protected] 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 attempted to rebuild freqtweak by updating the BD to libwxgtk3.0-dev but it the build fails due to various wx API changes. It looks like freqtweak is unmaintained upstream - the last release was in July 2009 (nearly 5 years ago), and the last email to their mailing list which got a reply was the same month. The popcon stats show 89 installs of which only 9 have been used recently: http://qa.debian.org/popcon.php?package=freqtweak So I wonder if removing freqtweak from Debian is the most sensible option? But if you're willing to take over upstream maintenance of freqtweak, then 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. Cheers, Olly -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
