Skip to content

Rebuild for libgdal_core 3.11#332

Closed
regro-cf-autotick-bot wants to merge 1 commit intoconda-forge:mainfrom
regro-cf-autotick-bot:rebuild-libgdal_core311-0-1_hf4ee94
Closed

Rebuild for libgdal_core 3.11#332
regro-cf-autotick-bot wants to merge 1 commit intoconda-forge:mainfrom
regro-cf-autotick-bot:rebuild-libgdal_core311-0-1_hf4ee94

Conversation

@regro-cf-autotick-bot
Copy link
Copy Markdown
Contributor

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

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 @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/cf-scripts/actions/runs/15186307659 - please use this URL for debugging.

@conda-forge-admin
Copy link
Copy Markdown
Contributor

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/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/15186763411. Examine the logs at this URL for more detail.

@akrherz
Copy link
Copy Markdown
Contributor

akrherz commented May 22, 2025

Error appears to be:

+ rio --help
Traceback (most recent call last):
  File "/home/conda/feedstock_root/build_artifacts/.../bin/rio", line 7, in <module>
    from rasterio.rio.main import main_group
  File "/home/conda/feedstock_root/build_artifacts/.../lib/python3.9/site-packages/rasterio/rio/main.py", line 42, in <module>
    from importlib_metadata import entry_points
ImportError: cannot import name 'entry_points' from 'importlib_metadata' (unknown location)

@ocefpaf
Copy link
Copy Markdown
Member

ocefpaf commented May 22, 2025

See conda-forge/importlib_metadata-feedstock#148

I'm pulling those packages now.

@akrherz akrherz added the automerge Merge the PR when CI passes label May 22, 2025
@conda-forge-admin
Copy link
Copy Markdown
Contributor

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

  • linter: passed
  • azure: failed

Thus the PR was not passing and not merged.

@akrherz akrherz removed the automerge Merge the PR when CI passes label May 22, 2025
@akrherz
Copy link
Copy Markdown
Contributor

akrherz commented May 26, 2025

I don't see anything upstream with rasterio supporting GDAL 3.11, so this may be stuck until there's an upstream release...

@theroggy
Copy link
Copy Markdown

Is there something known that is blocking this, because it would be great to be able to combine rasterio with GDAL 3.11?

@akrherz
Copy link
Copy Markdown
Contributor

akrherz commented Jul 16, 2025

Is there something known that is blocking this

Last I checked, upstream had no release supporting GDAL 3.11

@akrherz
Copy link
Copy Markdown
Contributor

akrherz commented Sep 17, 2025

marked as draft as I see no simple path forward. Awaiting upstream release...

@akrherz akrherz force-pushed the rebuild-libgdal_core311-0-1_hf4ee94 branch from 5b69c23 to 8a5b7d5 Compare September 17, 2025 18:22
@akrherz akrherz closed this Sep 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants