Date: Tue, 7 Feb 2017 11:46:33 +1100 From: Dewayne Geraghty <dewaynegeraghty@gmail.com> To: Thorsten Baumeister <Thorsten_Baumeister@gmx.de> Cc: freebsd-stable stable <freebsd-stable@freebsd.org> Subject: Re: FreeBSD 11.0: Installation of icingaweb2 Message-ID: <CAGnMC6okBkb%2BpHNZCfYkRAuaX7KqFhQenGa8DzSOAtTw2sgjgg@mail.gmail.com> In-Reply-To: <2650EB83-6D80-4C75-9271-66AB81D0A08E@tba.home> References: <2650EB83-6D80-4C75-9271-66AB81D0A08E@tba.home>
next in thread | previous in thread | raw e-mail | index | archive | help
Thorsten, This is a ports issue so should go to the freebsd-ports mailing list (if at all) Your best option is to file a PR so that the maintainer of the port can update the plist file. You'll occassionally see this sort of package-build failure when the maintainer has missed a test package step. If you're shy, you could write to the maintainer directly but then others can't see that the issue has been raised (and presumably being raised/addressed). In the meantime - you could adjust the plist yourself to reflect the new reality. Though expedient this is not recommended. Filing a PR is highly recommended to benefit everyone and have a fix properly applied. Regard.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGnMC6okBkb%2BpHNZCfYkRAuaX7KqFhQenGa8DzSOAtTw2sgjgg>