On Wed, Feb 08, 2017 at 09:07:56AM -0800, Kevin Oberman wrote:
> On Tue, Feb 7, 2017 at 11:19 PM, Kevin Oberman wrote:
>
> > On Tue, Feb 7, 2017 at 5:02 PM, Kevin Oberman wrote:
> >
> >> On Tue, Feb 7, 2017 at 10:41 AM, Lars Engels
On Tue, Feb 7, 2017 at 11:19 PM, Kevin Oberman wrote:
> On Tue, Feb 7, 2017 at 5:02 PM, Kevin Oberman wrote:
>
>> On Tue, Feb 7, 2017 at 10:41 AM, Lars Engels
>> wrote:
>>
>>> On Mon, Feb 06, 2017 at 05:48:23PM +0100, Thorsten
On Tue, Feb 7, 2017 at 5:02 PM, Kevin Oberman wrote:
> On Tue, Feb 7, 2017 at 10:41 AM, Lars Engels wrote:
>
>> On Mon, Feb 06, 2017 at 05:48:23PM +0100, Thorsten Baumeister wrote:
>> > Hi folks,
>> > last weekend I tried to install the port icingaweb2
On Tue, Feb 7, 2017 at 10:41 AM, Lars Engels wrote:
> On Mon, Feb 06, 2017 at 05:48:23PM +0100, Thorsten Baumeister wrote:
> > Hi folks,
> > last weekend I tried to install the port icingaweb2 on a patched
> > FreeBSD 11.0 server. 'make' worked fine, but 'make install'
On Mon, Feb 06, 2017 at 05:48:23PM +0100, Thorsten Baumeister wrote:
> Hi folks,
> last weekend I tried to install the port icingaweb2 on a patched
> FreeBSD 11.0 server. 'make' worked fine, but 'make install' failed.
> Has anyone seen / resolved this problem?
>
> ===> Checking if icingaweb2
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
On Mon, Feb 6, 2017 at 8:48 AM, Thorsten Baumeister <
thorsten_baumeis...@gmx.de> wrote:
> Hi folks,
> last weekend I tried to install the port icingaweb2 on a patched FreeBSD
> 11.0 server. 'make' worked fine, but 'make install' failed. Has anyone seen
> / resolved this problem?
>
> Thorsten
>
>