[Bug 231993] security/barnyard2-sguil: depends on MySQL 5.6 despite DEFAULT_VERSIONS+=mysql=5.7
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Oct 6 07:49:29 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231993
Bug ID: 231993
Summary: security/barnyard2-sguil: depends on MySQL 5.6 despite
DEFAULT_VERSIONS+=mysql=5.7
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: bofh at freebsd.org
Reporter: Trond.Endrestol at ximalas.info
Flags: maintainer-feedback?(bofh at freebsd.org)
Assignee: bofh at freebsd.org
My builder couldn't rebuild barnyard2-sguil-1.13_1 this morning.
--------------------------------------------------------------------------------
-- Phase: lib-depends
--------------------------------------------------------------------------------
===> barnyard2-sguil-1.13_1 depends on shared library: libtcl86.so - not
found
===> Installing existing package /packages/All/tcl86-8.6.8.txz
Installing tcl86-8.6.8...
Extracting tcl86-8.6.8: .......... done
===> barnyard2-sguil-1.13_1 depends on shared library: libtcl86.so - found
(/usr/local/lib/libtcl86.so)
===> Returning to build of barnyard2-sguil-1.13_1
===> barnyard2-sguil-1.13_1 depends on shared library: libmysqlclient.so.18 -
not found
===> barnyard2-sguil-1.13_1 depends on package:
/packages/All/mysql56-client-5.6.41.txz - not found
===> USE_PACKAGE_DEPENDS_ONLY set - not building missing dependency from
source
*** Error code 1
Stop.
make: stopped in /xports/security/barnyard2-sguil
--------------------------------------------------
-- Termination
--------------------------------------------------
Finished: Saturday, 6 OCT 2018 at 07:24:43 UTC
Duration: 00:00:12
Despite having DEFAULT_VERSIONS+=mysql=5.7 in
/usr/local/etc/synth/LiveSystem-make.conf (and /etc/make.conf),
security/barnyard2-sguil falls back to MySQL 5.6. Is there another way of
(en)forcing MySQL 5.7?
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list