Remove net-mgmt/zabbix24-(agent|frontend|proxy|server)
ClosedPublic
Actions

Authored by dbaio on May 26 2017, 11:46 PM.

Details

Reviewers

Commits

rP442033: Remove net-mgmt/zabbix24-(agent|frontend|proxy|server)

Summary

Remove net-mgmt/zabbix24-(agent|frontend|proxy|server)

Upstream has declared this version EoL in 2016 (Q1)

PR:	219563
Submitted by: pg@pakhom.spb.ru (maintainer)
Approved by:	garga (mentor)
Differential Revision:	https://reviews.freebsd.org/D10949

Test Plan

$ make index
Generating INDEX-12 - please wait..--- describe.accessibility ---
--- describe.arabic ---
--- describe.archivers ---
--- describe.astro ---
--- describe.audio ---
--- describe.benchmark
[...]
--- describe.x11-fonts ---
--- describe.x11-servers ---
--- describe.x11-themes ---
--- describe.x11-toolkits ---
--- describe.x11-wm ---
 Done.

$ env PORTSDIR=$PWD Tools/scripts/MOVEDlint.awk
 9213: Final character is a dot: (Has expired: Starting with 10.0 functionality has been merged into base.)
 6401: news/husky-sqpack must be marked as resurrected

Diff Detail

Repository

rP FreeBSD ports repository

Lint

No Lint Coverage

Unit

No Test Coverage

Build Status

Buildable 9517
Build 9966: arc lint + arc unit

Event Timeline

dbaio created this revision.May 26 2017, 11:46 PM

Herald added a subscriber: mat. · View Herald TranscriptMay 26 2017, 11:46 PM

Harbormaster completed remote builds in B9517: Diff 28890.May 26 2017, 11:46 PM

garga accepted this revision.May 29 2017, 12:38 PM

This revision is now accepted and ready to land.May 29 2017, 12:38 PM

Closed by commit rP442033: Remove net-mgmt/zabbix24-(agent|frontend|proxy|server) (authored by dbaio). · Explain WhyMay 29 2017, 9:46 PM

This revision was automatically updated to reflect the committed changes.

mat added inline comments.May 29 2017, 10:01 PM

MOVED
9394–9397	There is probably a newer version of each those ports that people should be using, it should be put in the second field on each of those lines.

I let those fields empty because this is a standard release supported only for 6 months by Zabbix, users can now go to 3.0 LTS, version supported by 3 years or 3.2 standard, also supported by 6 months...

See this: Zabbix Life Cycle image

Anyway, should I still fill those fields?

Thank you.

In D10949#227377, @dbaio wrote:

I let those fields empty because this is a standard release supported only for 6 months by Zabbix, users can now go to 3.0 LTS, version supported by 3 years or 3.2 standard, also supported by 6 months...

See this: Zabbix Life Cycle image

Anyway, should I still fill those fields?

Thank you.

From the comments at the top of MOVED:

#     Moved to: Where the port was moved to, or which port users can
#               and should migrate to (category/portname); no entry
#               indicates that the port was deleted

So, well, you can leave them empty, because the port was deleted and not renamed. Now, you could try and be nice with our users, and tell them that, "hey, there is this zabbix version that you can use instead."

In D10949#227521, @mat wrote:

So, well, you can leave them empty, because the port was deleted and not renamed. Now, you could try and be nice with our users, and tell them that, "hey, there is this zabbix version that you can use instead."

You are right, I will open a review to insert a note informing the users.