*/*php86*: Sunrise Please DO NOT use this version in production, it is an early test version. For upgrade notes please visit: https://github.com/php/php-src/blob/php-8.6.0alpha1/UPGRADING Changelog: https://github.com/php/php-src/blob/php-8.6.0alpha1/NEWS63b6120db0
Port details
net-mgmt/icingaweb2-module-vsphere1.1.1_1
Automated import of your VMs and Physical Host from VMware Sphere
- Maintainer
- ports@FreeBSD.org
- Packages
- icingaweb2-module-vsphere-php82 1.1.1_1, icingaweb2-module-vsphere-php83 1.1.1_1, icingaweb2-module-vsphere-php84 1.1.1_1, icingaweb2-module-vsphere-php85 1.1.1_1
- Upstream
- up to date
- CPE
- none, CVEs only via VuXML
- WWW
- https://github.com/Icinga/icingaweb2-module-vsphere
- Links
- cgit · VuXML
Unaddressed (0) · The CVE record lists this version as affected, no VuXML entry names the CVE
None. There is no CVE without a VuXML entry for this version.
VuXML only (0) · listed, port not fixed yet
None.
pkg audit reports nothing for this version.Fixed (0)
No VuXML entries for this package.
Commits (21)
*/*php81*: Sunset95b3559914
net-mgmt/icingaweb2*: Fix more breakage Fix more ports broken by 2a12b7cab556 and f95fbf3e2406 that don't have a direct dependency on net-mgmt/icinga-php-library or net-mgmt/icinga-php-thirdparty. Mark them all IGNORE_WITH_PHP=81 This should fix poudriere bulk -a.3b3d96867c
net-mgmt/icingaweb2-module-vsphere: drop maintainership net-mgmt/icingaweb2-module-vsphere: drop maintainership637e3d983d
*/*: 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)6373a1df1f
*/*: Mark IGNORE_WITH_PHP=84 These ports are currently not compatible with php84 and is only a limited set of ports. There might be more ports which has runtime issues. Please check if your ports are compatible with php84 and if not pleae mark them IGNORE_WITH_PHP=84 Approved by: portmgr (blanket)c00a7b36df
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 GmbHf63dc16ac2
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)fb16dfecae
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. This commit implements such a proposal and moves one of the WWW: entries of each pkg-descr file into the respective port's Makefile. A heuristic attempts to identify the most relevant URL in case there is more than one WWW: entry in some pkg-descr file. URLs that are not moved into the Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr files in order to preserve them. There are 1256 ports that had no WWW: entries in pkg-descr files. These ports will not be touched in this commit. The portlint port has been adjusted to expect a WWW entry in each port Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as deprecated. Approved by: portmgr (tcberner)b7f05445c0
net-mgmt/icingaweb2-module-vsphere: Update to 1.1.1 Sponsored by: Netzkommune GmbH1e0341d5cf
net-mgmt/icinga*: - Take Maintainership Sponsored by: Netzkommune GmbH8e7206467b
*: Drop maintainership on most of my ports. Unfortunately I cannot give them the love they deserve at the moment.c4fd7792f9
One more small cleanup, forgotten yesterday. Reported by: lwhsucf118ccf87
Remove # $FreeBSD$ from Makefiles.305f148f48
Fix dependency syntax PR: 210021 Submitted by: fluffy@ Reported by: mat@4fc808df0c
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@7fee233362
net-mgmt: Add missing USES={gnome,php}152c8d7c3cBump 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: 238330ea8c8ec7da
net-mgmt/icingaweb2-module-vsphere: Spell USE_PHP correctlya65d8ad623
Bump PORTREVISION for ports depending on the canonical version of GCC defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t GCC 8.2 under most circumstances. 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, as a double check, everything INDEX-11 showed depending on lang/gcc7. PR: 231590a9f015d155
Add new port net-mgmt/icingaweb2-module-vsphere: In case you want to have an automated import of your Virtual Machines and/or Physical Host from VMware Sphere (vCenter) into your Icinga monitoring system this module might be what you have been looking for. At the time of this writing, the main purpose of this module is being a Import Source provider for the Icinga Director. WWW: https://github.com/Icinga/icingaweb2-module-vspherec578b3cbaa