From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Bugzilla 4 migration
Date: Mon, 7 Mar 2011 09:47:11 -0600 [thread overview]
Message-ID: <20110307154710.GA22974@comet.mayo.edu> (raw)
In-Reply-To: <AANLkTi=OB0o9JY2DjKZeG1mo1QbAaFBMt9vR5JwgmCD=@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
On 16:35 Mon 07 Mar , Dirkjan Ochtman wrote:
> On Mon, Mar 7, 2011 at 15:13, Donnie Berkholz <dberkholz@gentoo.org> wrote:
> > Thanks! One thing I've been very interested about in 3.x and 4.x is API
> > access that's better than screen-scraping. I tried using the
> > python-bugzilla client that accesses Bugzilla via XML-RPC but it didn't
> > seem to work. Do we have anything available?
>
> Is that the one you get if you emerge pybugz?
No, pybugz is a screen-scraper. We previously had Bugzilla 2 so we
couldn't do anything else.
> The Mozilla guys made a pretty nice REST API that can be installed as a
> plugin, I think. Maybe we could run that?
I've been somewhat following that too, but I don't know if anyone's
written a CLI client for it yet, whereas python-bugzilla already exists
(and has an ebuild in the sabayon overlay).
--
Thanks,
Donnie
Donnie Berkholz
Sr. Developer, Gentoo Linux
Blog: http://dberkholz.com
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-03-07 15:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 22:55 [gentoo-dev] Bugzilla 4 migration Christian Ruppert
[not found] ` <4D742033.5030609@gentoo.org>
2011-03-07 1:49 ` Christian Ruppert
2011-03-07 9:12 ` Michał Górny
2011-03-07 9:24 ` Dirkjan Ochtman
2011-03-07 9:30 ` Michał Górny
2011-03-07 9:25 ` Mike Frysinger
2011-03-07 14:48 ` Tobias Klausmann
2011-03-07 14:50 ` Dane Smith
2011-03-07 15:00 ` Mike Frysinger
2011-03-07 19:47 ` Michał Górny
2011-03-07 20:03 ` Christian Ruppert
2011-03-07 20:06 ` Olivier Crête
2011-03-07 21:32 ` Fabian Groffen
2011-03-07 21:52 ` Rich Freeman
2011-03-07 21:59 ` Fabian Groffen
2011-03-07 22:23 ` Mike Frysinger
2011-03-07 22:25 ` Mike Frysinger
2011-03-08 8:08 ` Fabian Groffen
2011-03-08 14:26 ` Michał Górny
2011-03-08 14:41 ` Antoni Grzymała
2011-03-08 14:53 ` Michał Górny
2011-03-08 15:06 ` Nathan Phillip Brink
2011-03-07 9:33 ` Robin H. Johnson
2011-03-07 9:51 ` Robin H. Johnson
2011-03-07 10:09 ` justin
2011-03-07 11:30 ` Jorge Manuel B. S. Vicetto
2011-03-07 14:13 ` Donnie Berkholz
2011-03-07 15:35 ` Dirkjan Ochtman
2011-03-07 15:47 ` Donnie Berkholz [this message]
2011-03-08 6:50 ` Hans de Graaff
2011-03-08 14:06 ` Donnie Berkholz
2011-03-07 12:20 ` Markos Chandras
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=20110307154710.GA22974@comet.mayo.edu \
--to=dberkholz@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