[rpms/perl-Schedule-Cron] f44: 1.07 release

[Andrew Bauer <zonexpertconsulting@outlook.com>]

A new commit has been pushed.

Repo   : rpms/perl-Schedule-Cron
Branch : f44
Commit : 1cc7a4dd95c189c963603ab6ed081c2e523ca9f6
Author : Andrew Bauer <zonexpertconsulting@outlook.com>
Date   : 2026-08-02T16:47:45-05:00
Stats  : +6/-79 in 5 file(s)
URL    : https://src.fedoraproject.org/rpms/perl-Schedule-Cron/c/1cc7a4dd95c189c963603ab6ed081c2e523ca9f6?branch=f44

Log:
1.07 release

---
diff --git a/.gitignore b/.gitignore
index b5d80e1..e4c417f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,3 +3,4 @@
 /Schedule-Cron-1.04.tar.gz
 /Schedule-Cron-1.05.tar.gz
 /Schedule-Cron-1.06.tar.gz
+/Schedule-Cron-1.07.tar.gz

diff --git a/perl-Schedule-Cron.spec b/perl-Schedule-Cron.spec
index 58e1fb3..e02b30e 100644
--- a/perl-Schedule-Cron.spec
+++ b/perl-Schedule-Cron.spec
@@ -2,7 +2,7 @@
 
 Name:      perl-Schedule-Cron
 Summary:   Provides a simple but complete cron like scheduler
-Version:   1.06
+Version:   1.07
 Release:   1%{?dist}
 # Automatically converted from old format: GPL+ or Artistic - review is highly recommended.
 License:   GPL-1.0-or-later OR Artistic-1.0-Perl
@@ -89,6 +89,9 @@ find %{buildroot} -type f -name .packlist -delete
 %{_mandir}/man3/*
 
 %changelog
+* Sun Aug 02 2026 Andrew Bauer <zonexpertconsulting@outlook.com> - 1.07-1
+- 1.07 release
+
 * Mon Jul 20 2026 Andrew Bauer <zonexpertconsulting@outlook.com> - 1.06-1
 - 1.06 release
 

diff --git a/perl-schedule-cron-fix-spelling.patch b/perl-schedule-cron-fix-spelling.patch
deleted file mode 100644
index 8b888ca..0000000
--- a/perl-schedule-cron-fix-spelling.patch
+++ /dev/null
@@ -1,51 +0,0 @@
-Description: spelling fixes
-Origin: vendor
-Author: gregor herrmann <gregoa@debian.org>
-Last-Update: 2017-06-30
-Forwarded: https://rt.cpan.org/Ticket/Display.html?id=122278
-Bug: https://rt.cpan.org/Ticket/Display.html?id=122278
-
---- a/lib/Schedule/Cron.pm
-+++ b/lib/Schedule/Cron.pm
-@@ -543,7 +543,7 @@
- In addition, ranges or lists of names are allowed. 
- 
- An optional sixth column can be used to specify the seconds within the
--minute. If not present, it is implicitely set to "0".
-+minute. If not present, it is implicitly set to "0".
- 
- B<Command specification>
- 
-@@ -683,7 +683,7 @@
- Note that these entries are returned by value and were opbtained from the
- internal list by a deep copy. I.e. you are free to modify it, but this won't
- influence the original entries. Instead use C<update_entry> if you need to
--modify an exisiting crontab entry.
-+modify an existing crontab entry.
- 
- =cut
- 
-@@ -761,7 +761,7 @@
- 
- =item $cron->update_entry($idx,$entry)
- 
--Updates the entry with index C<$idx>. C<$entry> is a hash ref as descibed in
-+Updates the entry with index C<$idx>. C<$entry> is a hash ref as described in
- C<list_entries()> and must contain at least a value C<$entry-E<gt>{time}>. If no
- C<$entry-E<gt>{dispatcher}> is given, then the default dispatcher is used.  This
- method returns the old entry on success, C<undef> otherwise.
-@@ -1811,11 +1811,11 @@
- calculates epoch times for dates given like C<02:50:00 2009/10/25>. Should it
- return the seconds since 1970 for this time happening 'first', or for this time
- in the extra hour ? As it turns out, L<Time::ParseDate> returns the epoch time
--of the first occurence for C<PST8PDT> and for C<MET> it returns the second
--occurence. Unfortunately, there is no way to specify I<which> entry
-+of the first occurrence for C<PST8PDT> and for C<MET> it returns the second
-+occurrence. Unfortunately, there is no way to specify I<which> entry
- L<Time::ParseDate> should pick (until now). Of course, after all, this is
- obviously not L<Time::ParseDate>'s fault, since a simple date specification
--within the DST backswitch period B<is> ambigious. However, it would be nice if
-+within the DST backswitch period B<is> ambiguous. However, it would be nice if
- the parsing behaviour of L<Time::ParseDate> would be consistent across time
- zones (a ticket has be raised for fixing this). Then L<Schedule::Cron>'s
- behaviour within a DST backward switch would be consistent as well.

diff --git a/perl-schedule-cron-fix-unescaped-left-brace.patch b/perl-schedule-cron-fix-unescaped-left-brace.patch
deleted file mode 100644
index 9665ebd..0000000
--- a/perl-schedule-cron-fix-unescaped-left-brace.patch
+++ /dev/null
@@ -1,26 +0,0 @@
-From fabead181f55e8b8ee5729e25d1b3c9327e95b67 Mon Sep 17 00:00:00 2001
-From: Alexandr Ciornii <alexchorny@gmail.com>
-Date: Wed, 4 Jan 2017 15:06:37 +0200
-Subject: [PATCH] Fixes "Unescaped left brace in regex is illegal", RT#117437
-
-
-Bug: https://rt.cpan.org/Public/Bug/Display.html?id=117437
-Bug-Debian: https://bugs.debian.org/826491
-
----
- t/pretty_print_args.t | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/t/pretty_print_args.t b/t/pretty_print_args.t
-index 7a1322e..e50e76b 100644
---- a/t/pretty_print_args.t
-+++ b/t/pretty_print_args.t
-@@ -11,4 +11,4 @@ my @args = (
-            );     
- 
- my $out = join(",",Schedule::Cron->_format_args(@args));
--like($out,qr/\['bla','blub',{.*?'and'\s*=>\s*'HASH\(.*?\)'.*?}\],3,{.*?'blub'\s*=>\s*'bla'.*?}/);
-+like($out,qr/\['bla','blub',\{.*?'and'\s*=>\s*'HASH\(.*?\)'.*?}\],3,\{.*?'blub'\s*=>\s*'bla'.*?}/);
--- 
-2.13.2
-

diff --git a/sources b/sources
index 176a4d3..dd29b1e 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (Schedule-Cron-1.06.tar.gz) = 8d947cf0550a31f27b2086b8d3ff2ea2f31fcc9794e5199c8f41d34a32ed700abd06eec22a6291f21e97b1170c10d290eaa406f9b69301d9f4daf846f3079094
+SHA512 (Schedule-Cron-1.07.tar.gz) = e4d4b325e30b3a2576ec0625fe6fc009d73c9c71ca192a372fdf88deab3f42fc2e19c4c0b7ff65c2b37d8f5a057531daa46e08940626f25d8f3841d131c7d8d9