From: Joseph Myers <joseph@codesourcery.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: Overseers mailing list <overseers@sourceware.org>,
<overseers@gcc.gnu.org>, Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: No more notifications of wwwdocs commits?
Date: Mon, 9 Mar 2020 14:05:51 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2003091359130.26872@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20200308223040.GA94530@elastic.org>
On Sun, 8 Mar 2020, Frank Ch. Eigler wrote:
> Hi -
>
> > There definitely are several things not working properly as far as
> > our web page infrastructure goes:
> >
> > - https://gcc.gnu.org/pipermail/gcc-cvs-wwwdocs/2020/date.html
> > misses the last two commits:
> >
> > commit 09a7a9579b59619ea3f601b821ec8b9dd3fe708e (HEAD -> master,
> > commit 8a562ce34e441587b87d5e5bc2ebb58f4ce630b9
>
> OK, will look into it, though the git-email processing is done
> by the adacore hooks AIUI.
No, wwwdocs uses its own post-receive hook (a symlink to
/www/gcc/wwwdocs-checkout/bin/post-receive - at some point the symlink had
somehow become a copy that was thus missing the last commit, I've now
restored the symlink). That calls
/sourceware/libre/infra/bin/post-receive-email, which is missing on new
sourceware. I don't know if other projects might be using
post-receive-email as well.
The logs (/www/gcc/updatelog) also show mhc segfaulting.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-03-09 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 23:41 Gerald Pfeifer
2020-03-08 17:42 ` Christopher Faylor
2020-03-08 22:04 ` Gerald Pfeifer
2020-03-08 22:30 ` Frank Ch. Eigler
2020-03-09 14:05 ` Joseph Myers [this message]
2020-03-09 17:59 ` Christopher Faylor
2020-03-09 21:02 ` Joseph Myers
2020-03-09 3:33 ` Frank Ch. Eigler
2020-03-09 12:18 ` gcc.gnu.org web site updates broken (was: No more notifications of wwwdocs commits?) Gerald Pfeifer
2020-03-09 14:14 ` Frank Ch. Eigler
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=alpine.DEB.2.21.2003091359130.26872@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=fche@elastic.org \
--cc=gerald@pfeifer.com \
--cc=overseers@gcc.gnu.org \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).