Skip to content

New rule for g10 license, updated fsf-unlimited-no-warranty - #5335

Open
hesa wants to merge 2 commits into
aboutcode-org:developfrom
hesa:hesa-fix-3934-g10-license
Open

hesa wants to merge 2 commits into
aboutcode-org:developfrom
hesa:hesa-fix-3934-g10-license

Conversation

@hesa

@hesa hesa commented Sep 25, 2026

Copy link
Copy Markdown
Contributor

Fixes #3934

Tasks

  • Reviewed contribution guidelines
  • PR is descriptively titled 📑 and links the original issue above 🔗
  • Tests pass -- look for a green checkbox ✔️ a few minutes after opening your PR
    Run tests locally to check for errors.
  • Commits are in uniquely-named feature branch and has no merge conflicts 📁
  • Updated documentation pages (if applicable)
  • Updated CHANGELOG.rst (if applicable)

Signed-off-by: Henrik Sandklef <hesa@sandklef.com>
forcing text "as a special exception the author gives"

Signed-off-by: Henrik Sandklef <hesa@sandklef.com>

@AyanSinhaMahapatra AyanSinhaMahapatra left a comment •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks++ @hesa see comments for your consideration wrt.:

  • deprecating rules vs changing the text
  • using required_phrases vs minimum_coverage

Also lots of text failures which are related to your changes and we need to update test expectations there.
For example:
SCANCODE_REGEN_TEST_FIXTURES=yes pytest -vvs tests/packagedcode/test_debian_copyright.py::TestDebianCopyrightLicenseDetection::test_debian_parse_copyright_file_detailed_main_g_gnupg2_stable_copyright --test-suite=validate
All of the related test failures seem to be for debian copyright files where we need to update expectations.

notes: small variant
---

This file is free software; as a special exception the author gives

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We cannot change rule text content, instead we should deprecate a rule and create new rules as required as these are useful reference for detections.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Otherwise folks using an older version and getting a match with this rule would be confused about the matched text. We ourselves also use this for diff btw

is_required_phrase: yes
---

This program is free software; {{as a special exception the author gives}}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if this a good idea to keep "author" in required phrases, as this could change, though I have not found any cases where other authors are used. Setting a high minimum_coverage is another option, when there aren't great required phrases.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

G10's license identified as fsf-unlimited-no-warranty

2 participants