public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Mamoru TASAKA <mtasaka@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/cairo-dock-plug-ins] nightly: update to the latest git
Date: Mon, 20 Jul 2026 07:34:17 GMT	[thread overview]
Message-ID: <178453285744.1.7002438561415583077.rpms-cairo-dock-plug-ins-e880ec6f9002@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/cairo-dock-plug-ins
Branch : nightly
Commit : e880ec6f90026856636ed41cc0b9ad9ffee098c7
Author : Mamoru TASAKA <mtasaka@fedoraproject.org>
Date   : 2026-07-20T16:34:06+09:00
Stats  : +12/-5 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/cairo-dock-plug-ins/c/e880ec6f90026856636ed41cc0b9ad9ffee098c7?branch=nightly

Log:
update to the latest git

---
diff --git a/cairo-dock-plug-ins.spec b/cairo-dock-plug-ins.spec
index 9d57fd6..aaeda6d 100644
--- a/cairo-dock-plug-ins.spec
+++ b/cairo-dock-plug-ins.spec
@@ -4,8 +4,8 @@
 %global	core_least_ver	3.6.101
 
 %global	use_git	1
-%global	gitdate	20260719
-%global	githash	1d14d651f4a6c8185a7ad35bba4cf57827d0a22b
+%global	gitdate	20260720
+%global	githash	e00c6c40579a5ea7a07418ea04d080160bfdc63d
 %global	shorthash	%(c=%{githash} ; echo ${c:0:7})
 
 %global	tarballver	%{mainver}%{?use_git:-%{gitdate}git%{shorthash}}
@@ -35,7 +35,13 @@ Release:		%{baserelease}%{?alphatag}%{?dist}%{flagrel}
 Summary:		Plug-ins files for Cairo-Dock
 
 # SPDX confirmed
-License:		GPL-3.0-or-later AND GPL-2.0-or-later AND LGPL-2.1-or-later AND GPL-2.0-only
+License:		%{shrink:
+	GPL-3.0-or-later AND
+	GPL-2.0-or-later AND
+	LGPL-2.1-or-later AND
+	GPL-2.0-only AND
+	CC-BY-SA-4.0
+}
 URL:			http://glx-dock.org/
 #Source0:		http://launchpad.net/cairo-dock-plug-ins/%%{urlver}/%%{mainver}/+download/cairo-dock-plugins-%%{mainver}.tar.gz
 # Some contents removed: see https://bugzilla.redhat.com/show_bug.cgi?id=1178912
@@ -43,7 +49,7 @@ Source0:		cairo-dock-plugins-fedora-%{tarballver}.tar.gz
 # Source0 is created from Source1
 Source1:		cairo-dock-plug-ins-create-fedora-tarball.sh
 
-BuildRequires:  gcc-c++
+BuildRequires:	gcc-c++
 BuildRequires:	cmake
 BuildRequires:	extra-cmake-modules
 BuildRequires:	gettext
@@ -296,6 +302,7 @@ mkdir documents-dbus/Dbus
 cp -a Dbus/demos \
 	documents-dbus/Dbus/
 cp -a \
+	CC-SA-4.0 \
 	LGPL-2 \
 	LICENSE \
 	copyright \

diff --git a/sources b/sources
index 24ffe0b..6c87898 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (cairo-dock-plugins-fedora-3.6.101-20260719git1d14d65.tar.gz) = 2d0b439eb0cb2b730773c5d2a77e3161beda12a60b398cec0b72c357513e12ab53d040ad6919b95a0afa000967913bfd4ff674aa7795119a857680fe006ace20
+SHA512 (cairo-dock-plugins-fedora-3.6.101-20260720gite00c6c4.tar.gz) = 7ec3b45e39a68405a66b0ed8e05f34049072fce17455278f0177b813e4805602bb8b4471b0da060aee08bdd5de4e4e56adf131a32027ab901fb46c6d58a2e123

             reply	other threads:[~2026-07-20  7:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20  7:34 Mamoru TASAKA [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-07-19 13:13 [rpms/cairo-dock-plug-ins] nightly: update to the latest git Mamoru TASAKA
2026-07-11 13:44 Mamoru TASAKA
2026-07-09  1:29 Mamoru TASAKA

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=178453285744.1.7002438561415583077.rpms-cairo-dock-plug-ins-e880ec6f9002@fedoraproject.org \
    --to=mtasaka@fedoraproject.org \
    --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