public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Dick Marinus <dick@mrns.nl>
To: git-commits@fedoraproject.org
Subject: [rpms/remind] epel9: fix tests
Date: Fri, 21 Aug 2026 13:53:30 GMT	[thread overview]
Message-ID: <178732041090.1.1619361207198851360.rpms-remind-da7530a72e70@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/remind
Branch : epel9
Commit : da7530a72e70a9c43783378d3d83c1b177cca9ad
Author : Dick Marinus <dick@mrns.nl>
Date   : 2025-05-19T19:54:30+02:00
Stats  : +39/-1 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/remind/c/da7530a72e70a9c43783378d3d83c1b177cca9ad?branch=epel9

Log:
fix tests

---
diff --git a/0001-Do-not-use-obsolete-tail-2-syntax.-Instead-use-tail-.patch b/0001-Do-not-use-obsolete-tail-2-syntax.-Instead-use-tail-.patch
new file mode 100644
index 0000000..1ea894a
--- /dev/null
+++ b/0001-Do-not-use-obsolete-tail-2-syntax.-Instead-use-tail-.patch
@@ -0,0 +1,34 @@
+From 098cf4707ab53885ecaf5c0b5d736341d4491f6a Mon Sep 17 00:00:00 2001
+From: Dianne Skoll <dianne@skoll.ca>
+Date: Sat, 17 May 2025 10:59:28 -0400
+Subject: [PATCH] Do not use obsolete "tail +2" syntax.  Instead use "tail
+ -n+2"
+
+Fix courtesy of Dick Marinus.
+---
+ tests/test-rem | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/tests/test-rem b/tests/test-rem
+index e9cd99fa..1906e7dc 100644
+--- a/tests/test-rem
++++ b/tests/test-rem
+@@ -589,13 +589,13 @@ rm -f ../tests/once.timestamp
+ ../src/remind ../tests/test-once.rem >> ../tests/test.out 2>&1
+ ../src/remind ../tests/test-once.rem >> ../tests/test.out 2>&1
+ ../src/remind ../tests/test-once.rem >> ../tests/test.out 2>&1
+-tail +2 ../tests/once.timestamp >> ../tests/test.out 2>&1
++tail -n+2 ../tests/once.timestamp >> ../tests/test.out 2>&1
+ rm -f ../tests/once.timestamp
+ 
+ ../src/remind - < ../tests/test-once.rem >> ../tests/test.out 2>&1
+ ../src/remind - < ../tests/test-once.rem >> ../tests/test.out 2>&1
+ ../src/remind - < ../tests/test-once.rem >> ../tests/test.out 2>&1
+-tail +2 ../tests/once.timestamp >> ../tests/test.out 2>&1
++tail -n+2 ../tests/once.timestamp >> ../tests/test.out 2>&1
+ rm -f ../tests/once.timestamp
+ 
+ # Newlines in calendar output
+-- 
+2.49.0
+

diff --git a/remind.spec b/remind.spec
index 930f237..42f50c8 100644
--- a/remind.spec
+++ b/remind.spec
@@ -1,6 +1,6 @@
 Name:           remind
 Version:        05.00.05
-Release:        2%{?dist}
+Release:        3%{?dist}
 Summary:        Sophisticated calendar and alarm program
 
 # GPL-2.0-only: main software
@@ -19,6 +19,7 @@ Patch:          use-system-libjsonparser.diff
 
 # temporary
 Patch:          remove-timezone-tests-from-compare.patch
+Patch:          0001-Do-not-use-obsolete-tail-2-syntax.-Instead-use-tail-.patch
 
 BuildRequires:  gcc
 BuildRequires:  gnupg2
@@ -144,6 +145,9 @@ make test
 %{_datadir}/pixmaps/tkremind.png
 
 %changelog
+* Mon May 19 2025 Dick Marinus <dick@mrns.nl> - 05.00.05-3
+- Fix tests
+
 * Sat Jan 18 2025 Fedora Release Engineering <releng@fedoraproject.org> - 05.00.05-2
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_42_Mass_Rebuild
 

                 reply	other threads:[~2026-08-21 13:53 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=178732041090.1.1619361207198851360.rpms-remind-da7530a72e70@fedoraproject.org \
    --to=dick@mrns.nl \
    --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