1 |
On Thu, Mar 29, 2012 at 07:37:15PM -0700, Alec Warner wrote: |
2 |
> On Tue, Mar 27, 2012 at 1:03 PM, William Hubbs <williamh@g.o> wrote: |
3 |
> > On Tue, Mar 27, 2012 at 05:19:10PM +0200, "Paweł Hajdan, Jr." wrote: |
4 |
> >> On 3/26/12 7:20 PM, Mike Gilbert wrote: |
5 |
> >> > On Mon, Mar 26, 2012 at 1:08 PM, "Paweł Hajdan, Jr." |
6 |
> >> > <phajdan.jr@g.o> wrote: |
7 |
> >> >> I posted this issue here because it's not obvious what to do with it. |
8 |
> >> >> That version of pybugz worked for me before (20 February 2012). |
9 |
> >> >> |
10 |
> >> >> Any ideas? |
11 |
> >> >> |
12 |
> >> > I'm guessing it was broken by the upgrade from Bugzilla 4.0 to Bugzilla 4.2. |
13 |
> >> > |
14 |
> >> > I think you should file a bug for pybugz. :) |
15 |
> >> |
16 |
> >> Right, and indeed I've found existing |
17 |
> >> <https://github.com/williamh/pybugz/pull/19> (there is patch inside). |
18 |
> > |
19 |
> > That is now merged into pybugz-9999, but it had nothing to do with the |
20 |
> > bugzilla 4.2 issues. |
21 |
> > |
22 |
> > I will see what else I can come up with, but patches/suggestions are |
23 |
> > welcome. |
24 |
> > |
25 |
> > William |
26 |
> > |
27 |
> |
28 |
> My plan is to add support for the jsonrpc api, which I was going to do |
29 |
> this weekend. |
30 |
|
31 |
Go for it; actually I wouldn't have a problem with us converting over to |
32 |
that and dropping the old method of communicating with bugzilla. |
33 |
|
34 |
William |