Created attachment 149089 [details]
patch to update 2.0.13
update to 2.0.13
Created attachment 149090 [details]
poudriere testport of zabbix2-agent
Created attachment 149091 [details]
poudriere testport log of zabbix2-server
Created attachment 149092 [details]
poudriere testport log of zabbix2-frontend
Created attachment 149093 [details]
poudriere testport log of zabbix2-proxy
Looks ok, assuming those @dir lines are for empty directories.
Do we really need zabbix 2.0, 2.2 and 2.4?
While pondering that question, I'll promote this PR.
zabbix 2.0, 2.2 is LTS and many people use this version.
Could you please commit this patch ?
We really need this update!
(In reply to alex.deiter from comment #7)
> Could you please commit this patch ?
> We really need this update!
You need to understand how this works (besides the fact that I wasn't on the PR CC list and didn't see the question)
1) The PR gets submitted
2) The PR gets a preliminary review
3) It gets promoted if that looks good
4) Somebody picks it up out of the patch-ready pool does a final review
5) If the final review is good, it gets committed.
While it's in the pool (not really a queue) nobody is in charge of it, so nobody hears your pleas. Only people on the CC list would. Also, some PRs have been in the patch-ready pool for over a month (not great but true) so pleading 1 day after the PR gets promoted, one that is only 4 days old in entirety, doesn't go over well either.
I'll try to do this in a bit.
A commit references this bug:
Date: Sun Nov 9 11:34:25 UTC 2014
New revision: 372356
net-mgmt/zabbix2: Upgrade version 2.0.12 => 2.0.13
Submitted by: maintainer (pakhom706 - gmail)