Closed traversaro closed 2 years ago
Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found it was in an excellent condition.
Thanks @hmaarrfk for removing the only existing patch, indeed this can be dropped thanks to https://github.com/opencv/opencv/pull/20386 .
Nice. yeah. tryinf to help with other config when I have time too.
Seems like we need to add a similar tesseract line for windows. are you able to do that?
Seems like we need to add a similar tesseract line for windows. are you able to do that?
Done: https://github.com/traversaro/opencv-feedstock/commit/04098806fd6f0e1ba4337504738bcf79b6588c7d .
@conda-forge-admin, please rerender
fyi @wolfv @Tobias-Fischer as this could result in requiring rebuild on the RoboStack side.
This will trigger a new CI, but probably we can remove the file https://github.com/traversaro/opencv-feedstock/blob/patch-2/recipe/20386-SetTotalBytesLimit-one-arg.patch, is that ok for you @hmaarrfk ?
Hi! This is the friendly conda-forge automerge bot!
Commits were made to this PR after the automerge
label was added. For security reasons, I have disabled automerge by removing the automerge
label. Please add the automerge
label again (or ask a maintainer to do so) if you'd like to enable automerge again!
I know the windows builds are slow, but thye are often the ones that fail for some random reason. Trying to ensure they pass before breaking things in the system.
Hi! This is the friendly conda-forge automerge bot!
I considered the following status checks when analyzing this PR:
Thus the PR was passing and merged! Have a great day!
Thanks @hmaarrfk !
@hmaarrfk not sure if you saw it, but in the post-merge CI job there was a spurious failure: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=439846&view=logs&jobId=4b3757f9-99c5-5891-6c0c-93d7030cdf7d .
I tried pressing the rerun button
I did not see the failure. I think when yo urestarted it destroyed the old build log. Seems to be working now!
Note that this triggered a migration: https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/2392
On RoboStack, we have libopencv in the mutex package, so we should be safe ...
I tried to use the existing
libopencv
4.5.3 package with Visual Studio 2022, but it does not work as theOpenCVConfig.cmake
file has some logic that needed to be update explicity for Visual Studio 2022 (see https://github.com/robotology/robotology-superbuild/pull/995#issuecomment-1010144950). As4.5.5
is the latest release, I updated directly to the last one.Checklist
0
(if the version changed)conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)