There's another way to do the upgrade, which is a bit more brute force,
but should exercise the post-inst changes adequately which may be
sufficient for sru validation:

1.  Set up the earlier release, and install the PPA and fixed mod_php.
2.  Manually edit /etc/apt/sources.list and change all instances of the earlier 
release to the new one.  IOW, do this:
    $ sudo sed -i 's/xenial/bionic/g' /etc/apt/sources.list
3.  Do the same for anything in /etc/apt/sources.list.d/.  In particular, 
update the file for the PPA with the php7.4 fixes.
4.  Manually upgrade
    $ sudo apt update && sudo apt -y dist-upgrade
    Note this may present different config prompts and such than the 
do-release-upgrade command.
5.  Validate upgrade works, as per the original test case.

I haven't tested this process, but used to use it long ago, and it
appears to still be the method used with debian, so I think it should
work.  (I wouldn't attempt this on production hardware, obviously.)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865218

Title:
  mod_php gets disabled during do-release-upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.2/+bug/1865218/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to