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