From 936d91e41c87671bd3b861960ec109f337e95289 Mon Sep 17 00:00:00 2001
From: Matt Simerson <matt@tnpi.net>
Date: Wed, 13 Mar 2024 00:05:56 -0700
Subject: [PATCH] rename backends

---
 DEVELOP.md                                        | 4 ++--
 MANIFEST.SKIP                                     | 2 +-
 lib/Mail/DMARC.pm                                 | 2 +-
 t/12.Report.Store.SQL.t                           | 2 +-
 t/{travis => }/backends/mail-dmarc.sql.Pg.ini     | 0
 t/{travis => }/backends/mail-dmarc.sql.SQLite.ini | 0
 t/{travis => }/backends/mail-dmarc.sql.mysql.ini  | 0
 7 files changed, 5 insertions(+), 5 deletions(-)
 rename t/{travis => }/backends/mail-dmarc.sql.Pg.ini (100%)
 rename t/{travis => }/backends/mail-dmarc.sql.SQLite.ini (100%)
 rename t/{travis => }/backends/mail-dmarc.sql.mysql.ini (100%)

diff --git a/DEVELOP.md b/DEVELOP.md
index 6a43bc34..a388254b 100644
--- a/DEVELOP.md
+++ b/DEVELOP.md
@@ -45,9 +45,9 @@ Visit your fork on the GitHub web site. On the main page of your fork is a ***Pu
 
 # Check build status:
 
-[![Build Status](https://travis-ci.org/msimerson/mail-dmarc.png?branch=master)](https://travis-ci.org/msimerson/mail-dmarc)
+[![Build Status](https://github.com/msimerson/mail-dmarc/actions/workflows/ci.yml/badge.svg)](https://github.com/msimerson/mail-dmarc/actions/workflows/ci.yml)
 
-Travis automatically runs build tests when commits are pushed to GitHub, and sends notifications to the author(s) in case of failure. For everyone else, checking the build status after a push request is merged is a good idea.
+GitHub Actions automatically runs build tests when commits are pushed to GitHub, and sends notifications to the author(s) in case of failure. For everyone else, checking the build status after a push request is merged is a good idea.
 
 # Release
 
diff --git a/MANIFEST.SKIP b/MANIFEST.SKIP
index 89a4e269..9f09c474 100644
--- a/MANIFEST.SKIP
+++ b/MANIFEST.SKIP
@@ -8,9 +8,9 @@
 ^_build
 ^blib
 ^Makefile$
+^Makefile.old$
 ^Build$
 ^MANIFEST\.bak$
 ^MYMETA.
 dmarc_reports.sqlite
 t/reports-test.sqlite
-t/travis
diff --git a/lib/Mail/DMARC.pm b/lib/Mail/DMARC.pm
index eacb3b35..7a130252 100644
--- a/lib/Mail/DMARC.pm
+++ b/lib/Mail/DMARC.pm
@@ -583,7 +583,7 @@ The DMARC spec is lengthy and evolving, making correctness a moving target. In c
 
 Providing an implementation of DMARC that SMTP utilities can utilize will aid DMARC adoption.
 
-The list of dependencies appears long because of reporting. If this module is used without reporting, the number of dependencies not included with perl is about 5. See the [Prereq] versus [Prereq / Recommends] sections in dist.ini.
+The list of dependencies appears long because of reporting. If this module is used without reporting, the number of dependencies not included with perl is about 5.
 
 =head2 Maintainable
 
diff --git a/t/12.Report.Store.SQL.t b/t/12.Report.Store.SQL.t
index 4bc58bd2..c6a7b6ae 100644
--- a/t/12.Report.Store.SQL.t
+++ b/t/12.Report.Store.SQL.t
@@ -45,7 +45,7 @@ use_ok($mod);
 my $sql = $mod->new;
 isa_ok( $sql, $mod );
 
-my $backend_dir = './t/travis/backends';
+my $backend_dir = './t/backends';
 opendir( my $dir, $backend_dir ) || die "Unable to view backends in $backend_dir";
 # The general gist of the tests is:
 #  test query mechanisms
diff --git a/t/travis/backends/mail-dmarc.sql.Pg.ini b/t/backends/mail-dmarc.sql.Pg.ini
similarity index 100%
rename from t/travis/backends/mail-dmarc.sql.Pg.ini
rename to t/backends/mail-dmarc.sql.Pg.ini
diff --git a/t/travis/backends/mail-dmarc.sql.SQLite.ini b/t/backends/mail-dmarc.sql.SQLite.ini
similarity index 100%
rename from t/travis/backends/mail-dmarc.sql.SQLite.ini
rename to t/backends/mail-dmarc.sql.SQLite.ini
diff --git a/t/travis/backends/mail-dmarc.sql.mysql.ini b/t/backends/mail-dmarc.sql.mysql.ini
similarity index 100%
rename from t/travis/backends/mail-dmarc.sql.mysql.ini
rename to t/backends/mail-dmarc.sql.mysql.ini