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/rubygem-pango] f45: 4.3.9 entry
Date: Sun, 06 Sep 2026 03:32:23 GMT [thread overview]
Message-ID: <178866554381.1.9705911830530875408.rpms-rubygem-pango-5005ea50cce3@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/rubygem-pango
Branch : f45
Commit : 5005ea50cce34ad87f91a4ee3324c88d4858ceb3
Author : Mamoru TASAKA <mtasaka@fedoraproject.org>
Date : 2026-09-06T12:32:02+09:00
Stats : +7/-4 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/rubygem-pango/c/5005ea50cce34ad87f91a4ee3324c88d4858ceb3?branch=f45
Log:
4.3.9 entry
---
diff --git a/rubygem-pango.spec b/rubygem-pango.spec
index 8d078a1..e30d115 100644
--- a/rubygem-pango.spec
+++ b/rubygem-pango.spec
@@ -12,7 +12,7 @@
Summary: Ruby binding of pango-1.x
Name: rubygem-%{gem_name}
-Version: 4.3.8
+Version: 4.3.9
Release: 1%{?dist}
# SPDX confirmed
# LGPL-2.1-or-later: gemspec
@@ -80,7 +80,7 @@ rubygem-%{gem_name}
mv ../%{gem_name}-%{version}.gemspec .
# Allow ruby-gnome2 no less than ones
-sed -i -e 's|= 4\.3\.8|>= 4.3.8|' %{gem_name}-%{version}.gemspec
+sed -i -e 's|= 4\.3\.9|>= 4.3.9|' %{gem_name}-%{version}.gemspec
# Remove unneeded rake runtime dependency
sed -i %{gem_name}-%{version}.gemspec \
@@ -177,6 +177,9 @@ ruby -Ilib:test:%{buildroot}%{gem_extdir_mri} ./test/run-test.rb \
%exclude %{gem_instdir}/Rakefile
%changelog
+* Sun Sep 6 2026 Mamoru TASAKA <mtasaka@fedoraproject.org> - 4.3.9-1
+- 4.3.9
+
* Sun Aug 30 2026 Mamoru TASAKA <mtasaka@fedoraproject.org> - 4.3.8-1
- 4.3.8
diff --git a/sources b/sources
index ad3d152..efd42e3 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (pango-4.3.8.gem) = 90593e19b7ddc93b17c91f368461a08b645906949c5e0b05a49c0fb0b3ef0053c0cb99f7d0d26b4a105190c75e3026b71a5b14b2594ddf28e6dce659402ef256
-SHA512 (pango-4.3.8-test-missing-files.tar.gz) = f25603daa648dafa6a23769afb23969fd9895cfea1f7ce8dee23f24af1f934a9bcfa80e598c8d48ebfc24b85b2f54f477ac0ddc66047585b228d44f12b9e9c28
+SHA512 (pango-4.3.9.gem) = ee1de1fa65645a2eedafc87faa767ebc799c7c0652873e4bd45d4458214e0706b6a2d7380fa44b038c0b7c1477899cae1eab29ea74dc54615f6acec59db6825d
+SHA512 (pango-4.3.9-test-missing-files.tar.gz) = 197a7df195e846d83105cd9092a55f65a436f9d3d27c818d1f0d8e9773e4c84a9d73cd7efba54cac390a98ee1d5df841204337991475fe261c79ce73e0432b3a
reply other threads:[~2026-09-06 3:32 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=178866554381.1.9705911830530875408.rpms-rubygem-pango-5005ea50cce3@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