If you wonder why I stopped filing new stabilization request, the
pybugz-based script that was filing those bugs started failing.

I have added some debugging statements to see what's going on, and
here's what https://bugs.gentoo.org says as a response to pybugz's
request to create a new bug:

<div class="throw_error">
It looks like you didn't come from the right page (you have no valid
token for
the <em>create_bug</em> action while processing the
'post_bug.cgi' script). The reason could be one of:<br>
<ul>
<li>You clicked the "Back" button of your web browser after having
successfully
submitted changes, which is generally not a good idea (but
harmless).</li>
<li>You entered the URL in the address bar of your web browser
directly,
which should be safe.</li>
<li>You clicked on a URL which redirected you here <b>without your
consent</b>,
in which case this action is much more critical.</li>
</ul>
Are you sure you want to commit these changes anyway? This may result in
unexpected and undesired results.
</div>

And there is a form below etc. etc. Note that only filing new bugs is
affected (updating existing ones works fine).

It's possible to repro with the command-line bugz tool (bugz ... post).

I'm using pybugz-0.9.3 and I'm connecting to https://bugs.gentoo.org

I posted this issue here because it's not obvious what to do with it.
That version of pybugz worked for me before (20 February 2012).

Any ideas?

On Mon, Mar 26, 2012 at 1:08 PM, "Paweł Hajdan, Jr."
<phajdan.jr@gentoo.org> wrote:
> I posted this issue here because it's not obvious what to do with it.
> That version of pybugz worked for me before (20 February 2012).
>
> Any ideas?
>

I'm guessing it was broken by the upgrade from Bugzilla 4.0 to Bugzilla 4.2.

I think you should file a bug for pybugz.

Long term, we may want to consider porting pybugz to use Bugzilla's
XML-RPC api to avoid such breakage.

On Mon, Mar 26, 2012 at 10:20 AM, Mike Gilbert <floppym@gentoo.org> wrote:
> On Mon, Mar 26, 2012 at 1:08 PM, "Paweł Hajdan, Jr."
> <phajdan.jr@gentoo.org> wrote:
>> I posted this issue here because it's not obvious what to do with it.
>> That version of pybugz worked for me before (20 February 2012).
>>
>> Any ideas?
>>
>
> I'm guessing it was broken by the upgrade from Bugzilla 4.0 to Bugzilla 4.2.
>
> I think you should file a bug for pybugz.
>
> Long term, we may want to consider porting pybugz to use Bugzilla's
> XML-RPC api to avoid such breakage.
>

XML-RPC is shit.

[eom]

-A

On Mon, Mar 26, 2012 at 20:44, Alec Warner <antarus@gentoo.org> wrote:
>> Long term, we may want to consider porting pybugz to use Bugzilla's
>> XML-RPC api to avoid such breakage.
>
> XML-RPC is shit.

https://wiki.mozilla.org/Bugzilla:REST_API

On 27 March 2012 08:33, Dirkjan Ochtman <djc@gentoo.org> wrote:
> On Mon, Mar 26, 2012 at 20:44, Alec Warner <antarus@gentoo.org> wrote:
>>> Long term, we may want to consider porting pybugz to use Bugzilla's
>>> XML-RPC api to avoid such breakage.
>>
>> XML-RPC is shit.
>
> https://wiki.mozilla.org/Bugzilla:REST_API
>

Shame that it requires custom patches to BZ, personally I think the
preferable (and offically supported) method would be JSON-RPC[1]

Ian

1.http://www.bugzilla.org/docs/4.0/en/html/api/Bugzilla/WebService/Server/JSONRPC.html

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 27/03/12 04:04 AM, Ian Whyman wrote:
> On 27 March 2012 08:33, Dirkjan Ochtman <djc@gentoo.org> wrote:
>> On Mon, Mar 26, 2012 at 20:44, Alec Warner <antarus@gentoo.org>
>> wrote:
>>>> Long term, we may want to consider porting pybugz to use
>>>> Bugzilla's XML-RPC api to avoid such breakage.
>>>
>>> XML-RPC is shit.
>>
>> https://wiki.mozilla.org/Bugzilla:REST_API
>>
>
> Shame that it requires custom patches to BZ, personally I think
> the preferable (and offically supported) method would be
> JSON-RPC[1]
>
> Ian
>
> 1.http://www.bugzilla.org/docs/4.0/en/html/api/Bugzilla/WebService/Server/JSONRPC.html
>
>
What about all of the above? Shouldn't be hard to use the various
support libs to dump the request object to either format, right?

(no, i'm not volunteering)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iF4EAREIAAYFAk9xxhoACgkQAJxUfCtlWe0nVwEA6DIm5IcHax ZuFUZz7ETOq8o3
zzVOBJqP84SY+FQv8xkBALlNtfKSgQLPR0Qoyc3/nUqt8hAuvOF0jOIEx9r0FVMm
=wYwb
-----END PGP SIGNATURE-----

On Tue, Mar 27, 2012 at 4:04 AM, Ian Whyman <thev00d00@gentoo.org> wrote:
> On 27 March 2012 08:33, Dirkjan Ochtman <djc@gentoo.org> wrote:
>> On Mon, Mar 26, 2012 at 20:44, Alec Warner <antarus@gentoo.org> wrote:
>>>> Long term, we may want to consider porting pybugz to use Bugzilla's
>>>> XML-RPC api to avoid such breakage.
>>>
>>> XML-RPC is shit.
>>
>> https://wiki.mozilla.org/Bugzilla:REST_API
>>
>
> Shame that it requires custom patches to BZ, personally I think the
> preferable (and offically supported) method would be JSON-RPC[1]
>
> Ian
>
> 1.http://www.bugzilla.org/docs/4.0/en/html/api/Bugzilla/WebService/Server/JSONRPC.html
>

Quoting that page:

Please note that everything about this JSON-RPC interface is
EXPERIMENTAL. If you want a fully stable API, please use the
Bugzilla::WebService::Server::XMLRPC|XML-RPC interface.

This is why I suggested the XML-RPC api.

On 3/26/12 7:20 PM, Mike Gilbert wrote:
> On Mon, Mar 26, 2012 at 1:08 PM, "Paweł Hajdan, Jr."
> <phajdan.jr@gentoo.org> wrote:
>> I posted this issue here because it's not obvious what to do with it.
>> That version of pybugz worked for me before (20 February 2012).
>>
>> Any ideas?
>>
> I'm guessing it was broken by the upgrade from Bugzilla 4.0 to Bugzilla 4.2.
>
> I think you should file a bug for pybugz.

Right, and indeed I've found existing
<https://github.com/williamh/pybugz/pull/19> (there is patch inside).

William, this is now broken with Gentoo bugzilla. Could you please take
another look at the pull request referenced above.

Thanks.

On Tue, Mar 27, 2012 at 05:19:10PM +0200, "Paweł Hajdan, Jr." wrote:
> On 3/26/12 7:20 PM, Mike Gilbert wrote:
> > On Mon, Mar 26, 2012 at 1:08 PM, "Paweł Hajdan, Jr."
> > <phajdan.jr@gentoo.org> wrote:
> >> I posted this issue here because it's not obvious what to do with it.
> >> That version of pybugz worked for me before (20 February 2012).
> >>
> >> Any ideas?
> >>
> > I'm guessing it was broken by the upgrade from Bugzilla 4.0 to Bugzilla 4.2.
> >
> > I think you should file a bug for pybugz.
>
> Right, and indeed I've found existing
> <https://github.com/williamh/pybugz/pull/19> (there is patch inside).

That is now merged into pybugz-9999, but it had nothing to do with the
bugzilla 4.2 issues.

I will see what else I can come up with, but patches/suggestions are
welcome.

William

On Tue, Mar 27, 2012 at 1:03 PM, William Hubbs <williamh@gentoo.org> wrote:
> On Tue, Mar 27, 2012 at 05:19:10PM +0200, "Paweł Hajdan, Jr." wrote:
>> On 3/26/12 7:20 PM, Mike Gilbert wrote:
>> > On Mon, Mar 26, 2012 at 1:08 PM, "Paweł Hajdan, Jr."
>> > <phajdan.jr@gentoo.org> wrote:
>> >> I posted this issue here because it's not obvious what to do with it.
>> >> That version of pybugz worked for me before (20 February 2012).
>> >>
>> >> Any ideas?
>> >>
>> > I'm guessing it was broken by the upgrade from Bugzilla 4.0 to Bugzilla 4.2.
>> >
>> > I think you should file a bug for pybugz.
>>
>> Right, and indeed I've found existing
>> <https://github.com/williamh/pybugz/pull/19> (there is patch inside).
>
> That is now merged into pybugz-9999, but it had nothing to do with the
> bugzilla 4.2 issues.
>
> I will see what else I can come up with, but patches/suggestions are
> welcome.
>
> William
>

My plan is to add support for the jsonrpc api, which I was going to do
this weekend.

-A