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

Bug #6594 export compatible V1 lost changelog when import existing package v2
Submitted: 2006-01-26 13:18 UTC
From: farell Assigned: farell
Status: Closed Package: PEAR_PackageFileManager
PHP Version: 4.4.2 OS: Windows XP
Roadmaps: (Not assigned)    

 [2006-01-26 13:18 UTC] farell
Description: ------------ With PEAR_PackageFileManager2, when you import an existing package v2.0 and try to export a compatible version 1.0, you will lose changelog history. That will occurs only for package v1, v2 keep full changelog. To reproduce, you must have only a package v2.0 version. In test script, its "E:/wamp/tmp/myQFAMS_package2.xml", with many changelog entries. Test script will save a new package v2 version (package2.xml) and a first version of package v1 (package.xml). package2.xml has full changelog entries. package.xml has only the last(current) version enty. I'll fix it into CVS: i've already a solution. Laurent Test script: --------------- <?php require_once 'PEAR/PackageFileManager2.php'; $optionsUpdate = array( 'packagefile' => "package.xml", 'pathtopackagefile' => false, 'packagedirectory' => "D:/php/pear/HTML_QuickForm_advmultiselect/", 'baseinstalldir' => 'HTML/QuickForm', 'filelistgenerator' => 'cvs', 'changelogoldtonew' => false, 'simpleoutput' => false, 'cleardependencies' => false, ); $pkg = &PEAR_PackageFileManager2::importFromPackageFile1('E:/wamp/tmp/myQFAMS_package2.xml', $optionsUpdate); $pkgV1 = &$pkg->exportCompatiblePackageFile1(); echo '<pre>'; var_dump($pkgV1->_packageXml); echo '</pre>'; ?> Expected result: ---------------- keep full v1 changelog on convert v2 to v1 operation. Actual result: -------------- only package v2 keep full changelog. package v1 result of convertion lost the changelog.


 [2006-01-26 13:39 UTC] farell
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.