[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1092505: transition: opencv



On 15/02/2025 01:53, M. Zhou wrote:
On Fri, 2025-02-14 at 11:48 +0100, Emilio Pozuelo Monfort wrote:
Control: tags -1 confirmed

The numpy 2 transition shouldn't be a blocker, as numpy rdeps can migrate to
testing freely. As it's taking a while to get it sorted out, let's go ahead with
this one.
Thanks, and uploaded to unstable. Among release architectures,
only riscv64 is still building.
There's a couple of autopkgtest failures, as we have mentioned in the past. The 
rebuilds for those in sid don't help, because reverse-autopkgtests are ran 
against testing, in order to ensure that if opencv migrates on its own (which is 
possible) it wouldn't break e.g. ros-image-pipeline/testing. If those 
combinations actually break, then opencv should probably gain appropriate breaks 
to prevent that situation, and that will also help the autopkgtests. If that is 
not an issue and is a test-only problem, then let us know and we can workaround 
it on the britney or CI side.
Cheers,
Emilio


Reply to: