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

Bug #6387 Unable to open zip files created on a PC
Submitted: 2006-01-01 23:18 UTC
From: kelvins at kelhome dot dyndns dot org Assigned: cbrunet
Status: Closed Package: File_Archive
PHP Version: 4.3.6 OS: Fedora Core 3
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 : 47 - 27 = ?

 
 [2006-01-01 23:18 UTC] kelvins at kelhome dot dyndns dot org
Description: ------------ Using version 1.5.3. If I use winzip on PC platform and create an archive, then try and open it on linux platform, I get a "No directory tcf.zip/ in inner reader". The zip file is there and the permissions are correct. I can use zip and unzip -l from the command line and it works perfectly. If I unzip the package with unzip, the zip it again (while leaving in the same location) it works fine. Does not work even if I use absolute file paths. The first few bytes of a good zip file PKxxx, and a bad zip file starts with PK00PKxxx (where xxx is other data). You can download the zip file from: http://kelhome.dyndns.org/tcf.zip Test script: --------------- <?php require_once "File/Archive.php"; // This opens a file (Archive or not) for reading. $source = File_Archive::read("./tcf.zip/"); if (PEAR::isError($source)) echo $source->getMessage(); // Starts recursing through file while ($source->next() ) { // List files from archive echo "Processing file...".$source->getFilename()."<BR>"; */ } ? Expected result: ---------------- Should be able to read archive file Actual result: -------------- As explained in the description

Comments

 [2008-05-28 15:55 UTC] cbrunet (Charles Brunet)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net 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.