Re: bugzilla

[Marco Trudel <mtrudel at gmx dot ch>]

Andrew Haley wrote:
> Marco Trudel writes:
>  > Andrew Haley wrote:
>  > > Marco Trudel writes:
>  > >  > 
>  > >  > So, what am I doing wrong. This can't be broken, can it? There are too 
>  > >  > much people using it...
>  > > 
>  > > This is a bug report, and like very other bug report it needs a
>  > > reproducible test case.
>  > 
>  > Of course, you're right. Sorry about that...
>  > 
>  > - I use firefox 2.0.0.1.
>  > - The error only occurs if you're not logged in at first (just found out 
>  > myself).
>  > 
>  > Go to (be sure to not be logged in):
>  > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30510
>  > 
>  > Fill in the "Additional Comments:":
>  > Something that makes sense. At best use another bug but one that someone 
>  > else reported...
>  > 
>  > - Leave "Leave as REOPENED"
>
> What does this mean, as an instruction?  Am I not to change anything
> here?

Yes. Do not change any of the settings. Just add a comment and Commit it.

>  > - Click "Commit"
>  > - Log in
>  > 
>  > I get:
>  >   You tried to change the Assignee field from unassigned@gcc.gnu.org to 
>  > __UNKNOWN__, but only the assignee of the bug, or a sufficiently 
>  > empowered user may change that field.
>
> Works for me: I get a prompt to log in to gcc bugzilla, and when I
> then log in my change is then committed.  (This is probably because I
> am "sufficently empowered".)

Either that or because it is from you.

I also tried to add a comment to that bug as I described before. I again 
run into:
You tried to change the Assignee field from unassigned@gcc.gnu.org to 
__UNKNOWN__, but only the assignee of the bug, or a sufficiently 
empowered user may change that field.

So maybe you have the right to change the assignee field...
I can give you my account if you're not interested in creating a new one 
(You can change all my bugs anyway and I do not use the password 
somewhere else).


Marco