[MacPorts] #29132: port upgrade php5 does nothing.
#29132: port upgrade php5 does nothing. -------------------------------------+-------------------------------------- Reporter: pavel.motorin@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: php5 upgrade | Port: php5 -------------------------------------+-------------------------------------- So, "sudo port upgrade php5" does nothing. There is begin of log for "sudo port -d upgrade php5": {{{ Motorin:~ motorin$ sudo port -d upgrade php5 DEBUG: epoch: in tree: 1 installed: 1 DEBUG: php5 5.3.6_0 exists in the ports tree DEBUG: php5 5.3.5_0 +apache2+fastcgi+pear is the latest installed DEBUG: php5 5.3.5_0 +apache2+fastcgi+pear is active DEBUG: Merging existing variants '+apache2+fastcgi+pear' into variants DEBUG: new fully merged portvariants: pear + apache2 + fastcgi + DEBUG: Changing to port directory: /opt/local/var/macports/sources/www.macports.org/files/ports/lang/php5 DEBUG: OS darwin/10.7.0 (Mac OS X 10.6) arch i386 DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre- existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/www.macports.org/files/ports/_resources/port1.0/variant_descriptions.conf DEBUG: Executing variant apache2 provides apache2 DEBUG: Executing variant fastcgi provides fastcgi DEBUG: Executing variant pear provides pear DEBUG: No need to upgrade! php5 5.3.5_0 >= php5 5.3.5_0 }}} I don't understand why it does not want to upgrade. But it's necessary because some new libs demands php5 5.3.6 (php5-exif for example). -- Ticket URL: <https://trac.macports.org/ticket/29132> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29132: port upgrade php5 does nothing. -------------------------------------+-------------------------------------- Reporter: pavel.motorin@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: php5 -------------------------------------+-------------------------------------- Changes (by ryandesign@…): * keywords: php5 upgrade => * owner: macports-tickets@… => ryandesign@… Comment: Do you perhaps have a local portfile for php5 5.3.5? -- Ticket URL: <https://trac.macports.org/ticket/29132#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29132: port upgrade php5 does nothing. -------------------------------------+-------------------------------------- Reporter: pavel.motorin@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: php5 -------------------------------------+-------------------------------------- Comment(by pavel.motorin@…): So... it make me the point. It was no open port for rsync, when I installed macports, so I had choose "Portfile Sync via Daily Tarball". So i return to rsync in sources.conf (now it's ok with the rsync port), did selfupdate and than port upgrade php5. It works for me now. May be it'll be better to notice user about situations like this. Just something like "Attention! You've used local portfile..." and explain some details about potential problem. Thank you for your help! -- Ticket URL: <https://trac.macports.org/ticket/29132#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29132: port upgrade php5 does nothing. --------------------------------------+------------------------------------- Reporter: pavel.motorin@… | Owner: ryandesign@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Resolution: invalid | Keywords: Port: php5 | --------------------------------------+------------------------------------- Changes (by ryandesign@…): * status: new => closed * resolution: => invalid Comment: I'm glad you got it working, and thanks for your suggestion. I've posted [http://lists.macosforge.org/pipermail/macports-dev/2011-April/014528.html a message to the macports-dev mailing list] inviting discussion on how this could be accomplished. -- Ticket URL: <https://trac.macports.org/ticket/29132#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts