Mysql Systemd won't start woes

After a Gentoo reinstall on my laptop (Thinkpad T420), I configured my system to use Systemd and KDE with UEFI (no secure boot obviously).
It now boots in less than 7 seconds (!) but I do encounter the occasional issue. There is something to be said for the simplicity and stability of openrc.

One issue I've encountered isn't related to systemd insomuch as mysql isn't properly configured when I install it. Please note, it's not just mysql that is affected, but mariadb as well.


Problem is this:

/var/run/mysqld did not exist and it needs to be set to mysql:mysql ownership. Once I did those two things, systemd could start mysqld.

If those do not work, try the following:

cd /usr/
/usr/share/mysql/scripts/mysql_install_db
mkdir /var/run/mysqld
chown -R mysql:mysql /var/run/mysqld
systemd start mysqld
/usr/bin/mysql_secure_installation

On that last step, I had no root password so pressing Enter at the prompt passed that question.

I hope this helps.

KDE upgrade on Gentoo: 4.11 to 4.12.3

Recently I have noticed that while many of my kde packages are Upgradable (Blue highlighted "U" in emerge's output), they were not getting upgraded.
After browsing some forums and attempting to explicitly install a kde 4.12.3 package and having it failed, it appears I may have found the solution.

It may seem like a simple solution, but I am using layman to manage all my kde packages so I assumed that when I ran layman -S or layman -f, it would have updated my kde keyword to reflect the latest packages.

This was not the case, so I created this file in the path: /etc/portage/package.accept_keywords/kde-4.12.3 and inside it, placed all the packages the output listed that had dependencies. Since it was a bit of effort to find, copy and paste into the file, I'm listing it here for those interested.

=kde-base/kcmshell-4.12.3 ~amd64
=kde-base/kiconfinder-4.12.3 ~amd64
=kde-base/kwrite-4.12.3 ~amd64
=kde-base/oxygen-icons-4.12.3 ~amd64
=kde-base/khelpcenter-4.12.3 ~amd64
=kde-base/kdnssd-4.12.3 ~amd64
=kde-base/knetattach-4.12.3 ~amd64
=kde-base/kdontchangethehostname-4.12.3 ~amd64
=kde-base/kstart-4.12.3 ~amd64
=kde-base/keditfiletype-4.12.3 ~amd64
=kde-base/kmimetypefinder-4.12.3 ~amd64
=kde-base/kurifilter-plugins-4.12.3 ~amd64
=kde-base/kdepasswd-4.12.3 ~amd64
=kde-base/ktraderclient-4.12.3 ~amd64
=kde-base/kdebase-menu-4.12.3 ~amd64
=kde-base/kdesu-4.12.3 ~amd64
=kde-base/dolphin-4.12.3 ~amd64
=app-office/akonadi-server-1.11.0 ~amd64
=kde-base/nsplugins-4.12.3 ~amd64
=kde-base/kde-base-artwork-4.12.3 ~amd64
=kde-base/kuiserver-4.12.3 ~amd64
=kde-base/svgpart-4.12.3 ~amd64
=kde-base/konsole-4.12.3 ~amd64
=kde-base/kdebase-runtime-meta-4.12.3 ~amd64
=kde-base/kdebase-desktoptheme-4.12.3 ~amd64
=kde-base/katepart-4.12.3-r1 ~amd64
=kde-base/nepomuk-widgets-4.12.3 ~amd64
=kde-base/kquitapp-4.12.3 ~amd64
=kde-base/keditbookmarks-4.12.3 ~amd64
=kde-base/drkonqi-4.12.3 ~amd64
=kde-base/kglobalaccel-4.12.3 ~amd64
=kde-base/kfind-4.12.3 ~amd64
=kde-base/kdebugdialog-4.12.3 ~amd64
=kde-base/kde-env-4.12.3 ~amd64
=kde-base/kfile-4.12.3 ~amd64
=kde-base/ktimezoned-4.12.3 ~amd64
=kde-base/solid-runtime-4.12.3 ~amd64
=kde-base/kwalletd-4.12.3 ~amd64
=kde-base/kdebase-menu-icons-4.12.3 ~amd64
=kde-base/nepomuk-4.12.3 ~amd64
=kde-base/kactivities-4.12.3 ~amd64
=kde-base/kdebase-meta-4.12.3 ~amd64
=kde-base/konq-plugins-4.12.3 ~amd64
=kde-base/kdebase-kioslaves-4.12.3 ~amd64
=kde-base/attica-4.12.3 ~amd64
=kde-base/kdelibs-4.12.3 ~amd64
=kde-base/plasma-runtime-4.12.3 ~amd64
=kde-base/kcontrol-4.12.3 ~amd64
=kde-base/kpasswdserver-4.12.3 ~amd64
=kde-base/kdepimlibs-4.12.3 ~amd64
=kde-base/phonon-kde-4.12.3 ~amd64
=kde-base/kwalletmanager-4.12.3 ~amd64
=kde-base/kfmclient-4.12.3 ~amd64
=kde-base/konqueror-4.12.3 ~amd64
=kde-base/kimgio-4.12.3 ~amd64
=kde-base/nepomuk-core-4.12.3 ~amd64
=kde-base/plasma-apps-4.12.3 ~amd64
=kde-base/kdebase-data-4.12.3 ~amd64
=kde-base/kdialog-4.12.3 ~amd64
=kde-base/renamedlg-plugins-4.12.3 ~amd64
=kde-base/knewstuff-4.12.3 ~amd64
=kde-base/libkonq-4.12.3 ~amd64
=kde-base/kioclient-4.12.3 ~amd64

Now you must know that this will require updating when new packages are released, so this isn't a proper solution. However, since the maintainers at Gentoo and KDE are working on plasma2 and KDE Frameworks 5, it is likely that there will be a proper upgrade path and all that will be required is the deletion of this file and a simple upgrade world.

I don't guarantee anything will work, these are just my thoughts and solutions.

Cheers.

Quickly changing python version in gentoo from 2.x to 3.x series

On my gentoo laptop I am upgrading my python from version 2.7 to 3.2 to aid in some development at my job.

Since it's been set up with 2.7, I cannot utilize some important libraries such as python-sqlite because they are not built for the 3.2 target.

Without going into the more complex explanation on why it works, these are the steps to configure your system to utilize python 3.x.

/etc/portage/make.conf:

USE_PYTHON="3.2 3.3 2.7"
PYTHON_TARGETS="python3_2 python3_3"
PYTHON_SINGLE_TARGET="python3_2"

Simple Explanation:

USE_PYTHON tells emerge the list of desired python versions.

PYTHON_TARGETS tells emerge what targets you prefer to build for. Only if a package cannot build for these targets, yet has a version in USE_PYTHON, will it build in a different version -- I *think*.

PYTHON_SINGLE_TARGET tells emerge that if a package can be built for only one target, use that target. My install of Blender requires the single target point to python3_3.

Be sure to set the python version with eselect.

eselect python set [number]

Next step is to update things by calling python-update, no parameters.
Once your eselect python show --ABI shows the 3.x version you specify in PYTHON_SINGLE_TARGET, you can start rebuilding your system.

This process may take a while. All packages that cannot be built in the 3 series must have the python version specified in /etc/portage/package.use. An example of how to do this is so:

echo "[group]/[package] python_targets_python2_[x] python_single_target_python2_[x]" >> /etc/portage/package.use

Do this until you can get through emerge --deep --update --newuse world -av without dependency issues.

Once you complete the emerge, run revdep-rebuild to make sure your packages are in order.