Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.32.0

Bug #10694 RC releases not accepted when uploading new release
Submitted: 2007-04-12 10:53 UTC
From: cipri Assigned: cipri
Status: Closed Package: pearweb (version 1.12.1)
PHP Version: Irrelevant OS: Irrelevant
Roadmaps: 1.13.0    

 [2007-04-12 10:53 UTC] cipri (Cipriano Groenendal)
Description: ------------ I just generated the package.xml for the latest Mail_Mime version(1.4.0 RC1, stability beta), but when I tried to upload it I got the following error: ERRORS: You must correct your package.xml file: * Release Candidate versions cannot be stable Please verify that the following release information is correct: Package: Mail_Mime Version: 1.4.0RC1 Release State: beta Test script: --------------- Here's the packaged file I tried to upload:


 [2007-04-12 22:47 UTC] cipri (Cipriano Groenendal)
The latest revision of release-upload.php refuses to accept RC releases, as can be seen on if (strpos($version, 'RC')) { $errors[] = 'Release Candidate versions cannot be stable'; } Which should ofcourse be something like if (strpos($version, 'RC') && ($info->getState() != 'beta')){ $errors[] 'Release Candidate versions must have stability beta'; }
 [2007-04-13 04:25 UTC] cellog (Greg Beaver)
the bad news: I'm on the road, so no time to do a pearweb release the good news: I manually fixed release-upload.php on the server, so release away.
 [2007-04-13 05:47 UTC] cipri (Cipriano Groenendal)
Just tried it, got the following error: Fatal error: Call to undefined method PEAR_PackageFile_v2::getStat() in /usr/local/web/ on line 278 Looks like you left out an e in there;)
 [2007-04-13 13:45 UTC] cellog (Greg Beaver)
e added, knock yourself out :)
 [2007-04-13 15:46 UTC] cipri (Cipriano Groenendal)
Hurrah! Version 1.4.0RC1 of Mail_Mime has been successfully released, and its promotion cycle has started.
 [2007-04-17 22:25 UTC] cellog (Greg Beaver)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the 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.