Bug#894663: transition: wxwidgets3.0
On Fri, Oct 25, 2019 at 09:27:48AM +1300, Olly Betts wrote:
> On Tue, Oct 22, 2019 at 08:58:42AM +1300, Olly Betts wrote:
> > * mrpt was updated but the build failed on mipsel due to running out of
> > memory and it's now entangled in auto-opencv. But it's due for AUTORM
> > on 2019-10-28 so that should resolve itself within a week.
>
> No change here.
The AUTORM happened for mrpt.
> However, checking with "dak rm" on coccia, I discovered four packages
> which build-depend on libwxgtk3.0-dev but without a resulting runtime
> dependency. I've filed bugs against these and set them as blocking this
> bug. They should at least be easy to address.
Fixes for these extra four have now been uploaded and checking again:
olly@coccia:~$ dak rm -Rn -b libwxgtk3.0-dev
[...]
# Broken Depends:
wxsvg: libwxsvg-dev
wxwidgets3.0: libwxgtk-media3.0-dev
# Broken Build-Depends:
amule: libwxgtk3.0-dev
codeblocks: libwxgtk3.0-dev
cubicsdr: libwxgtk3.0-dev
objcryst-fox: libwxgtk3.0-dev
pcsx2: libwxgtk3.0-dev
sooperlooper: libwxgtk3.0-dev
treesheets: libwxgtk3.0-dev
ucblogo: libwxgtk3.0-dev
wxsvg: libwxgtk3.0-dev
Which is just the packages which are only in unstable, so aren't
blockers.
The codeblocks maintainers never responded, but taffit is preparing an
update to the latest upstream release so that at least should be off the
list fairly soon.
I've uploaded wxwidgets3.0 dropping the GTK2 flavour packages, so I
think we can consider this transition complete. I'll leave actually
closing this bug to someone on the release team in case I've missed
something.
Upstream wx are making noises about actually releasing 3.2 early next
year, so we may have another wx transition before bullseye. We've
managed to prune many of the rdeps which are inactive upstream and
unmaintained in Debian, so the next one should hopefully be less work.
Cheers,
Olly
Reply to: