From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SCDbk-0000NX-P2 for garchives@archives.gentoo.org; Mon, 26 Mar 2012 17:21:29 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 90FC5E0205; Mon, 26 Mar 2012 17:21:18 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 3B58BE002B for ; Mon, 26 Mar 2012 17:20:41 +0000 (UTC) Received: from mail-qa0-f46.google.com (mail-qa0-f46.google.com [209.85.216.46]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: floppym) by smtp.gentoo.org (Postfix) with ESMTPSA id 9399E1B4009 for ; Mon, 26 Mar 2012 17:20:40 +0000 (UTC) Received: by qaeb19 with SMTP id b19so2315472qae.19 for ; Mon, 26 Mar 2012 10:20:38 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Received: by 10.224.86.208 with SMTP id t16mr2370128qal.16.1332782438534; Mon, 26 Mar 2012 10:20:38 -0700 (PDT) Received: by 10.229.214.134 with HTTP; Mon, 26 Mar 2012 10:20:38 -0700 (PDT) In-Reply-To: <4F70A285.3090401@gentoo.org> References: <4F70A285.3090401@gentoo.org> Date: Mon, 26 Mar 2012 13:20:38 -0400 Message-ID: Subject: Re: [gentoo-dev] automated bug filing (i.e. pybugz) failing because of missing token From: Mike Gilbert To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 6463c5f4-3029-4954-8d48-ec5626e8dd28 X-Archives-Hash: c788c1c5f0d7bab01c569ebcff703aec On Mon, Mar 26, 2012 at 1:08 PM, "Pawe=C5=82 Hajdan, Jr." 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.