[Bug 670526] Re: phpmyadmin broken after hardy -> lucid upgrade

[Clint Byrum]

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.

** Changed in: dbconfig-common (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubuntu.
https://bugs.launchpad.net/bugs/670526

Title:
  phpmyadmin broken after hardy -> lucid upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/670526/+subscriptions