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

local crate without license: failed to parse synthesized license expression #171

Closed
kamulos opened this issue Oct 29, 2021 · 2 comments · Fixed by #172
Closed

local crate without license: failed to parse synthesized license expression #171

kamulos opened this issue Oct 29, 2021 · 2 comments · Fixed by #172
Labels
bug Something isn't working

Comments

@kamulos
Copy link

kamulos commented Oct 29, 2021

Describe the bug
Having a local crate without a license used to work without a problem. Now with the newest version of cargo-about I get an error and cannot find any information in the documentation about it.

The error is:

error: failed to parse synthesized license expression
  ┌─ xyz 0.1.0.license:1:1
  │
1 │
  │ ^ empty expression

To Reproduce
Steps to reproduce the behavior:

  1. Create a new project with cargo new xyz
  2. Copy the default about.hbs file
  3. Run cargo about generate about.hbs with the newest version of cargo-about

Expected behavior
It should not break the (until now) flawlessly working CI. Alternatively there should be documentation how to solve this.

@kamulos kamulos added the bug Something isn't working label Oct 29, 2021
@Jake-Shadle
Copy link
Member

You can workaround this by adding a LicenseRef-<some_name> for now, but I'll need to add a config that can just ignore local crates that don't have a stated license.

@Jake-Shadle
Copy link
Member

More details on the custom SPDX identifiers is here https://embarkstudios.github.io/cargo-deny/checks/licenses/cfg.html#spdx-identifiers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants