Hi Emilio,
* Emilio Pozuelo Monfort [2025-02-17 09:55]:
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 p
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.
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 t
Control: tags -1 confirmed
On 31/01/2025 12:53, 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 transit
Hi Mo,
* M. Zhou [2025-01-31 10:40]:
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:
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-d
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 wa
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.
Hi Mo,
* M. Zhou [2025-01-11 14:04]:
OK now I'm unblocked from building the unvalidated packages on amd64.
Now I've validated all reverse dependencies of opencv, and only 2 out
of 39 sources FTBFS due to the transition. The bugs are filed correspondingly.
Please let me know whenever it is appr
On 11/01/2025 20:04, M. Zhou wrote:
OK now I'm unblocked from building the unvalidated packages on amd64.
Now I've validated all reverse dependencies of opencv, and only 2 out
of 39 sources FTBFS due to the transition. The bugs are filed correspondingly.
Please let me know whenever it is appropr
OK now I'm unblocked from building the unvalidated packages on amd64.
Now I've validated all reverse dependencies of opencv, and only 2 out
of 39 sources FTBFS due to the transition. The bugs are filed correspondingly.
Please let me know whenever it is appropriate to upload opencv to unstable.
am
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: ope...@packages.debian.org
Control: affects -1 + src:opencv
User: release.debian@packages.debian.org
Usertags: transition
Our current opencv version in sid is quite ancient. I intend to make
the transition towards the latest 4.10 versi
12 matches
Mail list logo
