perl.org bugs

[Damian Menscher]

Ok, I'll try really hard to not flame too much here.....

A while back I found a potentially critical flaw in perl. Being a
good person, I went to the perl.org website to report it. They want
the report done through perlbug, so I go through that process. It
was an important bug, so I marked it as critical.

Well, it was obviously asking too much to have the latest version of
perlbug be compatible with the website. The website didnt' know
what "critical" means -- apparently it's called "fatal" now. So it
didn't assign it a severity. Oh well, just means it'll take an
extra few days for someone to notice the bug report.

I've been checking back every few days to see if anyone has noticed
it, and this time when I checked back, I can't get in to the
website. It prompts for a password. Even guest logins want a
password.

Ok, so I create an account, and log in using that. What? Another
password prompt? Hrmm... I don't have a password for that one. Oh
well. Guess I can't check on my bug.

I'm sending this here with the hope that someone with a clue and
the power to do something will actually take note and get this
fixed. While you're at it, could you make the website a bit faster?
Having to wait a minute for each page to load is rather annoying.

Damian Menscher

 

[Rafael Garcia-Suarez]

A while back I found a potentially critical flaw in perl. Being a
good person, I went to the perl.org website to report it. They want
the report done through perlbug, so I go through that process. It
was an important bug, so I marked it as critical.

Well, it was obviously asking too much to have the latest version of
perlbug be compatible with the website. The website didnt' know
what "critical" means -- apparently it's called "fatal" now. So it
didn't assign it a severity. Oh well, just means it'll take an
extra few days for someone to notice the bug report.

The perlbug web interface is being currently upgraded to RT 3, so
it's expected it has still rough edges.

I've been checking back every few days to see if anyone has noticed
it, and this time when I checked back, I can't get in to the
website. It prompts for a password. Even guest logins want a
password.

Ok, so I create an account, and log in using that. What? Another
password prompt? Hrmm... I don't have a password for that one. Oh
well. Guess I can't check on my bug.

The same password should work. This is expected to be improved in the
near future as well.

I'm sending this here with the hope that someone with a clue and
the power to do something will actually take note and get this
fixed.

Several people have tried to reproduce your bug with different versions
of perl, and failed. I think you've not given enough info, or wrong
info. Sorry, I should have replied to your bug report earlier ; but
vague bug reports tend to be treated with less priority than the clear
and concise ones, and our free time is limited.

 

[Tassilo v. Parseval]

Also sprach Damian Menscher:

Ok, I'll try really hard to not flame too much here.....

A while back I found a potentially critical flaw in perl. Being a
good person, I went to the perl.org website to report it. They want
the report done through perlbug, so I go through that process. It
was an important bug, so I marked it as critical.

Well, it was obviously asking too much to have the latest version of
perlbug be compatible with the website. The website didnt' know
what "critical" means -- apparently it's called "fatal" now. So it
didn't assign it a severity. Oh well, just means it'll take an
extra few days for someone to notice the bug report.

I've been checking back every few days to see if anyone has noticed
it, and this time when I checked back, I can't get in to the
website. It prompts for a password. Even guest logins want a
password.

The normal way of submitting reports is using 'perlbug' from the
command-line. These requests will end on the perl5-porters mailinglist
where someone is certainly going to pick them up. Btw, the severity you
assign to bugs is not that important. Even if you flag it as 'low' it'll
get noticed.

You will usually be able to see the correspondance following your report
even when you are not subscribed to (e-mail address removed) since mails
are normally CC'ed.

Ok, so I create an account, and log in using that. What? Another
password prompt? Hrmm... I don't have a password for that one. Oh
well. Guess I can't check on my bug.

I'm sending this here with the hope that someone with a clue and
the power to do something will actually take note and get this
fixed. While you're at it, could you make the website a bit faster?
Having to wait a minute for each page to load is rather annoying.

A few days ago Robert Spier made some changes to bugs.perl.org. It's
still being fine-tuned. No reports will be lost.

Tassilo