There seem to be two different ways of installing modphp: $ sudo apt-get install libapache2-mod-php or $ sudo apt-get install libapache2-mod-php7.2
libapache2-mod-php is a virtual package that depends on the appropriate libapache2-mod-phpN.M for that Ubuntu release; presumably if one had installed libapache2-mod-php the upgrade should work seamlessly. However, if one rather installed libapache2-mod-php7.2, then I think this is where the bug presents itself. Furthermore, there's multiple ways of upgrading to a new modphp: 1. Running `do-release-upgrade -d` 2. Editing /etc/apt/sources.list from bionic -> focal (or focal -> jammy, or impish -> jammy) 3. Upgrading just modphp itself via a PPA Way #1 is presumably how most users would be experiencing this, so the main one needing fixed, but it's also the most time-intensive to test. #2 is easier to test and still conceivably used by some experienced users, so is worth getting right. #3 is easiest to test but pretty artificial (though php users are accustomed to upgrading php via ondrej's ppa). We see that in each of these cases, libapache2-mod-php7.2 might be left in place, or removed as cleanup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890263 Title: release upgrade does not move to the new php apache mod To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-defaults/+bug/1890263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
