On Thu, Oct 24, 2019 at 12:48:08AM +0200, Gianfranco Costamagna wrote:
> the package is going to get kicked out from testing because of this
> bug soon...
It's actually #933469 which will get it auto-removed from testing in
next few days - the AUTORM for this bug wouldn't kick in for a couple
of weeks (at least based on my understanding of the system).
Unfortunately there was a missing mipsel build (because the buildd ran
out of memory) but the auto-opencv transition started before that was
resolved. But now that missing mipsel build can't be addressed without
also updating mrpt for auto-opencv because it currently FTBFS in
unstable.
> > This problem is already solved upstream in the forthcoming mrpt-2.0.0
> > version. I'm marking this as "fixed-upstream" in the meanwhile.
It was waiting for mrpt 2.0.0 for wxwidgets3.0-gtk3 that got us into the
current mess of having two entangled transitions on the go for mrpt. If
we'd just updated the B-Ds of the existing package we'd have got that
out the way weeks (possibly months) ago. Instead mrpt is now the final
package blocking wxwidgets3.0-gtk3's completion.
I understand it's tempting when you're both upstream maintainer and
Debian maintainer to try to do everything via new upstream releases
(it's a trap I've fallen into myself), but there are situations where
just fixing it in Debian really is the better option.
Cheers,
Olly
