Since r1882293 effectively reverted this, I'm guessing there was some
transient error. However, ENOTIME to look into this, particularly as
I didn't get a copy of stderr.
The relevant cron job is:
# Puppet Name: Update our upcoming changes list
SVN=svn
15 4 * * * chronic ~/src/svn/site/tools/generate-upcoming-changes-log.sh
The script is in site/tools/ in the repository.
Cheers,
Daniel
svn-role_at_apache.org wrote on Tue, 06 Oct 2020 04:15 +00:00:
> Author: svn-role
> Date: Tue Oct 6 04:15:36 2020
> New Revision: 1882263
>
> URL: http://svn.apache.org/viewvc?rev=1882263&view=rev
> Log:
> * upcoming.part.html: Automatically regenerated
>
> Modified:
> subversion/site/publish/upcoming.part.html
>
> Modified: subversion/site/publish/upcoming.part.html
> URL:
> http://svn.apache.org/viewvc/subversion/site/publish/upcoming.part.html?rev=1882263&r1=1882262&r2=1882263&view=diff
> ==============================================================================
> --- subversion/site/publish/upcoming.part.html (original)
> +++ subversion/site/publish/upcoming.part.html Tue Oct 6 04:15:36 2020
> @@ -1,179 +1,5 @@
> <!-- Automatically generated by
> ^/subversion/site/tools/generate-upcoming-changes-log.sh -->
> <pre style="border-style: none">
> -Changes in ^/subversion/branches/1.14.x:
> -------------------------------------------------------------------------
> -r1877978 | svn-role |
> 2020-05-21 04:00:13 +0000 (Thu, 21 May 2020) | 7 lines
⋮
> -------------------------------------------------------------------------
> </pre>
>
> <p>Further changes currently under consideration are listed in each
> release line's
>
>
>
Received on 2020-10-07 16:23:01 CEST