-
Notifications
You must be signed in to change notification settings - Fork 628
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
Can't publish AGPL-3.0-or-later crate #1278
Comments
This is ultimately a duplicate of rust-lang/cargo#4930 -- cargo and crates.io still use SPDX 2.4 and AGPL-3.0-or-later is SPDX 3.0. The documentation for this has been improved but cargo's docs now ride the trains so the improvement has only made it to the beta cargo docs at https://doc.rust-lang.org/beta/cargo/reference/manifest.html#package-metadata. |
|
I've just pushed license-exprs v1.4.0 to crates.io with support for identifiers from the SPDX License List v3.1. What's the procedure for bumping our dependencies. I'd guess we want to bump this repo, and then, once that was live, update the Cargo docs and code? Should we reopen this issue to track? Get new issues? An existing associated Cargo issue might be rust-lang/cargo#4930. |
Reopened! I'd love a PR that updates license-exprs! |
Filed as #1457. |
1457: Cargo.toml: Bump license-exprs to 1.4.0 r=carols10cents And then update `Cargo.lock` with: ```console $ cargo build ``` This bumps us from the SPDX License List 2.4 to 3.1. Some 2.4 identifiers have since been deprecated by SPDX, but none of them have been removed, so it should be safe to deploy this before bumping Cargo and its docs (which mention 2.4 since rust-lang/cargo#4898). Fixes #1278.
The fix has been merged and deployed, thank you @wking !!! |
Fails with
error: api errors: unknown license or other term: AGPL-3.0-or-later; see http://opensource.org/licenses for options, and http://spdx.org/licenses/ for their identifiers
, yet it is clearly listed on http://spdx.org/licenses/The text was updated successfully, but these errors were encountered: