Ok, sorry, forgot my last message, you already mentioned the new problem: > But now that missing mipsel build can't be addressed without > also updating mrpt for auto-opencv because it currently FTBFS in > unstable.
It's a shame, but I think that perhaps I'll just leave mrpt to be removed from testing. Anyway, mrpt-2 comes with many different packages so (if I recall it right...) the procedure would be similar, it will have to go through the "New queue" (sigh). Right now, addressing all the opencv4 changes in the mrpt-1.x branch would take me too much time, which will be better invested in going for the 2.0.0 version. Thanks for all your help, any other comments or advice will be much appreciated!
