From: Joseph Myers <joseph@codesourcery.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Overseers mailing list <overseers@sourceware.org>,
<overseers@gcc.gnu.org>, GCC Development <gcc@gcc.gnu.org>
Subject: Re: GCC bugzilla: REST API
Date: Wed, 11 Mar 2020 21:17:17 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2003112057290.30536@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20200311184124.GA683@redhat.com>
On Wed, 11 Mar 2020, Frank Ch. Eigler via Gcc wrote:
> Hi -
>
> > I'm working on a script that will catch the missing email into
> > Bugzilla that are triggered by git commits mentioning a PR.
> > For that I would need the enablement of REST API that was enabled
> > in previous bugzilla instance.
>
> Just for clarity, which REST API was this? Have a test URL we can
> useto smoke-test?
Here's anm example for sourceware bugzilla, where it's also broken, but
used to work.
https://sourceware.org/bugzilla/rest.cgi/bug?product=glibc&resolution=FIXED&target_milestone=2.32&include_fields=id,component,summary
(as used in the list-fixed-bugs.py script to generate a list of bugs that
goes in the glibc NEWS file at release time).
/www/gcc/bugzilla/Bugzilla/Install/Requirements.pm has a list of perl
modules required by various Bugzilla features. It appears new-sourceware
is missing at least JSON::RPC and Test::Taint required for the REST API.
Likely the other features people report are missing are the result of
other such missing modules. Some of those were in what's now the
lib.rhel6-obsolete directory in both GCC and sourceware Bugzilla (going
through the modules there to see what features they might cause to be
missing may be a good idea), but you may want to install relevant modules
from appropriate OS packages if available.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-03-11 21:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 10:22 Martin Liška
2020-03-11 18:41 ` Frank Ch. Eigler
2020-03-11 21:17 ` Joseph Myers [this message]
2020-03-11 23:15 ` Frank Ch. Eigler
2020-03-12 8:27 ` Martin Liška
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.2003112057290.30536@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=fche@redhat.com \
--cc=gcc@gcc.gnu.org \
--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).