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

pypi/pypi/-/matplotlib/3.4.1 #10483

Merged
merged 6 commits into from
May 18, 2021
Merged

Conversation

clearlydefinedbot
Copy link
Contributor

Type: Auto

Summary:
pypi/pypi/-/matplotlib/3.4.1

Details:
Add OTHER license

Resolution:
Auto-generated curation. Newly harvested version 3.4.1 matches existing version 3.3.4.
Matching metadata: registryData.info.license: 'PSF'

Affected definitions:

@clearlydefinedbot
Copy link
Contributor Author

You can review the change introduced to the full definition at ClearlyDefined.

@AE49 AE49 self-assigned this Apr 6, 2021
@AE49
Copy link
Contributor

AE49 commented Apr 6, 2021

@capfei This could be Declared as PSF-2.0. PyPI metadata is PSF. The license is a close enough match with references to PSF and Python customized, but main licensing text was not changed. https://matplotlib.org/stable/users/license.html. Thoughts?

@AE49
Copy link
Contributor

AE49 commented Apr 20, 2021

Same as #10486. Changing to PSF-2.0

@saheel1115
Copy link

@AE49 Thanks a lot for taking this up!

After your changes, looks like the ClearlyDefined curation check was unsuccessful. How can we resolve that and complete the pull request?

--
Saheel (dev at microsoft)

@capfei capfei closed this Apr 22, 2021
@capfei capfei reopened this Apr 22, 2021
@nellshamrell nellshamrell reopened this Apr 26, 2021
@github-actions github-actions bot added the merge conflict GitHub Action bot will auto add/remove this label when there's a conflict. label Apr 27, 2021
@capfei capfei closed this Apr 27, 2021
@capfei capfei reopened this Apr 27, 2021
@github-actions
Copy link

Conflicts have been resolved.

@github-actions github-actions bot removed the merge conflict GitHub Action bot will auto add/remove this label when there's a conflict. label Apr 27, 2021
@capfei capfei closed this Apr 27, 2021
@capfei capfei reopened this Apr 27, 2021
@capfei
Copy link
Member

capfei commented Apr 27, 2021

@saheel1115 Validation is still failing for PSF-2.0 due to an issue with the bot. Will merge when resolved. Tracking in #11048.

@capfei capfei added the issue There is a tooling or process based issue or question. label Apr 27, 2021
@saheel1115
Copy link

@capfei Thanks for the update! I'll pass it forward to others in my team.

@clearlydefinedbot
Copy link
Contributor Author

We discovered some errors in this curation when validating it:

2.2.2 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.0.0 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.0.2 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.2.2 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.3.0 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.3.1 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.3.2 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.3.3 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.3.4 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.4.1 licensed.declared with value "PSF-2.0" is not SPDX compliant

@github-actions github-actions bot added the merge conflict GitHub Action bot will auto add/remove this label when there's a conflict. label May 10, 2021
@clearlydefinedbot
Copy link
Contributor Author

We discovered some errors in this curation when validating it:

2.2.2 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.0.0 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.0.2 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.2.2 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.3.0 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.3.1 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.3.2 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.3.3 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.3.4 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.4.0 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.4.1 licensed.declared with value "PSF-2.0" is not SPDX compliant

1 similar comment
@clearlydefinedbot
Copy link
Contributor Author

We discovered some errors in this curation when validating it:

2.2.2 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.0.0 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.0.2 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.2.2 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.3.0 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.3.1 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.3.2 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.3.3 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.3.4 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.4.0 licensed.declared with value "PSF-2.0" is not SPDX compliant
3.4.1 licensed.declared with value "PSF-2.0" is not SPDX compliant

@github-actions github-actions bot removed the merge conflict GitHub Action bot will auto add/remove this label when there's a conflict. label May 17, 2021
@github-actions
Copy link

Conflicts have been resolved.

@ariel11 ariel11 merged commit 2d76aa0 into master May 18, 2021
@ariel11 ariel11 deleted the clearlydefinedbot_210405_202835.158 branch May 18, 2021 20:40
@AE49 AE49 removed their assignment May 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue There is a tooling or process based issue or question.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants