Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apache PHP7 module isn't enabled automatically following dist-upgrade from Symbiosis Jessie #116

Closed
andrewladlow opened this issue Jun 18, 2018 · 2 comments

Comments

@andrewladlow
Copy link
Contributor

@andrewladlow andrewladlow commented Jun 18, 2018

During the dist-upgrade from Symbiosis Jessie to Stretch, Apache will not enable the PHP7 module as it conflicts with PHP5 (which should already be enabled). The PHP5 module should therefore be explicitly disabled in favour of PHP7.

@banburybill
Copy link
Contributor

@banburybill banburybill commented Jul 19, 2018

I see Bytemark have now done this. This action, though, broke the website on one of the hosts I manage.

Yes, the website uses an old PHP framework which doesn't work on PHP7. We're slowly working towards replacing it. But it's not there yet, and I think that, convenient as it may be for Symbiosis, upgrading the system PHP version in this manner isn't quite the done thing.

Loading

@andrewladlow
Copy link
Contributor Author

@andrewladlow andrewladlow commented Jul 24, 2018

We've reverted this so that it'll behave as a standard Debian Jessie -> Stretch dist-upgrade would - informing the user that PHP7 modules won't be enabled, but not forcing them instead of PHP5.

The idea was to streamline the dist-upgrade process for users who were perhaps not all that confident with the Linux command line, but having them manually disable/enable Apache mods is definitely preferable to breaking sites that aren't quite ready for PHP7. 🙂

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants