Source: xtensor Followup-For: Bug #1052882 Control: fixed 1052882 0.24.7-1 This bug is weird, in the sense that xtensor 0.24.3-2 in testing failed its test against xsimd 10.0.0-3 from unstable.
So why then did the migration daemon allow xsimd to migrate from unstable to testing?