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/java-latest-openjdk] rawhide: Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
Date: Thu, 16 Jul 2026 04:11:11 GMT [thread overview]
Message-ID: <178417507119.1.16372687060766472839.rpms-java-latest-openjdk-bdf926dbd8d6@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/java-latest-openjdk
Branch : rawhide
Commit : bdf926dbd8d68bc2530e5c6e8f7df2a22ed73d6c
Author : Fedora Release Engineering <releng@fedoraproject.org>
Date : 2026-07-16T04:11:08+00:00
Stats : +4/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/java-latest-openjdk/c/bdf926dbd8d68bc2530e5c6e8f7df2a22ed73d6c?branch=rawhide
Log:
Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
---
diff --git a/java-latest-openjdk.spec b/java-latest-openjdk.spec
index 7ee9db8..45109ea 100644
--- a/java-latest-openjdk.spec
+++ b/java-latest-openjdk.spec
@@ -1191,7 +1191,7 @@ Version: %{newjavaver}.%{buildver}
# This package needs `.0` as prefix of Release so as to not conflict on install with
# java-X-openjdk. I.e. when latest rolling release is also an LTS release packaged as
# java-X-openjdk. See: https://bugzilla.redhat.com/show_bug.cgi?id=1647298
-Release: %{?eaprefix}0.%{rpmrelease}%{?extraver}%{?dist}
+Release: %{?eaprefix}0.%{rpmrelease}%{?extraver}%{?dist}.1
# java-1.5.0-ibm from jpackage.org set Epoch to 1 for unknown reasons
# and this change was brought into RHEL-4. java-1.5.0-ibm packages
# also included the epoch in their virtual provides. This created a
@@ -2553,4 +2553,7 @@ exit 0
%endif
%changelog
+* Thu Jul 16 2026 Fedora Release Engineering <releng@fedoraproject.org> - 1:26.0.1.0.8-0.2.1
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
+
%autochangelog
reply other threads:[~2026-07-16 4:11 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=178417507119.1.16372687060766472839.rpms-java-latest-openjdk-bdf926dbd8d6@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