** Description changed:
Binary package hint: mysql-client-5.0
Trying to upgrade MySQL 4.1 to 5.0 (just after a dapper -> hardy LTS
upgrade):
Preconfiguring packages ...
(Reading database ... 140431 files and directories currently installed.)
Unpacking mysql-client-5.0 (from
.../mysql-client-5.0_5.0.51a-3ubuntu5_amd64.deb) ...
dpkg: error processing
/var/cache/apt/archives/mysql-client-5.0_5.0.51a-3ubuntu5_amd64.deb (--unpack):
trying to overwrite `/usr/bin/myisam_ftdump', which is also in package
mysql-client-4.1
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Unpacking mysql-server-5.0 (from
.../mysql-server-5.0_5.0.51a-3ubuntu5_amd64.deb) ...
Stopping MySQL database server: mysqld.
dpkg: error processing
/var/cache/apt/archives/mysql-server-5.0_5.0.51a-3ubuntu5_amd64.deb (--unpack):
trying to overwrite `/usr/bin/comp_err', which is also in package
mysql-server-4.1
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/mysql-client-5.0_5.0.51a-3ubuntu5_amd64.deb
/var/cache/apt/archives/mysql-server-5.0_5.0.51a-3ubuntu5_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
+
+ SRU justification: breaks installation of new packages when particular
+ packages from universe are installed from the previous LTS release
+
+ Does not apply to intrepid, for which direct upgrades from dapper are
+ not supported.
+
+ TEST CASE:
+ 1) Install mysql-server-4.1 and mysql-client-4.1 from dapper.
+ 2) upgrade to hardy.
+ 3) install the mysql-client and mysql-server packages.
+ 4) observe that the upgrade fails with file conflicts.
+ 5) enable hardy-proposed.
+ 6) try again to install the mysql-client and mysql-server packages.
+ 7) observe that the upgrade completes successfully, with removal of the old
mysql-{client,server}-4.1 packages.
+
+ Regression potential: minimal, since the only change is to declare
+ conflicts/replaces with packages that already have these file conflicts
+ in practice. However, the impact of this bug is also lower than I
+ originally thought, because it can't be triggered on a dapper->hardy
+ upgrade itself since the mysql-client and mysql-server metapackages are
+ /already/ pointing at 5.0 in dapper, and already have the undeclared
+ file conflicts. Therefore this SRU does not need to be accepted prior
+ to the 8.04.1 point release.
** Changed in: mysql-dfsg-5.0 (Ubuntu Hardy)
Importance: Undecided => Medium
Target: ubuntu-8.04.1 => None
--
Cannot upgrade to mysql-server-5.0
https://bugs.launchpad.net/bugs/208695
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
