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

Bug #3634 still too many pear specific restrictions on package validation
Submitted: 2005-02-28 06:23 UTC
From: wez Assigned: cellog
Status: Closed Package: PEAR
PHP Version: 5_1 CVS-2005-02-28 OS: linux
Roadmaps: (Not assigned)    

 [2005-02-28 06:23 UTC] wez
Description: ------------ When attempting to upload a bugfix release of mailparse, version 2.1.1 via (traditional package.xml): The first release of a package must be 'alpha' or 'beta', not 'stable'. Try releasing version 1.0.0RC1, state 'beta' When attempting to create a package2.xml file, using "pear convert": Attempting to process the second package file Warning: Channel validator warning: field "version" - major version x in x.y.z may not be greater than 1 for any package that does not have an <extends> tag Seems like it would be nice to have channel-specific validation, if possible (I can easily see a third-party channel wanting to do things a little bit differently).


 [2005-02-28 14:16 UTC] cellog
I think you are right - PECL needs its own validator. However, channel-specific validation is written into the existing version, all we have to do is write the actual validator, release it as a package, and list it in the channel.xml. I would like to do lots of local tests with my peclweb before we make this live, it is the least tested feature of PEAR 1.4 in the "wild" as nobody has needed it before now. Basically, I think pecl needs really loose version validation (you guys do things better by giving similar packages cool names like mysqli rather than mysql2, eliminating this particular version check). Other than this, it sounds like there is a bug at - I will see if I can add a check whether the uploaded release is a pecl package and then skip the strict validation on upload. Sorry for the inconvenience
 [2005-03-03 02:39 UTC] cellog
This bug has been fixed in CVS. In case this was a documentation problem, the fix will show up at the end of next Sunday (CET) on In case this was a website problem, the change will show up on the website in short time. Thank you for the report, and for helping us make PEAR better. to fully fix this, once you upgrade you have to "pear channel-update" I'll add a note to the release notes, I guess Greg