libtool-exception-2.0 and Libtool-exception weirdness

Open Beginner friendly
#265 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
backend

Research direction

Start by tracing how Flame looks up license aliases for the two identifiers in the issue, then inspect the relevant license metadata and alias definitions. Determine whether these names represent the same license or separate licenses, as the issue specifies. Update the alias data accordingly and verify that flame -of json license libtool-exception-2.0 and flame -of json license Libtool-exception identify the intended license consistently.

Written by the indexing model from the issue text.

Description

Flame confuses libtool-exception-2.0 with Libtool-exception (see below)

  • if it is the same license, remove alias
  • if separate licenses, fix the aliases
$ flame -of json license libtool-exception-2.0
{
    "queried_license": "libtool-exception-2.0",
    "identified_license": "libtool-exception-2.0",
    "identified_license_scancode_key": "libtool-exception-2.0",
    "identifications": [],
    "ambiguities": [],
    "updated_license": "libtool-exception-2.0",
    "license_parsed": "libtool-exception-2.0",
    "updates": []
}
$ flame -of json license Libtool-exception
{
    "queried_license": "Libtool-exception",
    "identified_license": "Libtool-exception",
    "identified_license_scancode_key": "libtool-exception-2.0",
    "identifications": [],
    "ambiguities": [],
    "updated_license": "Libtool-exception",
    "license_parsed": "Libtool-exception",
    "updates": []
}
Dominant language
Python
Stars
7
Forks
3
Avg merge
2h 53m
Merged PRs (30d)
7

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/foss-licenses

All issues in aboutcode-org/foss-licenses

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.