Report new bug | New search | Development Roadmap Status: Open | Feedback | All

Bug #6337 package.xml (2.0) does not validate with more than 1 <release> in <changelog>
Submitted: 2005-12-23 10:29 UTC
From: erik-pear at 29a dot nl Assigned: cellog
Status: Closed Package: Web Site
PHP Version: Irrelevant OS: Irrelevant
Roadmaps: (Not assigned)    
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 : 49 + 28 = ?

 
 [2005-12-23 10:29 UTC] erik-pear at 29a dot nl
Description: ------------ The package.xml file (version 2.0) does not validate against the current schema (http://pear.php.net/dtd/package-2.0.xsd) if you have more than one <release> child in the <changelog> section. This is also the case with the example file on http://pear.php.net/manual/en/guide.developers.package2.php so I guess the problem lies in the schema. Test script: --------------- Just try the demo package file on http://pear.php.net/manual/en/guide.developers.package2.php. Possible solution: I'm not an expert with XSD and I have not tested this, but I guess line 409: <xs:element name="release"> should be changed to: <xs:element name="release" minOccurs="1" maxOccurs="unbounded"> In the xsd on http://pear.php.net/dtd/package-2.0.xsd. Expected result: ---------------- No validation errors Actual result: -------------- Validation error on the second <release> element in the <changelog> section (line 220 in the example file).

Comments

 [2006-01-28 23:55 UTC] User who submitted this comment has not confirmed identity
If you submitted this note, check your email.If you do not have a message, click here to re-send
MANUAL CONFIRMATION IS NOT POSSIBLE.  Write a message to pear-dev@lists.php.net
to request the confirmation link.  All bugs/comments/patches associated with this

email address will be deleted within 48 hours if the account request is not confirmed!