phpmyadmin broken after hardy -> lucid upgrade

[Mark - Syminet]

Binary package hint: phpmyadmin

Lucid: 4:3.3.2-1

After upgrade hardy -> lucid phpmyadmin complains that controluser is invalid and logins fail.

These commands fixed it:

dpkg --purge phpmyadmin

apt-get install phpmyadmin

However more bugs/errors/warnings after being able to login... will post those next.

This has happened three times in a row on three different servers.

[Michal Čihař (nijel)]

Looks to me like if dbconfig-common forgot the generated credentials.

[Mark - Syminet (mark-syminet)]

OK thanks, the fix I posted worked easily enough over here. I might mention that I was using a /root/.my.cnf for auto-login to mysql. When being asked questions by dbconfig I leave the passwd blank and usually that seems to work just fine. So if you aren't hearing this from others, then maybe I chmodded the file or something while working and didn't realize.

[Clint Byrum (clint-fewbar)]

Mark, first off thanks for opening this bug report back in 2010. I am able to reproduce this, however I don't think it is a bug.

I started by configuring phpmyadmin to point at my mysql server in a hardy chroot, including a 'controluser'. I then upgraded the chroot to lucid. When accepting the dist config to replace my /etc/phpmyadmin/config.inc.php, things did not work, but switching to the old one produced a mostly working phpmyadmin that just warned me about a few broken things. Moving the dist config back into place and reconfiguring with dpkg-reconfigure phpmyadmin also did not break things. Using the old config (from hardy) with dpkg-reconfigure definitely broke things as you describe.

I feel that this is the wrong approach to support, as during an upgrade, the user should incorporate the new changes into the config file, merging the old values into the new config. The change is so radical from hardy to lucid, that its very easy to get wrong, but this is just part of the reality of config file management unfortunately.

I think this is purely a case where the old version configs and new version configs were just too incompatible. There haven't been any more reports of this, so I think this issue is not something we can handle in Ubuntu, nor is it something we can forward upstream. I'm closing it as Invalid, but if you think it might still be a bug worth looking at please do feel free to re-open it or open a new bug report.

[Mark - Syminet (mark-syminet)]

OK - thanks!