Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.32.0
Bug #16410 Rejected PEPr proposals should not steal names
Submitted: 2009-07-06 14:13 UTC
From: doconnor Assigned: doconnor
Status: Closed Package: pearweb (version CVS)
PHP Version: Irrelevant OS:
Roadmaps: 1.22.0    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 13 + 35 = ?

 
 [2009-07-06 14:13 UTC] doconnor (Daniel O'Connor)
Description: ------------ Bill Shupp says: So I just tried to propose Authentication::OpenID, but found that an old rejected proposal, http://pear.php.net/pepr/pepr-proposal-show.php?id=347, is preventing me from using that name. Why would finished, rejected proposals block new proposals of the same name? Can we fix that? This package is ready to go.

Comments

 [2009-07-13 14:15 UTC] doconnor (Daniel O'Connor)
The logic in mayRePropose() is kind of scary, as it's on the fly rather than setting a proposal to rejected.
 [2009-07-13 14:31 UTC] doconnor (Daniel O'Connor)
-Status: Open +Status: Closed -Assigned To: +Assigned To: doconnor
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. Addressed in [283999]