Relating this example above to a few details:
#1
Reasonable concern "What if people upgraded, use the (wrong, old and
non-serviced) mod-php happily and will now be broken by the SRU?
=> As shown above, once you are in this situation your mod-php is doing nothing.
That IMHO invalidates the
Thanks everyone for the discussion so far, I'm trying to add a few
details and fill a few argumentative gaps.
First let me re-share the simple scenario which I used to illustrate/prove the
issues.
Then in another comment below I'll outline a few affects of this overall case.
Example:
On bionic
** Description changed:
[Impact]
Users who install libapache2-mod-php7.2 (as opposed to the
virtual libapache2-mod-php package) and upgrade from bionic to focal
will not be upgraded to libapache2-mod-php7.4 as expected, and depending
- on the way they upgrade may have modphp removed
I discussed this with other members of the SRU team last week. My notes:
"...that would be a maintenance action being fixed in an SRU, and may
pull the rug from under users’ feet by forcibly upgrading them after it
has been working on Focal for years. The security implications should be
dealt
Good job finding a solution that works!
What's the status on Debian accepting something like this?
This also seems like a pattern that would be useful elsewhere. Is it
already an established pattern?
I'm reluctant to take this for an SRU without having confidence that we
won't end up iterating
** Merge proposal linked:
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/php7.4/+git/php7.4/+merge/421779
--
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
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/php7.4/+git/php7.4/+merge/421553
--
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
** Changed in: php-defaults (Ubuntu Bionic)
Status: New => In Progress
** Changed in: php-defaults (Ubuntu Focal)
Status: Fix Released => In Progress
** Changed in: php7.4 (Ubuntu Focal)
Status: Fix Released => In Progress
--
You received this bug notification because you
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/php7.4/+git/php7.4/+merge/421443
--
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
** Description changed:
- While checking how things behave for bug 1890029 I might have found
- another aspect/version of bug 1865218. But I'm not sure yet.
+ [Impact]
+ Users who install libapache2-mod-php7.2 (as opposed to the
+ virtual libapache2-mod-php package) and upgrade from bionic to
Similarly, the focal -> jammy upgrade process is also confirmed as fixed
now, with the jammy update:
###
### Focal Test Case for BUGGY Behavior ###
###
$ lxc launch ubuntu-daily:focal lp1890263-modphp-buggy-focal
$
I verified that the fix uploaded for jammy that's now available in the
release, does indeed resolve the issue for impish:
###
### Impish Test Case for BUGGY Behavior ###
###
$ lxc launch ubuntu-daily:impish
This bug was fixed in the package php8.1 - 8.1.2-1ubuntu2
---
php8.1 (8.1.2-1ubuntu2) jammy; urgency=medium
* d/control: Add transitional packages and Breaks/Replaces to force
upgrade from earlier mod-php's to version 8.1.
(LP: #1890263)
* d/rules: Don't fill up build log
** Changed in: php-defaults (Ubuntu Jammy)
Status: New => In Progress
** Changed in: php8.1 (Ubuntu Jammy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/php8.1/+git/php8.1/+merge/419245
--
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
Here we should note that some pieces come from phpM.N, others from php-
common:
$ pkg-source php-common
php-defaults
$ pkg-source libapache2-mod-php
php-defaults
$ pkg-source libapache2-mod-php7.2
php7.2
$ pkg-source libapache2-mod-php7.4
php7.4
$ pkg-source libapache2-mod-php8.0
php8.0
$
Earlier I had speculated:
> I wonder if there needs to be a dependency added for the
> libapache2-mod-php virtual package.
However I don't think this will work as a solution, because already we
have libapache2-mod-php depending on libapache2-mod-phpM.N, so adding a
dependency in the opposite
For testing method C, I've backported all the relevant PHP pieces to
this PPA:
https://launchpad.net/~bryce/+archive/ubuntu/modphp-upgrade-
lp1890263-unfixed-backports
(C.1) Considering only bionic, installation style 1 works as expected:
$ sudo apt-get install libapache2-mod-php
The
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
** Changed in: php8.1 (Ubuntu)
Assignee: (unassigned) => Bryce Harrington (bryce)
** Also affects: php7.4 (Ubuntu Jammy)
Importance: Medium
Assignee: Bryce Harrington (bryce)
Status: Triaged
** Also affects: php8.0 (Ubuntu Jammy)
Importance: Medium
Assignee: Bryce
** Changed in: php8.1 (Ubuntu)
Status: New => Triaged
** Changed in: php8.1 (Ubuntu)
Importance: Undecided => Medium
--
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
** Also affects: php8.1 (Ubuntu)
Importance: Undecided
Status: New
--
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
** Tags added: server-todo
** Changed in: php8.0 (Ubuntu)
Assignee: (unassigned) => Bryce Harrington (bryce)
** Changed in: php7.4 (Ubuntu)
Importance: Undecided => Medium
** Changed in: php8.0 (Ubuntu)
Importance: Undecided => Medium
** Changed in: php7.4 (Ubuntu)
Status:
** Also affects: php8.0 (Ubuntu)
Importance: Undecided
Status: New
--
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
Hmm. Yes, seems pretty straightforward to reproduce the problem in
lxc. At the end of the upgrade it offers to remove mod php 7.2:
Reading state information... Done
Remove obsolete packages?
69 packages are going to be removed.
Continue [yN] Details [d]d
Remove: libapache2-mod-php7.2
Note: I'll leave the two containers as-is for now in case you want any
logs in them to be checked.
--
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
26 matches
Mail list logo
