From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9251 invoked by alias); 1 Feb 2011 19:11:37 -0000 Received: (qmail 9243 invoked by uid 22791); 1 Feb 2011 19:11:36 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Received: from mail-wy0-f175.google.com (HELO mail-wy0-f175.google.com) (74.125.82.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 01 Feb 2011 19:11:29 +0000 Received: by wyb40 with SMTP id 40so7319352wyb.20 for ; Tue, 01 Feb 2011 11:11:26 -0800 (PST) Received: by 10.216.61.202 with SMTP id w52mr993989wec.110.1296587486673; Tue, 01 Feb 2011 11:11:26 -0800 (PST) Received: from [192.168.1.20] ([92.27.106.239]) by mx.google.com with ESMTPS id n1sm11626675weq.31.2011.02.01.11.11.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 01 Feb 2011 11:11:24 -0800 (PST) Subject: Re: Bug database write permissions From: Sebastien Bourdeauducq To: LpSolit@netscape.net Cc: Ian Lance Taylor , overseers@gcc.gnu.org, green@moxielogic.com In-Reply-To: <4D484A21.1010107@netscape.net> References: <20110130180606.26118.qmail@sourceware.org> <1296567357.15319.4.camel@localhost.localdomain> <4D484A21.1010107@netscape.net> Content-Type: text/plain; charset="UTF-8" Date: Tue, 01 Feb 2011 19:11:00 -0000 Message-ID: <1296587369.15319.34.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org X-SW-Source: 2011-q1/txt/msg00040.txt.bz2 On Tue, 2011-02-01 at 19:00 +0100, Frédéric Buclin wrote: > > I've confirmed that the user ID lekernel@gcc.gnu.org does not have any > > Bugzilla permissions, but the ID does match the regexps. Does anybody > > know what is going wrong here? > > Did you use the Bugzilla web interface to create this user account? No, I didn't. > Because I just edited this account, and all credentials have been > updated correctly. It works now. Thank you! Sébastien