Security support for php74 will expire on 28th November, 2022. Currently this is just a placeholder to track what ports fails to build when there is no php74 and check whether if it is possible to update them to support later versions of PHP like 8.0 or 8.1 or newer upcoming version. I have started exp-run to check which ports fails to build without php74 and add those as dependencies of this bug. There is nothing to be alarmed with this bug at the moment. Details about supported PHP versions and their EOL are available from where: https://www.php.net/supported-versions
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=5ebfc20bc191bf6c2bf15560118e5f4bdf8be515 commit 5ebfc20bc191bf6c2bf15560118e5f4bdf8be515 Author: Muhammad Moinur Rahman <bofh@FreeBSD.org> AuthorDate: 2022-02-01 08:03:33 +0000 Commit: Muhammad Moinur Rahman <bofh@FreeBSD.org> CommitDate: 2022-02-01 08:08:43 +0000 lang/php74{-extensions}: Mark DEPRECATED Security support for php74 will expire on 28th November, 2022. For details please see: https://www.php.net/supported-versions EXPIRATION_DATE has been set 1 day after the EOL. A metabug has been created to track which ports explicitly depends on php74{-extensions} only; which is available at: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261604 PR: 261604 Approved by: tz (private email) Sponsored by: Bounce Experts lang/php74-extensions/Makefile | 3 +++ lang/php74/Makefile | 3 +++ 2 files changed, 6 insertions(+)
Muhammad, can you explain why you completely flagged */horde*?: =================================================== commit 9645c923bf918a0b1ecceef7595ba3c3c2184702 Author: Muhammad Moinur Rahman <bofh@FreeBSD.org> Date: 2022-06-12T01:39:43+02:00 */horde*: Ignore with php82 =================================================== I have been testing for an upcoming WebSVN update pear-Horde-Text-Diff in and out with 8.0, 8.1, and 8.2 for two weeks now (https://github.com/websvnphp/websvn/issues/153#issuecomment-1242210463). I certain that there are some Horde ports which are broken, but certainly NOT ALL. Can you point me to a log file which shows the breakage? When I add this (https://github.com/michael-o/freebsd-ports/commit/27bb493c03b918c98cda3262e808c298fb778320): ${PEARDIR}/Horde/Text/Diff.php:textproc/pear-Horde_Text_Diff@${PHP_FLAVOR} and remove "IGNORE_WITH_PHP=80 81 82" from Mk/Uses/horde.mk I have zero failures, especially that in Bug 266443 PEAR now works across the board.
(In reply to Michael Osipov from comment #2) FIRST OF ALL PLEASE DO NOT CROSS POST YOUR QUERIES AS THIS SPECIFIC QUERY IS NOT RELATED TO THIS BUG. I have tried to explain you the procedure on the other bug you mentioned. If you see my commit it was dated on 2022-06-12 and depends on the state of horde or whatever other ports that depends on php8.2 and have failed to build. I definitely do not have the resources to maintain failed logs from 2 months ago hence I cannot share the logs. If you have specific queries on other frameworks or ports which do not have support for php 8.0/8.1/8.2 please create a new ticket and request them to update the ports according to your shared URLs and knowledge. We are all limited to the work we do. And it's not possible for a single committer to do build tests and functionality tests as there are hundreds of ports that might depend on php*. Like for say horde. When I imported php80 and php81 it used to build perfectly but they were not usable with php80 and php81 and were only discovered by the users; not by us. From your queries it looks like you are more of a ports person rather than a pkg person. The main difference when a committer makes a commit s/t/he/y must make sure that the pkg bulk build are not failing or in an unusable state as the "latest" builds are automatically triggered when a commit is made. Hence we do so many things at a certain point of a tree so that it's bulk buildable. Which ports user often do not have to face. So while you are looking at the problem from a smaller view we have to look at the bigger picture and often do stuffs which might not make logical sense for the ports users.
(In reply to Muhammad Moinur Rahman from comment #3) Let me crunch on this and see what I can do regarding horde.mk.
FTR: Bug 266552
(In reply to Michael Osipov from comment #5) This bug is in no way related to the reference bug you have mentioned. In case you want to follow which ports are currently marked to IGNORE with different versions you can have a look at: https://pkg.bounce-experts.com/ The names testPHP74, testPHP80, testPHP81 and testPHP82 are self explanatory. And these builds all ports dependent on php every night.
(In reply to Muhammad Moinur Rahman from comment #6) AWESOME, thank you.