On 05 Apr 2007, at 05:05, Jean-François Mertens wrote:
> There are a large number of pkgs still depending on mysql14 (or
> even older ..)
> Whenever any one of those has to be rebuilt (upgraded), mysql(-ssl)
> gets swapped
> out, so to restore the installation, one needs to "rm -fR %p/var/
>
On 04 Apr 2007, at 22:26, Daniel Macks wrote:
> At least in my initial tests, mysql_upgrade fails if mysql is already
> upgraded. That is, running it once upgrades, running it again is an
> error. Maybe:
>
> echo "The following may give an error, which you can ignore..."
> /sw/bin/mysql_upgra
On Thu, Apr 05, 2007 at 04:24:50AM +0900, ASARI Takashi wrote:
> Daniel Macks wrote:
> :
> > Looking at the PostInst, I see it's doing:
> >
> > # create initial database
> > # it is safe to call mysql_install_db even if a db is already present
> > /sw/bin/mysql_install_db --user=mysql
> >
> > Di
Daniel Macks wrote:
:
> Looking at the PostInst, I see it's doing:
>
> # create initial database
> # it is safe to call mysql_install_db even if a db is already present
> /sw/bin/mysql_install_db --user=mysql
>
> Digging into that script, apparently it doesn't realize I already have
> a mysql da
On Apr 3, 2007, at 10:22 PM, Daniel Macks wrote:
> 10.3/unstable, trying to install latest mysql (5.0.38-1) with the
> previous version of that package (5.0.34-6) installed, I got:
>
> Setting up mysql (5.0.38-1) ...
> Installing MySQL system tables...
> 070403 12:42:22 [Warning] Setting lower_cas
10.3/unstable, trying to install latest mysql (5.0.38-1) with the
previous version of that package (5.0.34-6) installed, I got:
Setting up mysql (5.0.38-1) ...
Installing MySQL system tables...
070403 12:42:22 [Warning] Setting lower_case_table_names=2 because file system
for /sw/var/mysql/ is ca
