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] rawhide: 4.3.7 entry
Date: Mon, 13 Jul 2026 08:05:46 GMT [thread overview]
Message-ID: <178392994604.1.16001090639356134480.rpms-rubygem-pango-af0248200417@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/rubygem-pango
Branch : rawhide
Commit : af02482004176d8ee9371625122037a4230fbe25
Author : Mamoru TASAKA <mtasaka@fedoraproject.org>
Date : 2026-07-13T17:05:36+09:00
Stats : +7/-4 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/rubygem-pango/c/af02482004176d8ee9371625122037a4230fbe25?branch=rawhide
Log:
4.3.7 entry
---
diff --git a/rubygem-pango.spec b/rubygem-pango.spec
index 10df933..15941bd 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.6
+Version: 4.3.7
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\.6|>= 4.3.6|' %{gem_name}-%{version}.gemspec
+sed -i -e 's|= 4\.3\.7|>= 4.3.7|' %{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
+* Mon Jul 13 2026 Mamoru TASAKA <mtasaka@fedoraproject.org> - 4.3.7-1
+- 4.3.7
+
* Sat Apr 04 2026 Mamoru TASAKA <mtasaka@fedoraproject.org> - 4.3.6-1
- 4.3.6
diff --git a/sources b/sources
index 904e9c5..2c6e7c4 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (pango-4.3.6.gem) = 7513c2bf48990d923da07b2e0e36314db8d89d232572edf3c7a5da9b89db88f2c42852bf33cce6649a1ac1f4eb303992e9ea3a9899c2e8b9ba1dbee44894e737
-SHA512 (pango-4.3.6-test-missing-files.tar.gz) = 4169e837de4bb146ba3b2c02d689435ed8ac1e2e9d2289c4b22be9d8f310abf8429d96977e8da5a73ce3d75fc16c4622cbaf07849d3540ed1ff4494888de5434
+SHA512 (pango-4.3.7.gem) = 2b3535b7e61df735157d243d7f486bf05ebb92c3bb37e151ce7f180d3c2ac83022c663b6d8727146fbd03728623fe5ba5ac2c351599e6f30f9115b7e84689cbe
+SHA512 (pango-4.3.7-test-missing-files.tar.gz) = f53be0630a9728f00bf4b9373c9dc1e1629b817c1847aecf45bed6501db796899a3d2c591e1744e4a99b3f117b7f600a7dff2d911937cdcbfc0bb94423eec2f4
reply other threads:[~2026-07-13 8:05 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=178392994604.1.16001090639356134480.rpms-rubygem-pango-af0248200417@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