Security Support for php 7.4 will end on 28th November, 2022 and we are planning to remove php 7.4 after that from the tree. So in preparation of that and for tracking purposes we are checking which ports actually fails without php 7.4 and notifying the relevant maintainer to check if viable update options are available to make it work on later versions of PHP. We still have a lot of time in hand to update and fix. Hence please do not get alarmed with this ticket. As mentioned again this is for tracking purposes only and hopefully by the time php 7.4 expires we will have a working version of this port for php 8.*. So there are two options here for the MAINTAINER: 1. If you have a version that works with php 8.* please commit and close this ticket. 2. In case you want it to expire with php 7.4 please add the following to the Makefile, commit and close this ticket DEPRECATED= Requires php 7.4 which is set to expire on 2022-11-29 EXPIRATION_DATE=2022-11-28
Zabbix 6.0 LTS will not support PHP 8.0, Zabbix 6.2 onwards will.
Let's keep this ticket open and track the upstream changes. Will decide later.
(In reply to Juraj Lutter from comment #1) I can see that there are other LTS release of zabbix in the tree mainly 4 and 5. I have marked the entire zabbix3* as DEPRECATED. Can you please advise me whether if zabbix*-server can function without the frontend. I know that the agent and proxy might be useful to keep. I am still confused with zabbix*-java and it's purpose over zabbix*-proxy.
(In reply to Muhammad Moinur Rahman from comment #3) Server will work without frontend, but user won't be able to get any reasonable data from it. Regarding -proxy and -java: -proxy is a "leightweighted" kind of server, that communicates with the real server (proxy is used to monitor "isolated islands"). -java is a "JMX proxy" that monitors java applications.
(In reply to Juraj Lutter from comment #4) Thanks for the clarification. I believe in that case we can just keep the -proxy, -java and -agent for peoples who are using FreeBSD in a Linux world so that they can still monitor FreeBSD hosts with their Zabbix Server installed on a Linux host. This note is applicable just for zabbix4- and zabbix5-; while zabbix54- is upgraded to zabbix62-.
Oops .. Looks like you are not the maintainer of zabbix4- and zabbix5-. Sorry for the noise. :[]
(In reply to Muhammad Moinur Rahman from comment #6) Essentially, I maintain also zabbix5 (as current maintainer is unresponsive).
For example, I use zabbix frontend on FreeBSD and it is not a viable for me to run frontend on other OS (as I don't have any other OS's).
(In reply to Juraj Lutter from comment #7) Noted. It makes things easier. And yes neither do I for my hosted service. But I am pretty much disappointed on Zabbix's Roadmap. I used to like this product a lot but eventually their commercialization and not keeping up the momentum looks very slow to me. Like when you have commercial support you should have better developers and more aggressive roadmaps. They are releasing LTS6 with php74 which will expire in 6 months within their release. Or maybe they are not FreeBSD friendly as other Linux distros seem to carry over legacies(php72 php73) as they have their own support systems/maintainers on those with friendly donations.
The branch main has been updated by cy: URL: https://cgit.FreeBSD.org/ports/commit/?id=0773873baee5474cc70de8912d2962ead58f155b commit 0773873baee5474cc70de8912d2962ead58f155b Author: Cy Schubert <cy@FreeBSD.org> AuthorDate: 2022-02-16 10:11:37 +0000 Commit: Cy Schubert <cy@FreeBSD.org> CommitDate: 2022-02-16 10:27:29 +0000 net-mgmt/zabbix6-frontend: Ignore for PHP80 and PHP81 Zabbix-frontend still requires PHP74; mark for deprecation pending updated PHP requirement. Reported by: bofh
cy@: As mentioned earlier no action is required from your end. This is just for tracking purposes only.
@otis do you have a plan for zabbix 6.2 in the tree? 5.4 has reached it's eol on 31st March 2022.
Yes, as soon as it will be released. Now it's in beta3 stage.
(In reply to Juraj Lutter from comment #13) I think it has been released on 30th May. https://www.zabbix.com/life_cycle_and_release_policy And as 5.4 has also reached EOL maybe it's better to mark it DEPRECATED and be removed before next quarterly.
I've set zabbix54 to expire on 2022-06-29
(In reply to Juraj Lutter from comment #15) Thanks a lot.
FYI: As of 6.0.5, zabbix frontend seems to run with php 8.0 (although, I did not tested it myself yet).
ANd, for the record, I've introduced zabbix62 ports already.
(In reply to Juraj Lutter from comment #18) Thanks a lot. (In reply to Juraj Lutter from comment #17) If you can test it successfully just update the Title of this bug.
Zabbix 6.2.1 work for me with PHP 8.1.9.
(In reply to VVD from comment #20) zabbix 6.2.x fully supports php 8.0 and php 8.1.
Can this be closed since these ports will never be PHP 8 compatible. 6.2 is in ports and it is reported to work.
(In reply to Michael Osipov from comment #22) This is an exception. We will keep this ticket open for a different purpose. We are not going to delete the entire zabbix{4|5|6}-* as there might be other users who will need zabbix-client for these versions as they might be running zabbix on a different platform. So we will remove zabbix-frontend only which requires certain amount of work in the zabbix ports too. And this ticket is here so that I don't forget this. :) So this ticket will remain open until end.
FWIW, zabbix6-frontend supports php 8.0 (and I'm actively using it).
(In reply to Juraj Lutter from comment #24) And zabbix62-frontend supports php 8.1.
Recent 6.0 supports PHP 8.1 as well.
(In reply to Muhammad Moinur Rahman from comment #23) This makes sense. Likely the scope of the ticket needs to be narrowed down.
(In reply to Juraj Lutter from comment #24) I am updating the title as per your comment. :)
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=30344125c070296a9a406cdfb8c2e95f9433826f commit 30344125c070296a9a406cdfb8c2e95f9433826f Author: Muhammad Moinur Rahman <bofh@FreeBSD.org> AuthorDate: 2022-12-05 14:38:54 +0000 Commit: Muhammad Moinur Rahman <bofh@FreeBSD.org> CommitDate: 2022-12-05 14:40:36 +0000 net-mgmt/zabbix4-frontend: Cleanup - Requires php74 which was EOL on 2022-11-28 PR: 261634 Approved by: otis Sponsored by: Bounce Experts MOVED | 1 + net-mgmt/Makefile | 1 - net-mgmt/zabbix4-frontend/Makefile (gone) | 31 - net-mgmt/zabbix4-server/Makefile | 5 - net-mgmt/zabbix4-server/pkg-plist.frontend (gone) | 956 ---------------------- 5 files changed, 1 insertion(+), 993 deletions(-)
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=9f72f354a11e8d167b2087877b69f755e9e8a3a0 commit 9f72f354a11e8d167b2087877b69f755e9e8a3a0 Author: Muhammad Moinur Rahman <bofh@FreeBSD.org> AuthorDate: 2022-12-08 17:53:46 +0000 Commit: Muhammad Moinur Rahman <bofh@FreeBSD.org> CommitDate: 2022-12-08 17:54:56 +0000 net-mgmt/zabbix5-frontend: Cleanup - Requires php74 which was EOL on 2022-11-28 PR: 261634 Approved by: otis Sponsored by: Bounce Experts MOVED | 1 + net-mgmt/Makefile | 1 - net-mgmt/zabbix5-frontend/Makefile (gone) | 30 - net-mgmt/zabbix5-server/Makefile | 5 - net-mgmt/zabbix5-server/pkg-plist.frontend (gone) | 1211 --------------------- 5 files changed, 1 insertion(+), 1247 deletions(-)