From: William Hubbs <williamh@gentoo.org>
To: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] automated bug filing (i.e. pybugz) failing because of missing token
Date: Tue, 27 Mar 2012 15:03:59 -0500 [thread overview]
Message-ID: <20120327200359.GB6987@linux1> (raw)
In-Reply-To: <4F71DA6E.6000000@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
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
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-03-27 20:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 17:08 [gentoo-dev] automated bug filing (i.e. pybugz) failing because of missing token "Paweł Hajdan, Jr."
2012-03-26 17:20 ` Mike Gilbert
2012-03-26 18:44 ` Alec Warner
2012-03-27 7:33 ` Dirkjan Ochtman
2012-03-27 8:04 ` Ian Whyman
2012-03-27 13:52 ` Ian Stakenvicius
2012-03-27 14:45 ` Mike Gilbert
2012-03-27 15:19 ` "Paweł Hajdan, Jr."
2012-03-27 20:03 ` William Hubbs [this message]
2012-03-30 2:37 ` Alec Warner
2012-04-01 2:26 ` William Hubbs
2012-04-05 21:59 ` William Hubbs
2012-04-06 1:40 ` Mike Gilbert
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=20120327200359.GB6987@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=phajdan.jr@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