Since last year, updates to mysql-client-5.5.x kept breaking all dependant
ports, including the server itself. Apparently, the client library could not
be located, thus triggering a re-install of the client, which failed because
the client was already installed. At the same time, the old
For the record: the upgrade wo 5.5.10 went smoothly here, vith
both server and client appearing (on very minimal testing) to work
as before.
Robert Huff
___
freebsd-ports@freebsd.org mailing list
On 03/20/11 06:39, Robert Huff wrote:
For the record: the upgrade wo 5.5.10 went smoothly here, vith
both server and client appearing (on very minimal testing) to work
as before.
Robert Huff
___
On Sun, 20 Mar 2011 07:19:11 -0700
Patrick Powell papow...@astart.com articulated:
On 03/20/11 06:39, Robert Huff wrote:
For the record: the upgrade wo 5.5.10 went smoothly here,
vith both server and client appearing (on very minimal testing) to
work as before.
On 03/20/11 07:33, Jerry wrote:
On Sun, 20 Mar 2011 07:19:11 -0700
Patrick Powellpapow...@astart.com articulated:
On 03/20/11 06:39, Robert Huff wrote:
For the record: the upgrade wo 5.5.10 went smoothly here,
vith both server and client appearing (on very minimal testing) to
work as
- Original Message -
From: Patrick Powell papow...@astart.com
Try running mysql_update and mysql_install_db. The last version of
these died with error messages indicating they could not find
executables. The problem appeared to be that the scripts were
generated with either null
On 03/20/11 13:20, Steven Hartland wrote:
- Original Message - From: Patrick Powell papow...@astart.com
Try running mysql_update and mysql_install_db. The last version of
these died with error messages indicating they could not find
executables. The problem appeared to be that the
- Original Message -
From: Patrick Powell papow...@astart.com
My bad. That was mysql_upgrade. Sorry for the confusion. How about
mysql_install_db?
Can't test that I'm afraid as the machine is now in production. Might want
to make sure the old mysql pkg was removed correctly before
Stefan Bethke ha scritto:
In my particular case, the umask is set to 0002 instead of the default 0022
http://lists.freebsd.org/pipermail/freebsd-ports/2007-September/043529.html
I've updated my portupgrade script to reset the umask to avoid similar problems
Correct way to install ports.
Am 20.03.2011 um 22:43 schrieb Alex Dupre:
Stefan Bethke ha scritto:
In my particular case, the umask is set to 0002 instead of the default 0022
http://lists.freebsd.org/pipermail/freebsd-ports/2007-September/043529.html
I've updated my portupgrade script to reset the umask to avoid
On 03/20/11 14:38, Steven Hartland wrote:
- Original Message - From: Patrick Powell papow...@astart.com
My bad. That was mysql_upgrade. Sorry for the confusion. How about
mysql_install_db?
Can't test that I'm afraid as the machine is now in production. Might
want
to make sure the
11 matches
Mail list logo
