[MacPorts] #24835: php5-zip 5.3.2 requires PHP 5.3.2 but you have PHP 5.3.0. (was: php5-zip 5.3.2 Error: php5-zip 5.3.2 requires PHP 5.3.2 but you have PHP 5.3.0.)

[MacPorts]

#24835: php5-zip 5.3.2 requires PHP 5.3.2 but you have PHP 5.3.0.
---------------------------------------------------+------------------------
  Reporter:  absolutelyunderstandguitar@…          |       Owner:  macports-tickets@…                   
      Type:  defect                                |      Status:  closed                               
  Priority:  Normal                                |   Milestone:                                       
 Component:  ports                                 |     Version:  1.8.2                                
Resolution:  invalid                               |    Keywords:                                       
      Port:  php5-zip                              |  
---------------------------------------------------+------------------------

Comment(by ryandesign@…):

 Indeed I had not noticed what Joshua pointed out, that MacPorts thought
 you had 5.3.2 installed ("DEBUG: No need to upgrade! php5 5.3.2_0 >= php5
 5.3.2_0"), and I cannot explain why it would think that when you clearly
 actually had 5.3.0 installed ("Error: php5-zip 5.3.2 requires PHP 5.3.2
 but you have PHP 5.3.0"). The latter error message is printed by the
 php5extension portgroup, whose code you can
 [browser:trunk/dports/_resources/port1.0/group/php5extension-1.0.tcl?rev=61501#L191
 read for yourself] to see that all it's doing is running "`${prefix}/bin
 /php-config --version`" and comparing that number to the version of the
 port. On your system, "`${prefix}/bin/php-config --version`" did return
 the string "5.3.0", for whatever reason. The only way I can explain this
 is if you installed 5.3.2 with MacPorts, then somehow without using
 MacPorts installed 5.3.0 on top of it, or used Time Machine or another
 backup restoration method to restore at least the php-config script from
 back when you had 5.3.0, or forcibly convinced MacPorts to try to activate
 an older version of php5 on top of the newer one that was already active.
 It's all rather inexplicable and there shouldn't be a way for this to
 happen in the normal course of events. In any case, I'm glad you got it
 working now.

 I'm not sure what you mean by "some sort of cache giving out old
 information"; MacPorts doesn't have a cache. It does keep a set of port
 definitions on hand, and they do not get updated unless you manually run
 "`sudo port selfupdate`" or "`sudo port sync`", so if you're installing
 ports and getting old versions, make sure you selfupdate first.

 Note you don't need to "sudo port clean --all ''portname''" unless you get
 an error message about a checksum mismatch, or you just want to delete the
 port's distfiles to save space. Otherwise, "sudo port clean ''portname''"
 is sufficient and quicker because you won't need to re-download the
 distfile.

 There is no file "mod_conf.php"; I assume you meant "mod_php.conf". This
 file is part of the php5 port when installed with the +apache2 variant,
 and is never a part of the apache2 port. "sudo port uninstall
 ''portname''" should indeed uninstall a port's files; I cannot explain why
 you ended up with a mod_php.conf that wasn't registered to the php5 port
 and wasn't uninstalled when you uninstalled the php5 port.

-- 
Ticket URL: <http://trac.macports.org/ticket/24835#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS