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

Bug #18063 install to wrong dir
Submitted: 2010-11-16 18:33 UTC
From: glen Assigned: doconnor
Status: Closed Package: Image_JpegXmpReader (version 0.5.2)
PHP Version: 5.3.3 OS:
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 : 7 - 5 = ?

 
 [2010-11-16 18:33 UTC] glen (Elan Ruusamäe)
Description: ------------ seems it installs wrong, i.e extra Image should be stripped $ pear download Image_JpegXmpReader downloading Image_JpegXmpReader-0.5.2.tgz ... Starting to download Image_JpegXmpReader-0.5.2.tgz (3,861 bytes) ....done: 3,861 bytes File /home/users/glen/rpm/pear-autoup/php-pear- Image_JpegXmpReader/Image_JpegXmpReader-0.5.2.tgz downloaded $ rm -rf /tmp/inst/ $ pear install --nodeps --offline --packagingroot=/tmp/inst Image_JpegXmpReader-0.5.2.tgz warning: pear/Image_JpegXmpReader requires package "pear/XML_Parser" warning: pear/Image_JpegXmpReader requires package "pear/Image_JpegMarkerReader" install ok: channel://pear.php.net/Image_JpegXmpReader-0.5.2 glen@carme-pld-i686 pear-autoup/php-pear- $ find /tmp/inst/ /tmp/inst/ /tmp/inst/usr /tmp/inst/usr/share /tmp/inst/usr/share/pear /tmp/inst/usr/share/pear/Image /tmp/inst/usr/share/pear/Image/Image /tmp/inst/usr/share/pear/Image/Image/JpegXmpReader.php ... $ pear -V PEAR Version: 1.9.1 PHP Version: 5.3.3 Zend Engine Version: 2.3.0 Running on: Linux carme-pld-i686 2.6.36-0.1 #1 SMP Sun Nov 7 11:59:00 CET 2010 i686

Comments

 [2010-12-06 04:50 UTC] doconnor (Daniel O'Connor)
-Status: Open +Status: Closed -Assigned To: +Assigned To: doconnor
This bug has been fixed in SVN. 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.