ius-community team mailing list archive

[Nat Colley <nat.colley@xxxxxxxxx>]

> rpm -qa | grep -i php php53-common-5.3.3-1.el5_6.1
php53-process-5.3.3-1.el5_6.1
php53-cli-5.3.3-1.el5_6.1
php53-5.3.3-1.el5_6.1
php53-xml-5.3.3-1.el5_6.1


________________________________
From: BJ Dierkes <wdierkes@xxxxxxxxxxxxx>
To: BJ Dierkes <wdierkes@xxxxxxxxxxxxx>
Cc: Nat Colley <nat.colley@xxxxxxxxx>; "ius-community@xxxxxxxxxxxxxxxxxxx" <ius-community@xxxxxxxxxxxxxxxxxxx>
Sent: Thursday, September 22, 2011 7:53 PM
Subject: Re: [Ius-community] php extension missing, et al


Also the same thing but for php.

Sent from my iPhone

On Sep 22, 2011, at 7:14 PM, "BJ Dierkes" <wdierkes@xxxxxxxxxxxxx> wrote:


Can you provide the output of:
>
>
>rpm -qa | grep -i mysql
>
>
>
>
>Sent from my iPhone
>
>On Sep 22, 2011, at 7:03 PM, "Nat Colley" <nat.colley@xxxxxxxxx> wrote:
>
>
>I’m back, unfortunately.
>>1.       The upgrade to php 5.3 seems to have gone smoothly. However, I have a question about the php upgrade. On the ius client usage page, it says:
>>“…however 'config(php-common)' should likely be added to the php53 packages and is simply just an rpm spec change that needs to happen. The yum-plugin-replace is new, and therefore small issues like this will be resolved in the near future as they are discovered…”
>>I see that my upgrade includes php53-common. Is this the same/upgraded file? The replace plug in does not seem to think so. I got the warning message that replace was not able to resolve all providers, starting with config(php-common), but it was able to erase php-common from 5.1.6.
>>If it is not the same file, is it in the repository so I can yum it? How crucial is config(php-common)? What does it do?
>>2.    There is, however, a more serious problem. Wordpress tells me that:
>>“Your PHP installation appears to be missing the MySQL extension which is required by WordPress.”
>>As near as I can tell, this is mysql.so. On the mysql site, I found a forum entry where someone asked “where can I get mysql.so”. the answer, in relevant part, was:
>>Requiring the .so file (Shared object) just basically means you're missing a package. On a modern system like Fedora Core for instance, you have the "yum" tool, so doing "yum search php-mysql" might be what you're after 
>>
>>Most likely, you need php-mysql, to provide /usr/lib/php/modules/mysql.so
>> 
>>But I ran this request on yum and got nothing
>>> yum install php_mysql -y
>>Loaded plugins: fastestmirror, replace
>>Loading mirror speeds from cached hostfile
>> * epel: mirror.steadfast.net
>> * ius: www.applesauceman.com
>>Setting up Install Process
>>No package php_mysql available.
>>Nothing to do
>> 
>>I found a slew of .so files in /usr/lib64/php/modules, but no mysql.so
>>Does anyone here know about this specific module and whether or not it is included or can be found in another package on ius yum? If not, do you know where/how I can get it?
>>3.       I was going to upgrade mysql along with php, but I got this message:
>> 
>>> yum replace mysql --replace-with mysql55
>>Loaded plugins: fastestmirror, replace
>>Loading mirror speeds from cached hostfile
>> * epel: mirror.steadfast.net
>> * ius: www.applesauceman.com
>>Error: Multiple packages found matching 'mysql'.  Please remove manually.
>>Replacing packages takes time, please be patient...
>>-
>>I found 13 files with mysql in the name so far. This will be a slow and painful process which I may skip altogether if I get the mysql.so issue resolved. But my question is, if I can’t/don’t get all the mysql files and then try to upgrade, will I be creating new problems? If I do get all the mysql files out, then I would be asking ius yum for a new install and not an upgrade or replace, correct? Any problems there if I haven’t gotten rid of all the old files manually?
>>Thx
>_______________________________________________
>>Mailing list: https://launchpad.net/~ius-community
>>Post to     : ius-community@xxxxxxxxxxxxxxxxxxx
>>Unsubscribe : https://launchpad.net/~ius-community
>>More help   : https://help.launchpad.net/ListHelp
>>This email may include confidential information. If you received it in error, please delete it.