libtool-exception-2.0 and Libtool-exception weirdness
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aboutcode-org/foss-licenses
-
Expanding "or later" licenses breaks the validatorPossibly taken @hesa claimed this 1 day ago. Open
aboutcode-org/foss-licenses#278 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Check data integrity with scancode license databasePossibly taken @hesa claimed this 2 days ago. Open
aboutcode-org/foss-licenses#277 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
aboutcode-org/foss-licenses#266 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
aboutcode-org/foss-licenses#256 ·
Maintainers usually reply within 1 day
-
Collaboration with LicenseLynx and other resourcesMay be free again @hesa claimed this 169 days ago, and no pull request is open. Open
aboutcode-org/foss-licenses#233 · 1 comment · 2 reactions · 1 assignee ·
Maintainers usually reply within 1 day
All issues in aboutcode-org/foss-licenses
Similar issues
-
Internal ErrorOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
frappe/frappe_docker#2071 ·
Maintainers usually reply within 1 day
-
bug python
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
traceloop/openllmetry#4717 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
The-Pocket/PocketFlow#161 ·
-
comp/desktop P2 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#157702 ·
Maintainers usually reply within 1 day
-
scibench_physics / scibench_chemistry: a correct answer scores 0 when the unit has a power of tenPossibly taken @BahaaMattar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
EvolvingLMMs-Lab/lmms-eval#1699 ·
Maintainers usually reply within 1 day