Skip to content

treewide: update licenses#30080

Open
feckert wants to merge 10 commits into
openwrt:masterfrom
TDT-AG:pr/20260722-treewide-licenses
Open

treewide: update licenses#30080
feckert wants to merge 10 commits into
openwrt:masterfrom
TDT-AG:pr/20260722-treewide-licenses

Conversation

@feckert

@feckert feckert commented Jul 22, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

📦 Package Details

Maintainer:

Description:

libjaylink: replace deprecated license GPL-2.0+ with GPL-2.0-or-later
igmpproxy: The license 'GPL-2.0+' is marked deprecated. Use instead 'GPL-2.0-or-later' identifier.
libnetfilter-cthelper: The license 'GPL-2.0+' is marked deprecated. Use instead 'GPL-2.0-or-later' identifier.
libnetfilter-cttimeout: The license 'GPL-2.0+' is marked deprecated. Use instead 'GPL-2.0-or-later' identifier.
libnetfilter-log: The license 'GPL-2.0+' is marked deprecated. Use instead 'GPL-2.0-or-later' identifier.
rpcd-mod-wireguard: The license 'LGPL-2.1+' is marked deprecated. Use instead 'LGPL-2.1-or-later' identifier.
xz: use correct SPDX license name
openssh: fix BSD license identifier with a valid one
nmap: Replace non-SPDX-compliant license identifiers with SPDX-compliant notation
zoneinfo: use SPDX valid identifier Unlicense instead of non valid identifier Public-Domain

@feckert
xz: use correct SPDX license name
6c5065b 
The value 'Public-Domain' is not a correct SPDX identifier so remove
them. In addition, the SPDX license GPL-2.0 is still missing, which is
hereby corrected.

Signed-off-by: Florian Eckert <fe@dev.tdt.de>
@openwrt

openwrt Bot commented Jul 22, 2026 •
edited
Loading

Copy link
Copy Markdown

Formality Check: Suggestions Available

We completed the verification flow. Please review the formatting overview logs below.

⚠️ STYLISTIC WARNINGS & SUGGESTIONS

Package Release Audit:

  • ⚠️ Package utils/xz content changed without a PKG_RELEASE or version bump. Please increment PKG_RELEASE by 1 (or bump PKG_VERSION/PKG_SOURCE_DATE and reset PKG_RELEASE to 1) so users receive the update.
  • Do not increment release for minor changes. Cosmetic edits (e.g., typos in comments, copyright updates, formatting/whitespace), changing the package maintainer (PKG_MAINTAINER), or updating source download info (PKG_SOURCE_URL / PKG_HASH) do not require incrementing PKG_RELEASE.
  • ⚠️ Package utils/rpcd-mod-wireguard content changed without a PKG_RELEASE or version bump. Please increment PKG_RELEASE by 1 (or bump PKG_VERSION/PKG_SOURCE_DATE and reset PKG_RELEASE to 1) so users receive the update.
  • Do not increment release for minor changes. Cosmetic edits (e.g., typos in comments, copyright updates, formatting/whitespace), changing the package maintainer (PKG_MAINTAINER), or updating source download info (PKG_SOURCE_URL / PKG_HASH) do not require incrementing PKG_RELEASE.
  • ⚠️ Package libs/libnetfilter-log content changed without a PKG_RELEASE or version bump. Please increment PKG_RELEASE by 1 (or bump PKG_VERSION/PKG_SOURCE_DATE and reset PKG_RELEASE to 1) so users receive the update.
  • Do not increment release for minor changes. Cosmetic edits (e.g., typos in comments, copyright updates, formatting/whitespace), changing the package maintainer (PKG_MAINTAINER), or updating source download info (PKG_SOURCE_URL / PKG_HASH) do not require incrementing PKG_RELEASE.
  • ⚠️ Package libs/libnetfilter-cttimeout content changed without a PKG_RELEASE or version bump. Please increment PKG_RELEASE by 1 (or bump PKG_VERSION/PKG_SOURCE_DATE and reset PKG_RELEASE to 1) so users receive the update.
  • Do not increment release for minor changes. Cosmetic edits (e.g., typos in comments, copyright updates, formatting/whitespace), changing the package maintainer (PKG_MAINTAINER), or updating source download info (PKG_SOURCE_URL / PKG_HASH) do not require incrementing PKG_RELEASE.
  • ⚠️ Package libs/libnetfilter-cthelper content changed without a PKG_RELEASE or version bump. Please increment PKG_RELEASE by 1 (or bump PKG_VERSION/PKG_SOURCE_DATE and reset PKG_RELEASE to 1) so users receive the update.
  • Do not increment release for minor changes. Cosmetic edits (e.g., typos in comments, copyright updates, formatting/whitespace), changing the package maintainer (PKG_MAINTAINER), or updating source download info (PKG_SOURCE_URL / PKG_HASH) do not require incrementing PKG_RELEASE.
  • ⚠️ Package net/igmpproxy content changed without a PKG_RELEASE or version bump. Please increment PKG_RELEASE by 1 (or bump PKG_VERSION/PKG_SOURCE_DATE and reset PKG_RELEASE to 1) so users receive the update.
  • Do not increment release for minor changes. Cosmetic edits (e.g., typos in comments, copyright updates, formatting/whitespace), changing the package maintainer (PKG_MAINTAINER), or updating source download info (PKG_SOURCE_URL / PKG_HASH) do not require incrementing PKG_RELEASE.
  • ⚠️ Package libs/libjaylink content changed without a PKG_RELEASE or version bump. Please increment PKG_RELEASE by 1 (or bump PKG_VERSION/PKG_SOURCE_DATE and reset PKG_RELEASE to 1) so users receive the update.
  • Do not increment release for minor changes. Cosmetic edits (e.g., typos in comments, copyright updates, formatting/whitespace), changing the package maintainer (PKG_MAINTAINER), or updating source download info (PKG_SOURCE_URL / PKG_HASH) do not require incrementing PKG_RELEASE.
  • ⚠️ Package net/openssh content changed without a PKG_RELEASE or version bump. Please increment PKG_RELEASE by 1 (or bump PKG_VERSION/PKG_SOURCE_DATE and reset PKG_RELEASE to 1) so users receive the update.
  • Do not increment release for minor changes. Cosmetic edits (e.g., typos in comments, copyright updates, formatting/whitespace), changing the package maintainer (PKG_MAINTAINER), or updating source download info (PKG_SOURCE_URL / PKG_HASH) do not require incrementing PKG_RELEASE.
  • ⚠️ Package net/nmap content changed without a PKG_RELEASE or version bump. Please increment PKG_RELEASE by 1 (or bump PKG_VERSION/PKG_SOURCE_DATE and reset PKG_RELEASE to 1) so users receive the update.
  • Do not increment release for minor changes. Cosmetic edits (e.g., typos in comments, copyright updates, formatting/whitespace), changing the package maintainer (PKG_MAINTAINER), or updating source download info (PKG_SOURCE_URL / PKG_HASH) do not require incrementing PKG_RELEASE.
  • ⚠️ Package utils/zoneinfo content changed without a PKG_RELEASE or version bump. Please increment PKG_RELEASE by 1 (or bump PKG_VERSION/PKG_SOURCE_DATE and reset PKG_RELEASE to 1) so users receive the update.
  • Do not increment release for minor changes. Cosmetic edits (e.g., typos in comments, copyright updates, formatting/whitespace), changing the package maintainer (PKG_MAINTAINER), or updating source download info (PKG_SOURCE_URL / PKG_HASH) do not require incrementing PKG_RELEASE.

Something broken? Consider reporting an issue.
Running version f3161d5 deployed on 2026-07-22 02:15:51 CEST

feckert added 7 commits July 22, 2026 16:17
@feckert
rpcd-mod-wireguard: replace deprecated LGPL-2.1+ with LGPL-2.1-or-later
c53f745 
The license 'LGPL-2.1+' is marked deprecated. Use instead
'LGPL-2.1-or-later' identifier.

 https://spdx.org/licenses/LGPL-2.1+.html

Signed-off-by: Florian Eckert <fe@dev.tdt.de>
@feckert
libnetfilter-log: replace deprecated GPL-2.0+ with GPL-2.0-or-later
a84cb27 
The license 'GPL-2.0+' is marked deprecated. Use instead
'GPL-2.0-or-later' identifier.

https://spdx.org/licenses/GPL-2.0+.html

Signed-off-by: Florian Eckert <fe@dev.tdt.de>
@feckert
libnetfilter-cttimeout: replace deprecated GPL-2.0+ with GPL-2.0-or-l…
8ad48f7 
…ater

The license 'GPL-2.0+' is marked deprecated. Use instead
'GPL-2.0-or-later' identifier.

https://spdx.org/licenses/GPL-2.0+.html

Signed-off-by: Florian Eckert <fe@dev.tdt.de>
@feckert
libnetfilter-cthelper: replace deprecated GPL-2.0+ with GPL-2.0-or-later
d2c3970 
The license 'GPL-2.0+' is marked deprecated. Use instead
'GPL-2.0-or-later' identifier.

https://spdx.org/licenses/GPL-2.0+.html

Signed-off-by: Florian Eckert <fe@dev.tdt.de>
@feckert
igmpproxy: replace deprecated GPL-2.0+ with GPL-2.0-or-later
fcaca6f 
The license 'GPL-2.0+' is marked deprecated. Use instead
'GPL-2.0-or-later' identifier.

https://spdx.org/licenses/GPL-2.0+.html

Signed-off-by: Florian Eckert <fe@dev.tdt.de>
@feckert
libjaylink: replace deprecated GPL-2.0+ with GPL-2.0-or-later
e62b15c 
The license 'GPL-2.0+' is marked deprecated. Use instead
'GPL-2.0-or-later' identifier.

https://spdx.org/licenses/GPL-2.0+.html

Signed-off-by: Florian Eckert <fe@dev.tdt.de>
@feckert
openssh: fix BSD license identifier with a valid one
6d7d711 
The situation here is complicated. The OpenSSH project combines different
licenses. However, the fact is that the name 'BSD' used here for the
license name is not SPDX-compliant.

It is therefore replaced by the valid SPDX licenses BSD-2-Clause and
BSD-3-Clause.

Signed-off-by: Florian Eckert <fe@dev.tdt.de>
@feckert
feckert force-pushed the pr/20260722-treewide-licenses branch from 59ff0bf to 074972a Compare July 22, 2026 14:18
feckert added 2 commits July 22, 2026 16:19
@feckert
nmap: replace non SPDX license identifiers with SPDX compliant notation
080ddb4 
Since this license is not included on the official SPDX License List, it is
referenced in practice as 'NPSL-0.95' or 'NPSL-0.94' but not
'NPSL-0.94-or-NPSL-0.95'.

While we're at it, let's remove the old 'NPSL-0.94', since the source code
uses only 'NPSL-0.95' in the LICENSE file.

Signed-off-by: Florian Eckert <fe@dev.tdt.de>
@feckert
zoneinfo: use SPDX valid identifier Unlicense instead of Public-Domain
2993538 
Replace the 'Public-Domain' not SPDX valid license identifier with the
valied SPDX 'Unlicense' indentifiert.

Signed-off-by: Florian Eckert <fe@dev.tdt.de>
@feckert
feckert force-pushed the pr/20260722-treewide-licenses branch from 074972a to 2993538 Compare July 22, 2026 14:24
@feckert feckert changed the title Pr/20260722 treewide licenses treewide: update licenses Jul 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@feckert