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

mark invalid packages for google-cloud-bigquery-storage-core as broken #183

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

conda-forge-daemon
Copy link
Contributor

Hi @conda-forge/google-cloud-bigquery-storage! I am the friendly conda-forge webservice!

I made this PR because I found files in one or more of your packages that are not allowed for that package. Once this PR is merged, the builds listed below will be marked as broken. They will not be installable from the main conda-forge channels, but you will still be able to download them from anaconda.org.

The core team will usually wait a week to merge these PRs. However, we may merge them earlier if we deem the packages below a signifcant security or usability issue.

If you think this PR was made by mistake or is incorrect, please get in touch with the core team in this PR or on gitter!

Information on invalid packages (see the files listed under bad_paths):

noarch/google-cloud-bigquery-storage-core-2.0.0-pyh9f0ad1d_1.tar.bz2:
  bad_paths:
    pyyaml.python.generated:
    - site-packages/PyYAML-5.3.1.dist-info/INSTALLER
  valid: false
noarch/google-cloud-bigquery-storage-core-2.0.1-pyh9f0ad1d_0.tar.bz2:
  bad_paths:
    pyyaml.python.generated:
    - site-packages/PyYAML-5.3.1.dist-info/INSTALLER
  valid: false
noarch/google-cloud-bigquery-storage-core-2.1.0-pyhd3deb0d_0.tar.bz2:
  bad_paths:
    pyyaml.python.generated:
    - site-packages/PyYAML-5.3.1.dist-info/INSTALLER
  valid: false

This job was generated by https://github.com/conda-forge/artifact-validation/actions/runs/401834470.

@parthea
Copy link

parthea commented Jun 17, 2021

@beckermr , ok to close this issue now that the issue has been fixed?

@beckermr
Copy link
Member

I think there is an open question as to whether or not we want to merge this PR to remove the artifacts with the extra files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants