Fix has been landed for focal's php7.4:
https://code.launchpad.net/~bryce/ubuntu/+source/php7.4/+git/php7.4/+merge/381283
** Changed in: apache2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The MP at [1] still is suggested as a solution to this issue going forward.
As Bryce coordinates the php uploads I'll leave that to him thou.
At least the overall migration is done, so maybe this can be a little
fix-follow up now.
[1]:
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/php7.4/+git/php7.4/+merge/381283
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850933
Title:
after upgrade 19.04 to
This is not 19.04->19.10 specific as no later than yesterday it affected
one of my client. I've reported the 16.04->18.04 bug against php-
defaults as it's the provider of mod_php, see LP: #1865218
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Still in our queue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850933
Title:
after upgrade 19.04 to 19.10, apache serves php code
To manage notifications about this bug go to:
Still in our queue.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1850933
Title:
after upgrade 19.04 to 19.10, apache serves php code
To manage notifications about this bug go to:
Offhand, wondering if we can take advantage of the fact that Ubuntu
provides one single php version per release. IOW, when a new php
version is installed, configurations should be pointing to that version;
this should work both ways - upgrading from php7.3 to php7.4, as well as
downgrading from
** Changed in: apache2 (Ubuntu)
Assignee: (unassigned) => Bryce Harrington (bryce)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850933
Title:
after upgrade 19.04 to 19.10, apache serves php
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850933
Title:
after upgrade 19.04 to 19.10, apache serves php code
To manage notifications about this bug go
Testing on the PPA confirmed that this would change the ordering but not
trigger the disable of mod-php7.2 as I expected.
Here the ordering from the log:
$ grep "mod-php7" apt.log
Removing libapache2-mod-php7.2 (7.2.24-0ubuntu0.19.04.1) ...
Package apache2 is not configured yet. Will defer
Hmm [1][2] which I'd consider to be needed here leave me somewhat confused.
I'm leaving my comfort zone here, IIRC breaks should always be versioned and
versioning the dependency here makes no sense.
OTOH a deconfigure would be enough so conflicts seems kind of hard for this.
And finally both
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/php7.3/+git/php7.3/+merge/375381
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850933
Title:
after upgrade 19.04 to
Just like the manual a2enmod the following resolves the situation as
well as now the old mod-php7.2 is "out-of-the-way".
$ apt install --reinstall libapache2-mod-php7.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After seeing that it even affects 16.04 -> 18.04 I was wondering and looked for
prior reports.
I found [1][2] and many similar, but no bug report.
[1]:
https://www.digitalocean.com/community/tutorials/how-to-upgrade-to-ubuntu-18-04
[2]: https://ubuntuforums.org/showthread.php?t=2393823
--
I saw in your dist-upgrade/apt-term.log file (first column are line numbers):
7245 Setting up libapache2-mod-php7.3 (7.3.11-0ubuntu0.19.10.1) ...
7247 Creating config file /etc/php/7.3/apache2/php.ini
I'd expect the two versions of libapache2-mod-php7 to have a conflicts
statement to enforce ordering.
Checking the same on 7.0 (xenial) -> 7.2 (bionic)
I'd expect this bug would have come up before if it was broken there as
well, so that should server as a good comparison.
There it is the
I have myself created a 19.04 system with:
- libapache2-mod-php + libapache2-mod-php7.2
- as expected on configure does this automatically
- This is from /var/lib/dpkg/info/libapache2-mod-php7.2.postinst
php_invoke enmod 7.2 apache2 $mod
- Created the most trivial PHP (index.php with
This is kind of useless, but I do not now know why I mentioned php5. I may have
seen mention of it but I'm not sure. I hope that you can see everything more
definitively in the logs. It looks to me like it was php7.2 that is mostly
recently mentioned in the logs, but you can read them better
Hi Christopher,
at least the answer for sharing privately would most likely be "send a mail".
You'll see mail addresses for me, Andreas and anyone else if you clock on their
username above the comments here on launchpad.
The path should only contain things triggered by the upgrade, not sure
what
Can I safely just zip up the entire dist-upgrade? It has some non- *.log files
and an entire subdirectory.
And Can I easily share these privately somehow? I'd rather not post the apache
error log broadly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for filing this bug in Ubuntu.
Could you please share the following logs:
- /var/log/dist-upgrade/*
- /var/log/dpkg.log
- /var/log/apache2/error.log
I'm trying to determine exactly from which version of each package did
you upgrade, and if there were any errors during that process.
You
Thanks for filing this bug in Ubuntu.
Could you please share the following logs:
- /var/log/dist-upgrade/*
- /var/log/dpkg.log
- /var/log/apache2/error.log
I'm trying to determine exactly from which version of each package did
you upgrade, and if there were any errors during that process.
You
It seems that something like the following my close the security hole:
`sudo a2enmod php7.3`
`systemctl restart apache2`
In which case, this should have been taken care of during the upgrade? Or when
php5 was deleted??
--
You received this bug notification because you are a member of
** Summary changed:
- after upgrade 18.04 to 18.10, apache serves php code
+ after upgrade 19.04 to 19.10, apache serves php code
** Description changed:
Apache2 has been working as a server on localhost (as well as on an fixed IP
when my laptop is at work) for years/many version.
- I just
24 matches
Mail list logo
