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/mine_detector] rawhide: Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
Date: Thu, 16 Jul 2026 08:16:03 GMT [thread overview]
Message-ID: <178418976354.1.18115198561578856041.rpms-mine_detector-59c5ed1c40d1@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/mine_detector
Branch : rawhide
Commit : 59c5ed1c40d12200181c0dc08935ca85f5f0ae7d
Author : Fedora Release Engineering <releng@fedoraproject.org>
Date : 2026-07-16T08:16:00+00:00
Stats : +4/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/mine_detector/c/59c5ed1c40d12200181c0dc08935ca85f5f0ae7d?branch=rawhide
Log:
Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
---
diff --git a/mine_detector.spec b/mine_detector.spec
index 1df64e9..c52f619 100644
--- a/mine_detector.spec
+++ b/mine_detector.spec
@@ -2,7 +2,7 @@ Name: mine_detector
Version: 6.0^20160527
# The version numbering upstream is inconsistent and useless. Here the date of
# the newest source file in the zip file is used to identify the version
-Release: 10%{?dist}
+Release: 11%{?dist}
Summary: Mine Detector, a mine-finding game
Summary(sv): Mine Detector, ett minröjningsspel
@@ -77,6 +77,9 @@ cp -p %{SOURCE8} %{buildroot}%{_mandir}/sv/man1/mine_detector.1
%changelog
+* Thu Jul 16 2026 Fedora Release Engineering <releng@fedoraproject.org> - 6.0^20160527-11
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
+
* Sat Mar 28 2026 Björn Persson <Bjorn@Rombobjörn.se> - 6.0^20160527-10
- Rebuilt because GCC 16.0.1-0.10 broke ALI.
reply other threads:[~2026-07-16 8:16 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=178418976354.1.18115198561578856041.rpms-mine_detector-59c5ed1c40d1@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