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

Bug #5374 package.dtd is broken, package-1.0 is not synced
Submitted: 2005-09-12 23:25 UTC
From: techtonik Assigned: cellog
Status: Closed Package: PEAR
PHP Version: Irrelevant OS:
Roadmaps: (Not assigned)    
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:
Solve the problem : 23 + 4 = ?

 [2005-09-12 23:25 UTC] techtonik
Description: ------------ Ok. DTD is not determinist, doesn't conform to std and doesn't validates with xmllint. Additionally it is not synced with XSD, but this is another story. Test script: --------------- --- package-1_old.0 Sun Jul 24 19:25:42 2005 +++ package-1.0 Tue Sep 13 01:50:22 2005 @@ -49,7 +49,7 @@ <!ELEMENT changelog (release)*> -<!ELEMENT release (version,date,license,state,notes,warnings?,((deps?,configureoptions?,provides*,filelist?)|(configureoptions?,provides*,filelist?,deps?)))> +<!ELEMENT release (version,date,license,state,notes,warnings?,provides*,deps?,configureoptions?,filelist)> <!ELEMENT version (#PCDATA)> @@ -84,7 +84,8 @@ <!ELEMENT filelist (dir|file|libfile)*> <!ELEMENT dir (dir|file|libfile)*> -<!ATTLIST dir name CDATA #REQUIRED +<!ATTLIST dir role (php|ext|test|doc|data|script|src) 'php' + name CDATA #REQUIRED baseinstalldir CDATA #IMPLIED> <!ELEMENT file (replace*)> Actual result: -------------- package.xml:60: validity error : Content model of release is not determinist: (version , date , license , state , notes , warnings? , ((deps? , configureoptions? , provides* , filelist?) | (configureoptions? , provides* , filelist? , deps?))) </release> ^


 [2005-09-13 05:15 UTC] cellog
let's put this in PEAR so that the PEAR devs also fix package.dtd inside the PEAR package
 [2005-09-14 00:24 UTC] cellog
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. again, thank for the report. Please keep descriptions informative, there is plenty of room on the mailing lists for opinions. package-1.0 and package.dtd were terribly out of sync. They also had nothing to do with what PEAR actually supports, and what actually exists, so they have been modified accordingly