© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hello and thank you for filing this report!
I am aware of the issue you referenced, but it's not necessarily an easy one to solve. The packages from 14.04 (php5 related) are replaced by those in 16.04 (php7.0 related), but e.g., the configuration files can't necessarily migrate -- so it's not a proper replacement, if that makes sense. Additionally, some packages simply don't exist any longer.
I believe similar cases have existed in the past, with major version bumps. I will definitely consider ways to make the upgrade more seamless, but it's more like there's a whole new version of PHP rather than a straightforward upgrade (in my mind).
The end-goal is to have php- based metapackages for everything in the core, which will ease these kinds of issues going forward (as php-* ends up depending on php7.0-* right now and in a future release (e.g., 17.04, say), we would change that dependency to be php7.1-*) and upgrades should work properly :) [with some additional work].
Ondřej, do you have any further comments you might provide here? Or insight into what Debian might do for the next release as an answer to similar questions?
Thanks,
Nish