GCC bugzilla: REST API
Joseph Myers
joseph@codesourcery.com
Wed Mar 11 21:17:17 GMT 2020
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
More information about the Gcc
mailing list