public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Michal Schorm <mschorm@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/ballz] rawhide: Fix SPDX license tag: 'LicenseRef-Callaway-BSD' -> 'BSD-3-Clause'
Date: Wed, 15 Jul 2026 18:04:24 GMT [thread overview]
Message-ID: <178413866491.1.7783618878559251174.rpms-ballz-b5840361830a@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/ballz
Branch : rawhide
Commit : b5840361830abd87920c687616ee72fbed74c451
Author : Michal Schorm <mschorm@redhat.com>
Date : 2026-07-14T23:03:18+02:00
Stats : +5/-3 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/ballz/c/b5840361830abd87920c687616ee72fbed74c451?branch=rawhide
Log:
Fix SPDX license tag: 'LicenseRef-Callaway-BSD' -> 'BSD-3-Clause'
License analysis:
- Examined 'BSD-license' (the main license file, referenced by 'COPYING')
- 'COPYING' simply states: "All files are licensed under the BSD license.
The BSD license is found in the file BSD-license."
- Copyright holders: Olof Naessen and Per Larsson (2007)
- The license text contains three clauses:
1. Redistributions of source code must retain copyright notice
2. Redistributions in binary form must reproduce copyright notice
3. "Neither the name of the Darkbits nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission"
- Clause 3 is the "no-endorsement" clause, making this BSD-3-Clause
The correct SPDX identifier is 'BSD-3-Clause'.
Co-Authored-By: Claude AI <noreply@anthropic.com>
---
diff --git a/ballz.spec b/ballz.spec
index 82739fb..bdb1011 100644
--- a/ballz.spec
+++ b/ballz.spec
@@ -1,9 +1,8 @@
Name: ballz
Version: 1.0.4
-Release: 19%{?dist}
+Release: 20%{?dist}
Summary: B.A.L.L.Z. - platform/puzzle game where you control a rolling ball
-# Automatically converted from old format: BSD - review is highly recommended.
-License: LicenseRef-Callaway-BSD
+License: BSD-3-Clause
URL: https://gitlab.com/groups/ballz
Source0: %{name}-%{version}.tar.gz
BuildRequires: gcc-c++
@@ -52,6 +51,9 @@ appstream-util validate-relax --nonet %{buildroot}%{_metainfodir}/*.appdata.xml
%changelog
+* Tue Jul 14 2026 Michal Schorm <mschorm@redhat.com> - 1.0.4-20
+- Fix SPDX license tag: 'LicenseRef-Callaway-BSD' -> 'BSD-3-Clause'
+
* Fri Jan 16 2026 Fedora Release Engineering <releng@fedoraproject.org> - 1.0.4-19
- Rebuilt for https://fedoraproject.org/wiki/Fedora_44_Mass_Rebuild
reply other threads:[~2026-07-15 18:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178413866491.1.7783618878559251174.rpms-ballz-b5840361830a@fedoraproject.org \
--to=mschorm@redhat.com \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox