Topic: Blades page: How do I get it back in synch?

[Rob Shiras]

SME 5.0
I have downloaded and installed the rpms as advised to date.
However, the blades page does not match what is installed.
For instance, it says I have not installed update 2.
It does say I have installed update 3.
It says I have not installed update 4.
When I click on the install link for update 4, I get:
There were errors installing the SMEServer-5.0_Update4-03 blade
New package php-4.0.6-7es4.i386 conflicts with installed package php-4.1.2-2es.i686.
New package php-mysql-4.0.6-7es4.i386 conflicts with installed package php-mysql-4.1.2-2es.i686.
New package php-imap-4.0.6-7es4.i386 conflicts with installed package php-imap-4.1.2-2es.i686.
New package php-ldap-4.0.6-7es4.i386 conflicts with installed package php-ldap-4.1.2-2es.i686.

How can I get my blades page back on track?

[Bill Talcott]

As it says, it can't install Update 4 due to version conflicts with PHP. I believe the author of the PHP upgrade RPM (Dan Brown?) posted here not too long ago saying that he changed the requirements so you wouldn't need the exact same version, though I'm not sure how this affects updates. You may need to revert back to the standard version of PHP.

If you use the Update 6 install script, it will not install if Update 4 isn't installed. FYI, the non-Blade updates don't have new "SME Update" RPMs, so it will still appear to the system that Update 4 is installed. The only way to fix that would be to create an "Update 6" RPM and replace the "Update 4" RPM with it.

[Dan Brown]

The update RPMs have very strict version dependencies--you must have exactly the versions of the relevant RPMs installed that it wants.  You've installed my upgraded PHP RPMs, which aren't what the update RPM wants to see.  Your options are either to force installation of the older PHP RPMs, and give up the features of the newer version, or live with not having the update RPM installed (but having all the other packages).

AFAIK, my recent PHP RPMs contain all security patches, but of course I can't guarantee they aren't vulnerable to some exploit somewhere.

Bill, what I was referring to in my earlier message was the php-manual package.  Previous versions of that one required the exact same version and release of PHP, which was silly.  The latest one I've built requires PHP >= 4.0.  For most purposes, though, it doesn't need to be installed at all, and it really wouldn't relate to the situation here.