Bug 2416948 - Possible incorrect license tag for zstd package in Fedora
Summary: Possible incorrect license tag for zstd package in Fedora
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: zstd
Version: 43
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Pádraig Brady
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-11-25 07:20 UTC by Fuminobu TAKEYAMA
Modified: 2025-11-25 14:29 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-11-25 14:29:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Fuminobu TAKEYAMA 2025-11-25 07:20:29 UTC
In Fedora 43 (and also other versions), the SPEC file for the zstd package currently states:

> License: BSD-3-Clause AND GPL-2.0-only

However, the official zstd repository (README.md and license headers) for version v1.5.7 includes the following statement:

> This repository represents the reference implementation, provided as an open-source dual BSD OR GPLv2 licensed C library, and a command line utility producing and decoding .zst, .gz, .xz and .lz4 files.

https://github.com/facebook/zstd/blob/v1.5.7/README.md

> This source code is licensed under both the BSD-style license (found in the   
> LICENSE file in the root directory of this source tree) and the GPLv2 (found   
> in the COPYING file in the root directory of this source tree).   
> You may select, at your option, one of the above-listed licenses.

https://github.com/facebook/zstd/blob/v1.5.7/lib/compress/zstd_compress.c

This indicates that zstd is dual-licensed under BSD-3-Clause OR GPL-2.0-only, not AND.


* Is there an intentional reason Fedora uses BSD-3-Clause AND GPL-2.0-only for this package?
* If this is not intentional, should the tag be corrected to BSD-3-Clause OR GPL-2.0-only?

Reproducible: Always

Comment 1 Pádraig Brady 2025-11-25 14:29:21 UTC
Agreed as per https://docs.fedoraproject.org/en-US/legal/license-field/#_special_rules_for_or_expressions
I pushed a change of AND -> OR


Note You need to log in before you can comment on or make changes to this bug.