mysql-3.23.51 was installed during "emerge xfree kde" then, later on, emerge --update world suggested to update the db package; after that, mysql crashed at startup immediately after /etc/init.d/mysql was issued. I had to unmerge and re-merge mysql again to fix the problem.
Which mysql? 3.23.51, 3.23.51-r1, or 3.23.51-r2 ?
with mysql-3.23.51. Btw: i checked it out two minutes ago, and aftr an emerge --clean rsync and emerge --pretend --update world, portage still say i'm fine with mysql-3.23.51: no need for update to -r1 or -r2 .. is this okay?
Hmm. -r2 is what you *should* be using. Can you verify that -r1 and -r2 are, indeed, available in the dev-db/mysql directory?
i checked the changelog and yes, i should use -r2. both -r1 and -r2 ebuilds exists in /usr/portage/dev-db/mysql/ btw, running emerge --pretend --update world will *not* list mysql in the list of packages in need of upgrade. i'm using portage-2.0.11
juddleg a bit with emerge unmerge portage and portage-2.0.10-x86.tbz2 rescue, it now says mysql need upgrade to -r2; i'm upgrading right now. btw, reading the changelog of mysql i noticed my original bug announcement (db library related) should had been fixed by -r2.... maybe this bug can be closed. thank you.
Since no futher action has been taken by this bug, and the bug appears to have been resolved by portage fixes, I am closing this bug.
