Bug#1092505: transition: opencv
On Fri, 2025-01-31 at 12:53 +0100, Emilio Pozuelo Monfort wrote:
> On 27/01/2025 00:45, M. Zhou wrote:
> > On Tue, 2025-01-14 at 13:19 +0100, Emilio Pozuelo Monfort wrote:
> > >
> > > This sounds good, but let's wait a bit for the Python transition to settle.
> >
> > Ping? The python3.13-default transition seems to be at 100% now.
>
> Sorry, we started the numpy2 transition, which was earlier in the queue, and is
> a blocking transition, hence I didn't want to start this one in parallel as
> there are various conflicts. In the meantime, I've noticed that there are a
> couple of autopkgtest failures on rdeps with the new opencv, can you take a look
> at them?
>
> https://qa.debian.org/excuses.php?experimental=1&package=opencv
No worries. I just hope the new version can enter testing before freeze.
The two CI failures are quite straightforward.
The one for ros-vision-opencv is still due the same "libopnecv_barcode.so
being merged into libopencv_objdetect.so" change. I've filed the bug at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094834
which is very similar to the one for ros-opencv-apps:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092502
The one for visp in fact passed. But pulling both the old opencv 4.6
and the new opencv 4.10 during test caused some stderr noise and
hence the failure. A rebuild should be able to automatically resolve
this.
Reply to: