From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] pybugz call for testers
Date: Tue, 10 Apr 2012 16:17:45 -0500 [thread overview]
Message-ID: <20120410211745.GA9144@linux1> (raw)
In-Reply-To: <4F849BDA.8030802@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
On Tue, Apr 10, 2012 at 10:45:14PM +0200, "Paweł Hajdan, Jr." wrote:
> On 4/10/12 7:54 PM, William Hubbs wrote:
> > I have updated pybugz-9999 to work with the xmlrpc interface of
> > bugzilla.
>
> Cool, thank you for working on that.
>
> > I can name a couple of issues that are api limitations that we can't do
> > anything about:
> >
> > - you can't search on cc: or keywords fields.
>
> That's going to be a problem for arch testing needs (e.g. STABLEREQ
> keyword and x86@ cc-ed). How about doing the searches "the old way" that
> allowed the above.
That is not so easy to do since we have completely gotten rid of the old
method of communicating with bugzilla. That method was not reliable and
had broken several times with bugzilla upgrades, but using the web
services will be more stable.
Here is the documentation for their search command [1]. It would
probably be better for us to open a bug against bugzilla itself and
request those changes be put in the api.
What are your thoughts?
William
[1] http://www.bugzilla.org/docs/4.2/en/html/api/Bugzilla/WebService/Bug.html#search
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-04-10 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 17:54 [gentoo-dev] pybugz call for testers William Hubbs
2012-04-10 20:45 ` "Paweł Hajdan, Jr."
2012-04-10 21:17 ` William Hubbs [this message]
2012-04-11 5:03 ` Mike Gilbert
2012-04-11 11:55 ` "Paweł Hajdan, Jr."
2012-04-13 3:19 ` Mike Gilbert
2012-04-13 4:32 ` "Paweł Hajdan, Jr."
-- strict thread matches above, loose matches on Subject: below --
2014-09-30 0:09 William Hubbs
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=20120410211745.GA9144@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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