After some hours of trying, I managed to get to an very nasty work-around for people not needing mysql, but needing apt-get to work. In my apt-get, it hung over the error as the first package, and just wouldn't continue. I couldn't find a way to disable it, but removed mysql with:
sudo apt-get upgrade hung at some packages of postgresql with a similar error, so I used the same way to remove those. errors with a package called "man-db" dissapeared (and it installed properly).
I have to say tough, that I didn't check if the mysql files were removed completely, this could cause security issues, minor disk space issues, and huge issues when re-installing the packages, but it got my apt-get working again and that's all I'm concerned about. If you're an experienced ubuntu user owning a test server, I ask you to test the severity of the risks of this (temporarily) solution, since I don't have the knowledge to do this, and my server is a part-hobby part production server.
After some hours of trying, I managed to get to an very nasty work-around for people not needing mysql, but needing apt-get to work. In my apt-get, it hung over the error as the first package, and just wouldn't continue. I couldn't find a way to disable it, but removed mysql with:
sudo dpkg --force- remove- reinstreq --remove mysql-server-5.1
sudo apt-get upgrade hung at some packages of postgresql with a similar error, so I used the same way to remove those. errors with a package called "man-db" dissapeared (and it installed properly).
I have to say tough, that I didn't check if the mysql files were removed completely, this could cause security issues, minor disk space issues, and huge issues when re-installing the packages, but it got my apt-get working again and that's all I'm concerned about. If you're an experienced ubuntu user owning a test server, I ask you to test the severity of the risks of this (temporarily) solution, since I don't have the knowledge to do this, and my server is a part-hobby part production server.