PHP sury afterhand activation #46

Open
opened 2019-05-06 20:48:48 +02:00 by Ghost · 1 comment

If one tries to activate PHP sury while PHP is already installed, the new PHP version is never installed and the task fails.

Ideally, enabling sury would force the reinstall of PHP.

The main problem becomming how to keep the right PHP version when re-rolling the playbook. I fear the very nature of the sury repository makes idempotent behaviour more difficult.

If one tries to activate PHP sury while PHP is already installed, the new PHP version is never installed and the task fails. Ideally, enabling sury would force the reinstall of PHP. The main problem becomming how to keep the right PHP version when re-rolling the playbook. I fear the very nature of the sury repository makes idempotent behaviour more difficult.
Ghost added the
bug
enhancement
labels 2019-05-06 20:48:48 +02:00
Owner

Don't use php-foo package. Instead, aim for the php7.X-foo packages

Then you'll know the exact version installed, so the right Apache Module to enable, the right path for configurations, etc...

Don't use php-foo package. Instead, aim for the php7.X-foo packages Then you'll know the exact version installed, so the right Apache Module to enable, the right path for configurations, etc...
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: evolix/ansible-roles#46
No description provided.