search

conda-forge / r-gdalcubes-feedstock

A conda-smithy repository for r-gdalcubes.
BSD 3-Clause "New" or "Revised" License
0 stars 5 forks source link

Rebuild for libgdal36 #41

Closed regro-cf-autotick-bot closed 2 years ago

regro-cf-autotick-bot commented 2 years ago

This PR has been triggered in an effort to update libgdal36.

Notes and instructions for merging this PR:

  1. Please merge the PR only after the tests have passed.
  2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase code>@<space/conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/3484624343, please use this URL for debugging.

conda-forge-linter commented 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.

zklaus commented 2 years ago

@conda-forge-admin, please restart ci

mbargull commented 2 years ago

It managed to pick up an "older" build of libgdal that didn't have pcre2 added as a build dependency but still linked to it. Since pcre2 wasn't in requirements/host yet, it didn't apply the pinning from conda-forge-pinning and as such it already used/linked to the newer 10.40 build. Let's restart once again and if it still picks up those older builds, let's think about other solutions to it.

mbargull commented 2 years ago

@conda-forge-admin, please restart ci

zklaus commented 2 years ago

Time for a plan B. I guess the two options are marking libgdal-3.6.0-h12400bf_2 broken or providing a repodata patch?

akrherz commented 2 years ago

@zklaus in theory, builds 0, 1, and 2 would all be broken in this manner. The dep-solver is picking build 2 here because of some conflict with build 3 and higher, which has the pcre2 requirement.

mbargull commented 2 years ago

Re solver conflict: We don't have the 4.1.x branch on r-base-feedstock in abi_migration_branches and thus it didn't get picked up for the pcre2=10.40 rebuild. I'll fix that on the r-base side. (give me an hour or two; I'm AFK for a brief moment)

mbargull commented 2 years ago

We should have a r-base=4.1 build for pcre2=10.40 is a couple of hours.

mbargull commented 2 years ago

Time for a plan B. I guess the two options are marking libgdal-3.6.0-h12400bf_2 broken or providing a repodata patch?

I wouldn't bother with marking any build as broken. I wouldn't want you to then want to end up marking all libgdal versions/builds as broken :smile: : https://github.com/conda-forge/gdal-feedstock/issues/690 Let's rather fix the current builds and go on from there.

akrherz commented 2 years ago

@conda-forge-admin, please restart ci

zklaus commented 2 years ago

Nice, thanks, @mbargull, @akrherz. @conda-forge/r-gdalcubes, this is ready for review.

dbast commented 2 years ago

@conda-forge-admin, please rerender

dbast commented 2 years ago

@conda-forge-admin, please rerender

regro-cf-autotick-bot commented 2 years ago

Due to the bot-rerun label I'm closing this PR. I will make another one as appropriate. This was generated by https://github.com/regro/autotick-bot/actions/runs/3614494680

dbast commented 2 years ago

uh. the bot closed for re-run :(