Bernard Spil wrote on 2017/04/19 21:32:
On 2017-04-18 21:45, Miroslav Lachman wrote:
Miroslav Lachman wrote on 2017/03/31 15:31:
I don't know if it was "pkg" fault or mariadb101-server and
I did standard "pkg upgrade" and at the end I have half files of
# pkg check -Ba
Checking all packages: ...
pkg: fstat() failed for(/usr/local/bin/msql2mysql): No such file or
[82/86] Upgrading mariadb101-server from 10.1.21 to 10.1.22...
===> Creating groups.
Using existing group 'mysql'.
===> Creating users
Using existing user 'mysql'.
[82/86] Extracting mariadb101-server-10.1.22: .......... done
This was on FreeBSD 10.3 amd64 with packages from own poudriere with
OPTIONS_UNSET= X11 GUI CUPS DOCS EXAMPLES NLS HAL
DEFAULT_VERSIONS=apache=2.4 perl5=5.24 mysql=10.1m php=5.6 python=2.7
python3=3.5 pgsql=9.4 ssl=openssl
I think all users of MariaDB 10.1 should be warned in UPDATING
Let me know if you need some more details.
Am I the only one beaten by this issue? I see this on each of our
machines during pkg upgrade.
Looks like it. My own servers were upgraded with mariadb from pkg
Sorry for your inconvenience, don't know what would cause that.
The root cause is IMHO this change in pkg-plist
but I don't understand why nobody else see this problem on pkg upgrade.
We are using poudriere with standard ports tree, MariaDB is build with
standard options etc.
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"