'pkg upgrade' wants to install php56
dnewman at networktest.com
Mon Mar 2 01:44:09 UTC 2015
On 3/1/15 4:28 PM, Michael Powell wrote:
> David Newman wrote:
>> How to ensure pkg will upgrade php5 modules within the same minor version?
>> After updating pkgs on a FreeBSD 10.1-RELEASE-p6 amd64 system, the 'pkg
>> upgrade' command wants to install php56 even though all php5 pkgs are on
>> 5.4.37. The rest of the commands from the upgrade appear to want to
>> upgrade modules from php5-5.4.37 to 5.4.38.
> The default recently changed to 5.6 as per 20150220: in /usr/ports/UPDATING.
> Also see 20140211: in same.
Thanks for your responses. Please note that I'm asking about pkg on
systems that don't have a ports tree, so also no UPDATING file.
Also, systems that formerly used ports but now used pkg will have an
UPDATING file but it will not be updated.
I think pkg does not correctly handle the php56 upgrade, as detailed below.
>> There's nothing in /etc/make.conf forcing version numbers.
> Try putting in make.conf this: DEFAULT_VERSIONS+=php=5.5
Side question: What is the difference between this syntax, with a plus
sign, and the 'DEFAULT_VERSIONS=php=5.5 mysql=5.6 apache=2.4' example,
without a plus sign, given in the 20140211 entry in UPDATING?
Neither the handbook nor the make.conf(5) manpage cover this.
>> I don't particularly care which php version runs (well, within 5.4-5.6)
>> as long as module versions are consistent. How to ensure that?
> I build everything from ports and do not use binary package management. Not
> entirely certain as to any difference(s) that may entail. I followed all the
> instructions as the came along about moving to the new 'pkg' system so in
> theory it should work just fine. Just have never tried it, yet. So, not
> entirely sure about how make.conf relates to binary (pkg) management
> practices. Would like to know more about this meself.
The pkg behavior is not consistent in my experience:
- On one system running 10.1-RELEASE-p6 and no /etc/make.conf file, 'pkg
update && pkg upgrade' just updates php5 modules from 5.4.37 to 5.4.38.
These commands did not install any php56 modules.
- On another system with the same version, the same commands want to
install php56, and also upgrade all other php5 modules (except php5
itself) from 5.4.37 to 5.4.38.
On this second system, adding 'DEFAULT_VERSIONS=php=5.6' to
/etc/make.conf does not change the outcome of these commands.
Even worse, if we proceed with those commands, pkg ends up with a
Fetching php56-5.6.6.txz: 100% 2 MiB 982.6kB/s 00:02
Checking integrity... done (1 conflicting)
pkg: Cannot solve problem using SAT solver:
upgrade rule: upgrade local php5-zlib-5.4.37 to remote php5-zlib-5.4.38
cannot install package php5-zlib, remove it from request? [Y/n]:
How to resolve this?
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions