Your message dated Sun, 20 Jul 2014 16:38:58 +0000
with message-id <e1x8u8y-0006to...@franck.debian.org>
and subject line Bug#755418: Removed package(s) from unstable
has caused the Debian Bug report #749993,
regarding multiget: Please update to use wxwidgets3.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.)
--
749993: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Version: 1.2.0-3.1+rm
Dear submitter,
as the package multiget has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/755418
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
