This is running as a cronjob on the "old" hardware. I no longer have access
to disable it. I thought that the plan was to decommission that hardware, but
currently it seems to be doing zombie impressions, shuffling onwards, not
properly alive but not properly dead yet either...
On Sat, Nov 02, 2019 at 03:08:17AM +0000, Perl 5 commit summary wrote:
> Perl 5 commit summary, activity since Wednesday
> No activity.
This is true, in that it's pulling from git://perl5.git.perl.org/perl.git
and nothing is moving there. As I noted in another e-mail, given this:
$ host perl5.git.perl.org
perl5.git.perl.org is an alias for git.perl.space.
git.perl.space has address 184.108.40.206
to me it would seem that if the CNAME perl5.git.perl.org changed
(not something I control)
to point to a machine that plans to stick around
(not something I own)
which then runs the mirror that we currently have,
then everything would work.
Meanwhile, the cron on the new hardware is definitely running, as I see
that the local repository now has this commit:
Author: Karl Williamson <firstname.lastname@example.org>
Date: Thu Oct 31 19:23:09 2019 -0600
Rmv more deprecated characlassify/case change macros
These were missed by 059703b088f44d5665f67fba0b9d80cad89085fd.
but mails it (tries to) send to the list vanish into the ether.
Not delivered, but not bouncing either. Whilst the same script "just works"
from the old hardware, no problems.
Mails the same script generates 24 hours earlier that are sent direct to
me from the new hardware arrive.
#11906 Look at the error message! Look at the error message!
implores Klortho, but I have no error message.