So far everything looks fine. I am even using PHP 8.1 in production for a week now, without any issues. So I'd like to move the packages to [extra]. The remaining blocker is nextcloud though. What is the best option to resolve this? 1) Remove the version constraint 2) same as above + try to apply the upstream patch: https://github.com/nextcloud/server/pull/29862 3) temporary depend on php7; I'd like to remove that package soon though 4) anything else? Greetings, Pierre On Sat, Jan 8, 2022 at 11:09 AM Pierre Schmitz <pierre@archlinux.de> wrote:
I have finished the rebuild of modules und pushed all packages into [testing]: . https://archlinux.org/todo/draft-php-81-module-rebuild/
Unfortunately there are two packages that had build issues: * libguestfs: No idea why it has a PHP module anyway. But this package does not compile with [extra] packages as well, so it is likely unrelated to PHP and probably cuased by an ocaml update. I used the repos archive from last month to build this package for now. * php-snuffleupagus: Does not pass tests with PHP 8.1 and there seems to be no upstream patches we could apply. (pkgstats usage is only 0.03%) I have disabled the failing tests for now.
Next is to check if there remain any incompatibilities aside from modules; e.g. the nextcloud version constrain we talked about. I might create a todo list as well.
Removing php7 and everything that depends on it will be done in a separate step once php 8.1 has moved into [extra].
Greetings,
Pierre
On Sun, Jan 2, 2022 at 2:00 PM Pierre Schmitz <pierre@archlinux.de> wrote:
So, its been some time and things seem to look a lot better now. I see the nextcloud patch was merged some time ago as well. We might need to aplly it manually as I don't see a patch release for some reason. Most things work fine with PHP 8.1. So far the issues are mostly arbitrary versions constraints or actual bugs that would be broken on 8.0 as well. (e.g. conflicting type hints in sub classes)
My plan is to prepare updating the php package to 8.1 and create a rebuild list. At the same time I'll remove the php7 package. It's been a year now and I would consider anything that only works on php7 as unmaintained. Here is a list of php7-packages that would be affected: * mediawiki: works fine with PHP 8 * drupal: should work on PHP 8 according to upstream * zabbix-frontend-php: unclear; I read that it might have been fixed in version 5.4 * phpvirtualbox: probably broken; latest release was in 2018. This should be remvoed fro mthe repos imho * web-news: brobably broken; latest release was in 2009. Also should be removed. * phppgadmin: probably broken; development seem slow or stalled on PHP 8 support. We might need to drop this as well * phpldapadmin: might work. New version was just released and claims to support anything newer than PHP 7.2 * dokuwiki: unclear; might need patches
Greetings,
Pierre
On Mon, Dec 6, 2021 at 6:53 PM David Runge <dave@sleepmap.de> wrote:
On 2021-12-06 18:32:49 (+0100), Pierre Schmitz via arch-dev-public wrote:
In general we could provide PHP 7 till its end of life in about eleven months. But I don't think its worth providing several different minor versions at the same time.
I agree.
This is not how semver is supposed to work :-) (Someone should check Nextcloud but looking at their PR it mostly seems about tests, documentation and deprecations but no hard errors).
I would definitely wait until the PR for nextcloud [1] has settled (it's still a draft). The changes apply to 23.0.0 (which has been in testing only for a few hours). Do note, that effects of php 8.1.0 on the nextcloud-apps is completely unaccounted for in this scenario.
I would like to have nextcloud 23.0.0 in [community] before we proceed with any testing with php 8.1.0 if that is fine with you.
Best, David
-- Pierre Schmitz, https://pierre-schmitz.com
-- Pierre Schmitz, https://pierre-schmitz.com
-- Pierre Schmitz, https://pierre-schmitz.com