[GH-ISSUE #699] License identifier in Cargo.toml #969

Closed
opened 2026-03-15 11:10:38 +03:00 by kerem · 1 comment
Owner

Originally created by @xfgusta on GitHub (Sep 28, 2025).
Original GitHub issue: https://github.com/asciinema/asciinema/issues/699

Pre-submission checks

  • I have searched existing issues and this bug has not been reported yet
  • This is a bug report for asciinema CLI (not player or server)

Bug Description

license = "GPL-3.0"

Should this be GPL-3.0-only or GPL-3.0-or-later? There is a discrepancy in the README, which states “All code is licensed under the GPL, v3 or later” (GPL-3.0-or-later).

Also, the GPL-3.0 identifier is deprecated in recent SPDX versions.

Steps to Reproduce

  1. Read the Cargo.toml file

Expected Behavior

The license in Cargo.toml should use a correct SPDX identifier and match the README.

Operating System

Fedora Linux 42

asciinema CLI Version

3.0.0

Installation Method

Built from source

Terminal Information

No response

Additional Context

No response

Originally created by @xfgusta on GitHub (Sep 28, 2025). Original GitHub issue: https://github.com/asciinema/asciinema/issues/699 ### Pre-submission checks - [x] I have searched existing issues and this bug has not been reported yet - [x] This is a bug report for asciinema CLI (not player or server) ### Bug Description ```toml license = "GPL-3.0" ``` Should this be [`GPL-3.0-only`](https://spdx.org/licenses/GPL-3.0-only.html) or [`GPL-3.0-or-later`](https://spdx.org/licenses/GPL-3.0-or-later.html)? There is a discrepancy in the README, which states “All code is licensed under the GPL, v3 or later” (`GPL-3.0-or-later`). Also, the [`GPL-3.0`](https://spdx.org/licenses/GPL-3.0.html) identifier is deprecated in recent SPDX versions. ### Steps to Reproduce 1. Read the `Cargo.toml` file ### Expected Behavior The license in `Cargo.toml` should use a correct SPDX identifier and match the README. ### Operating System Fedora Linux 42 ### asciinema CLI Version 3.0.0 ### Installation Method Built from source ### Terminal Information _No response_ ### Additional Context _No response_
kerem closed this issue 2026-03-15 11:10:44 +03:00
Author
Owner

@ku1ik commented on GitHub (Sep 29, 2025):

Good catch. Will fix shortly. Thanks!

<!-- gh-comment-id:3345682259 --> @ku1ik commented on GitHub (Sep 29, 2025): Good catch. Will fix shortly. Thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/asciinema#969
No description provided.