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.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.

I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory. You can also examine the workflow logs for more detail.

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

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.

To add some context for reviewers:

• sqlite-feedstock was recently changed to compile sqlite with DQS=0 (sqlite v3.49.0 build fix and compile-time options update sqlite-feedstock#124)
• diskcache upstream does not work with DQS=0, due to its use of double-quoted strings. There is a PR to address this (Support sqlite builds with DQS=off grantjenks/python-diskcache#311), but there has been no movement in a few weeks.

Changes to either sqlite-feedstock or diskcache upstream are likely to take longer. To me, patching the diskcache feedstock seems like a reasonable option in the interim.

And one bump for @pmlandwehr @xhochy, thanks for maintining this feedstock!

Ping @conda-forge/diskcache; it would be nice to have this merged.

I believe this should no longer be necessary since the merge of conda-forge/sqlite-feedstock#132