In case if one of net-mgmt/zabbix44-proxy or net-mgmt/zabbix44-server is installed, another failed with error below. root@sandbox:/usr/ports/net-mgmt/zabbix44-proxy # make install ===> Installing for zabbix44-proxy-4.4.5 ===> Checking if zabbix44-proxy is already installed ===> Registering installation for zabbix44-proxy-4.4.5 [sandbox.genesyslab.com] Installing zabbix44-proxy-4.4.5... pkg-static: zabbix44-proxy-4.4.5 conflicts with zabbix44-server-4.4.5 (installs files into the same place). Problematic file: /usr/local/bin/zabbix_js *** Error code 70 Stop. make[1]: stopped in /usr/ports/net-mgmt/zabbix44-proxy *** Error code 1 zabbix_js tool is new for 4.4.5. Guess, better way is to spin another port, like zabbix44-js.
It built successfully by poudriere. Problem appeared only if both ports are built on same host.
timeout
A commit references this bug: Author: dbaio Date: Sat Jun 6 16:42:28 UTC 2020 New revision: 538107 URL: https://svnweb.freebsd.org/changeset/ports/538107 Log: net-mgmt/zabbix44-[proxy|server]: Avoid conflicts with bin/zabbix_js Same approach in Zabbix 5. Another way is having another slave port, zabbix44-js just for this file. PR: 245037 Reported by: Aleksandr Ignatyev <alex@i.org.ua> Approved by: maintainer timeout (pg@pakhom.spb.ru, > 2 months) Changes: head/net-mgmt/zabbix44-server/Makefile head/net-mgmt/zabbix44-server/pkg-plist