Re: Bug report problems

On 10/24/07, Ash Searle <ash@hexmen.com> wrote: > Hi, > > I'm trying to submit a bug report for Image_Barcode (even though the > package seems to be abandoned.) > > The bug now seems to be stuck in some limbo status: > http://pear.php.net/bugs/bug.php?id=12331 > > I filled in the bug-report, complete with patch. On submission, I was > told the patch was in the wrong format - it took a few more attempts > before realising the real problem was I didn't type ".txt" on the end of > the patch name (i.e. nothing to do with the file format.) > > Attempting to access the bug gives: > ERROR: The user who submitted this bug has not yet confirmed their email > address. > > Following the confirmation link in my email gives: > ERROR: Unknown salt > > Trying to resend a confirmation email gives: > Error: handle is either already verified or does not exist > > (which is true... I've validate my email address in the past, so don't > know why I'm having to do it again.) > > Basically, I think I've jumped through all the right hoops, and yet my bug > report seems to be inaccessible... > > Thanks, > > Ash > > Note: This isn't the first time I've tried to contribute to PEAR; last > time I tried contributing there wasn't any facility for attaching patches > at all, so things are obviously progressing. But, I still find the PEAR > site and contribution process really hard to work with. > > - I'd like to contribute bug-reports without having to code fixes too; > > - If I code a fix, I'd like it acted on quickly (a week, maybe even a > month. But 2 months is too long (bug 9242), and 6 months without action > is taking the mick: http://pear.php.net/bugs/bug.php?id=10594.) > > - If a package seems abandoned (like Image_Barcode) I'd like to be able to > check stuff into CVS without having to read a 10,000 word treatise on the > responsibility of being a maintainer. I see all the reporting issues as they have come up multiple times on the list/irc. Maybe a bug report for the reporting system? No idea. Anyway, in your case I think pear-qa should be addressed. :) I cc'ed the list. Till