What happened to the php*-psa-compat packages?

Asked by Dane Elwell

It appears that the php*-psa-compat packages (e.g., php53u-psa-compat) are no longer in the repositories. I can't find a reason why these would have been removed, which confuses me as Plesk support appears to still be broken for packages that aren't named "php" exactly (at least, on Plesk 9 and seemingly Plesk 10).

Can someone advise why these packages were removed, and what the workaround is now?

Question information

Language:
English Edit question
Status:
Answered
For:
IUS Community Project Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Dane Elwell (dane-elwell) said :
#1

Commit that removed the package from php53u - http://bazaar.launchpad.net/~ius-coredev/ius/php53u/revision/73

Revision history for this message
Jeffrey Ness (jeffrey-ness) said :
#2

Hello Dane,

The reason the psa-compat packages were removed is because they did not resolve the issues
with Plesk and custom named PHP packages.

These packages didn't work because Plesk's packagemng binary updates the database each
time the Web interface is hit, so the compact packages were being overwritten as soon as a user logged in.

There are open communications with Parallells about supporting custom named PHP packages by means of
the rpm --provides database; however, at the moment we are not yet there.

Jeffrey-

Revision history for this message
Aaron Adams (aaron-p) said :
#3

(I edited the question just to specifically mention php53u-psa-compat, for Google's sake.)

I've started a thread here, detailing how Plesk actually "uninstalled itself," for lack of a better description, after I updated my PHP version with the IUS repository: http://forum.parallels.com/showthread.php?t=281789

For now, I'm going to create a dummy php53 package so Plesk behaves. Here's hoping you're able to make some progress with the Parallels team.

Can you help with this problem?

Provide an answer of your own, or ask Dane Elwell for more information if necessary.

To post a message you must log in.