Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cryptography v35.0.0 #70

Conversation

regro-cf-autotick-bot
Copy link
Contributor

It is very likely that the current package version for this feedstock is out of date.
Notes for merging this PR:

  1. Feel free to push to the bot's branch to update this PR if needed.
  2. The bot will almost always only open one PR per version.
    Checklist before merging this PR:
  • Dependencies have been updated if changed: see upstream
  • Tests have passed
  • Updated license if changed and license_file is packaged

Note that the bot will stop issuing PRs if more than 3 Version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.

NEW: If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our new bot automerge feature to your feedstock!

Closes: #69

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. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable.
Finally, 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/1289500339, please use this URL for debugging

Here is a list of all the pending dependencies (and their versions) for this repo. Please double check all dependencies before merging.

Name Upstream Version Current Version
cryptography-vectors 35.0.0 Anaconda-Server Badge

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: false to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis of the source code shows no discrepancy between the library's imports and the package's stated requirements in the meta.yaml.

@conda-forge-linter
Copy link

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.

@h-vetinari
Copy link
Member

Blocked on conda-forge/cryptography-vectors-feedstock#51, which is mergeable already

@ocefpaf
Copy link
Member

ocefpaf commented Sep 30, 2021

@conda-forge-admin, please restart ci

@ocefpaf ocefpaf added the automerge Merge the PR when CI passes label Sep 30, 2021
@github-actions
Copy link
Contributor

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

I considered the following status checks when analyzing this PR:

  • linter: passed
  • drone: passed
  • travis: passed
  • azure: failed

Thus the PR was not passing and not merged.

@h-vetinari
Copy link
Member

Errors on osx-arm:

  error: failed to run custom build command for `pyo3 v0.14.5`

  Caused by:
    process didn't exit successfully: `/private/tmp/pip-req-build-vsun04ep/src/rust/target/release/build/pyo3-39f30afe5a4dc8d5/build-script-build` (exit status: 1)
    --- stdout
    cargo:rerun-if-env-changed=PYO3_CROSS
    cargo:rerun-if-env-changed=PYO3_CROSS_LIB_DIR
    cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_VERSION

    --- stderr
    error: failed to parse PYO3_CROSS_PYTHON_VERSION
    caused by:
      - 0: expected major.minor version

Seems like the last line of

  script:
    - export PYO3_CROSS_INCLUDE_DIR=$PREFIX/include    # [build_platform != target_platform]
    - export PYO3_CROSS_LIB_DIR=$SP_DIR/../            # [build_platform != target_platform]
    - export PYO3_CROSS_PYTHON_VERSION=$python         # [build_platform != target_platform]

isn't doing what it's supposed to?

CC @isuruf, since you wrote that.

@h-vetinari
Copy link
Member

Hey @conda-forge/help-osx-arm64, it would be cool if we can get the new cryptography version out to users. I'd even suggest merging the PR as is and fixing osx-arm later...

@erykoff
Copy link

erykoff commented Oct 11, 2021

It looks like this line is wrong:

- export PYO3_CROSS_PYTHON_VERSION=$python # [build_platform != target_platform]

It's supposed to be set to the major.minor of the python version (e.g. 3.8 or 3.9). I'm not sure how to access this from the conda forge magic variables.

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

I see that this PR has conflicts, and I'm the only committer. I'm going to close this PR and will make another one as appropriate. This was generated by https://github.com/regro/autotick-bot/actions/runs/1330413420

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Merge the PR when CI passes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants