| Summary: | Cleanup number of Zabbix Ebuilds in tree, look into making 3.x new stable | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Matthew Marlowe (RETIRED) <mattm> |
| Component: | Current packages | Assignee: | Matthew Marlowe (RETIRED) <mattm> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | axiator, hydrapolic, mark+gentoobugs, patrick, spiderx |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Matthew Marlowe (RETIRED)
2018-11-08 05:44:51 UTC
3.4.15 is in tree. will wait 30 days, and if there is no urgent issues ...will push for 3.4.15 becoming new stable and removing some of the prior versions. 3.4 series is eol, maybe jump right to 4.0.3? I'm curious - 3.4.x ist EOL and unsupported, the current (supported) version is 4.0.x. Is there a good reason why you have to keyword 4.0.x? I mean is it really *that* unstable/volatile/beta, even if upstream tells it's stable? 4.0.x is still keyword masked mostly because I have confirmed it works for me, but almost no other user feedback. It was a big bump at the time. Its proaby about time to unmask it for general testing, and if we can eventually marked stable...slowly prune and deprecate all ebuilds before 4.0...although we may have to keep the latest in each major release set for awhile. i`m on 4.0.x too, no problems (In reply to Matthew Marlowe from comment #4) > 4.0.x is still keyword masked mostly because I have confirmed it works for > me, but almost no other user feedback. Well, for me it's a little bit a psychological barrier. I'm running ACCEPT_KEYWORDS="~amd64" but keyword masked is - in my eyes - a different, far far unstable/dangerous matter - so I'd very relucantly (and only if really necessary) use such packages whereas I don't mind using unstable ones. Updated from 3.4.15 to 4.0.4. All components (agent, server, web frontend) work fine. Looks like 4.0.5 was added to tree today with ~amd64, ~x86 keywords. 4.0.5 should be relatively stable..the last few 4.0.x releases have been almost nothing but bugfixes. https://www.zabbix.com/rn/rn4.0.5 Bump for 4.0.6 today (~amd64/~x86) Plan for tree cleaning/new stable: Zabbix 2.2 branch gets removed from portage after 3.0.26 gets marked stable. Zabbix 3.0.26 should be marked as stable candidate after another 30-60 days to ensure we have enough feedback (relatively new commit). All prior 3.0.x ebuilds get removed at tht point. Zabbix 3.2.x ebuilds should be removed asap? Deprecated upstream, might have security issues? Zabbix 3.4.15 should be the only 3.4.x ebuild retained, but perhaps with no keywords as upstream recommends either 3.0.26 or 4.0.6. Anyone disagree with the above? Thanks, looks great! (In reply to Matthew Marlowe from comment #9) > Plan for tree cleaning/new stable: https://www.zabbix.com/life_cycle_and_release_policy 2.2 still has some official lifetime left. I think it's a good idea to keep LTS versions until they reach EOL. Hmm... 2.2 EOL now! In portage version 4.4 already available. I'm update from 4.2 and no problems for me. May be make sense do stable version 4.0? The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9dd83ba9636be855abf97ac682cd55be731f0ce2 commit 9dd83ba9636be855abf97ac682cd55be731f0ce2 Author: Miroslav Šulc <fordfrog@gentoo.org> AuthorDate: 2020-02-28 15:01:10 +0000 Commit: Miroslav Šulc <fordfrog@gentoo.org> CommitDate: 2020-02-28 15:02:00 +0000 net-analyzer/zabbix: bumps + security fixes + rewritten + removed obsolete 1) many changes and improvements 2) config directory and files are not writeable by zabbix 3) creation of pid file disabled in zabbix, using s-s-d instead Bug: https://bugs.gentoo.org/629882 Bug: https://bugs.gentoo.org/709926 Bug: https://bugs.gentoo.org/629884 Closes: https://bugs.gentoo.org/665960 Closes: https://bugs.gentoo.org/670652 Package-Manager: Portage-2.3.89, Repoman-2.3.20 Signed-off-by: Miroslav Šulc <fordfrog@gentoo.org> net-analyzer/zabbix/Manifest | 10 +- net-analyzer/zabbix/files/2.2/init.d/zabbix-agentd | 28 - net-analyzer/zabbix/files/2.2/init.d/zabbix-proxy | 27 - net-analyzer/zabbix/files/2.2/init.d/zabbix-server | 26 - .../zabbix/files/2.2/patches/zbx7479.patch | 83 --- .../zabbix/files/2.2/patches/zbx8151.patch | 53 -- net-analyzer/zabbix/files/2.2/zabbix_agent.conf | 81 --- net-analyzer/zabbix/files/2.2/zabbix_agentd.conf | 278 --------- net-analyzer/zabbix/files/2.2/zabbix_proxy.conf | 519 ---------------- net-analyzer/zabbix/files/2.2/zabbix_server.conf | 546 ----------------- net-analyzer/zabbix/files/3.0/init.d/zabbix-agentd | 28 - net-analyzer/zabbix/files/3.0/init.d/zabbix-proxy | 27 - net-analyzer/zabbix/files/3.0/init.d/zabbix-server | 26 - net-analyzer/zabbix/files/3.0/zabbix_agent.conf | 81 --- net-analyzer/zabbix/files/3.0/zabbix_agentd.conf | 390 ------------ net-analyzer/zabbix/files/3.0/zabbix_proxy.conf | 674 --------------------- net-analyzer/zabbix/files/3.0/zabbix_server.conf | 635 ------------------- .../zabbix/files/zabbix-3.0.30-mysql8.patch | 17 + .../zabbix-3.0.30-security-disable-PidFile.patch | 49 ++ ...fix.patch => zabbix-4.0.18-modulepathfix.patch} | 0 .../zabbix-4.0.18-security-disable-PidFile.patch | 49 ++ net-analyzer/zabbix/files/zabbix-agentd.init | 20 + net-analyzer/zabbix/files/zabbix-agentd.service | 10 +- .../zabbix-jmx-proxy => zabbix-jmx-proxy.conf} | 0 .../zabbix-jmx-proxy => zabbix-jmx-proxy.init} | 0 net-analyzer/zabbix/files/zabbix-proxy.init | 20 + net-analyzer/zabbix/files/zabbix-proxy.service | 8 +- net-analyzer/zabbix/files/zabbix-server.init | 19 + net-analyzer/zabbix/files/zabbix-server.service | 11 +- net-analyzer/zabbix/zabbix-2.2.16-r1.ebuild | 340 ----------- net-analyzer/zabbix/zabbix-3.0.28.ebuild | 330 ---------- .../{zabbix-3.4.15.ebuild => zabbix-3.0.30.ebuild} | 204 ++++--- net-analyzer/zabbix/zabbix-4.0.13.ebuild | 332 ---------- .../{zabbix-4.2.7.ebuild => zabbix-4.0.18.ebuild} | 207 ++++--- net-analyzer/zabbix/zabbix-4.4.0-r1.ebuild | 333 ---------- .../{zabbix-4.4.5.ebuild => zabbix-4.4.6.ebuild} | 204 ++++--- 36 files changed, 523 insertions(+), 5142 deletions(-) |