public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Fedora Release Engineering <releng@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/perl-Encode] rawhide: Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
Date: Thu, 16 Jul 2026 12:37:13 GMT [thread overview]
Message-ID: <178420543306.1.3842570041653351475.rpms-perl-Encode-c466bb117f0a@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/perl-Encode
Branch : rawhide
Commit : c466bb117f0ad566248aa6574f55f30fc6196c53
Author : Fedora Release Engineering <releng@fedoraproject.org>
Date : 2026-07-16T12:37:09+00:00
Stats : +4/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/perl-Encode/c/c466bb117f0ad566248aa6574f55f30fc6196c53?branch=rawhide
Log:
Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
---
diff --git a/perl-Encode.spec b/perl-Encode.spec
index 7f8b3d0..3401cc8 100644
--- a/perl-Encode.spec
+++ b/perl-Encode.spec
@@ -8,7 +8,7 @@ Version: %{cpan_version}
# perl-encoding sub-package has independent version which does not change
# often and consecutive builds would clash on perl-encoding NEVRA. This is the
# same case as in perl.spec.
-Release: 524%{?dist}
+Release: 525%{?dist}
Summary: Character encodings in Perl
# ucm: license in this repository can be ingored based on
# https://gitlab.com/fedora/legal/fedora-license-data/-/issues/30#note_1435176617
@@ -216,6 +216,9 @@ make test
%{_libexecdir}/%{name}
%changelog
+* Thu Jul 16 2026 Fedora Release Engineering <releng@fedoraproject.org> - 4:3.24-525
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
+
* Thu Apr 30 2026 Jitka Plesnikova <jplesnik@redhat.com> - 4:3.24-524
- 3.24 bump (rhbz#2463946)
reply other threads:[~2026-07-16 12:37 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=178420543306.1.3842570041653351475.rpms-perl-Encode-c466bb117f0a@fedoraproject.org \
--to=releng@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