net-mgmt/icingaweb2-module-reporting: Update to 1.0.2

net-mgmt/icinga*: Take a couple of icinga ports

joneum offered me to take over the icinga2 ports a while ago.
Approved by:	joneum (private mail)

*/*: Unbreak with php84

These ports were initially marked to IGNORE with php84 as their runtime
dependencies were BROKEN. As all of the runtime dependencies has been
fixed for ther requirements unmark these ports. Although these ports
build perfectly with php84 but there might still be runtime issues with
these ports with php84. The maintainers are requested to do some runtime
checks for these ports.

Approved by:	portmgr (blanket)

php: unbreak bulk -a

net-mgmt/icingaweb2-module-reporting: Update to 1.0.1

Changelog:
https://github.com/Icinga/icingaweb2-module-reporting/releases/tag/v1.0.1

Sponsored by:	Netzkommune GmbH

audio/opus: bump consumers after update to 1.4

net-mgmt/icingaweb2: Update to 2.11.4

Changelog:
-Add/Edit dashlet not possible
-Custom library path + custom library, without slash in its name, results in
exception
-Reflected XSS vulnerability in User Backends config page

Sponsored by:	Netzkommune GmbH

net-mgmt/icingaweb2-module-reporting: Update to 0.10.0

Sponsored by:	Netzkommune GmbH

net-mgmt/icingaweb2-module-ipl: MOVED to net-mgmt/icinga-php-library/

The Icinga Project moved this module to icinga-php-library:
https://github.com/Icinga/icingaweb2-module-ipl/blob/master/README.md

Sponsored by:	Netzkommune GmbH

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

cleanup: remove transitive py27 deprecation (www/chromium)

net-mgmt/icinga*: - Take Maintainership

Sponsored by:	Netzkommune GmbH

*: Drop maintainership on most of my ports.

Unfortunately I cannot give them the love they deserve at the moment.

One more small cleanup, forgotten yesterday.
Reported by:	lwhsu

Remove # $FreeBSD$ from Makefiles.

Mark ports recursively depending on Python 2.7 for expiration on June 23.

For ports optionally dependending on Python 2.7, just mark those options
as expired. Remove konquerer from the x11/kde-baseapps metaport and bump
its PORTREVISION.

Submitted by:	rene
Reviewed by:	portmgr, adridg, ehaupt, lme, madpilot, pizzamig, se, sunpoet, yuri
Approved by:	portmgr
Differential Revision:	https://reviews.freebsd.org/D28665

Fix dependency syntax

PR:		210021
Submitted by:	fluffy@
Reported by:	mat@

net-mgmt/icingaweb2 and modules:
- Drop stale dependency on www/zendframework1
- FLAVORize for all php releases
- Improve OPTIONS for supported databases

PR:		242664
Submitted by:	fluffy@

net-mgmt/icingaweb2-module-reporting: Update to 0.9.2

Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.

PR:		238330

Add net-mgmt/icingaweb2-module-reporting:

Icinga Reporting is the central component for reporting related functionality
in the monitoring web frontend and framework Icinga Web 2. The engine allows
you to create reports over a specified time period for ad-hoc and scheduled
generation of reports. Other modules use the provided functionality in order to
provide concrete reports.

WWW: https://github.com/Icinga/icingaweb2-module-reporting