[MDEV-2289] LP:616307 - Failure to upgrade from MySQL to MariaDB on Debian 6.0 "Squeeze" Created: 2010-08-11  Updated: 2015-02-02  Resolved: 2012-10-04

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Kristian Nielsen Assignee: Kristian Nielsen
Resolution: Fixed Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug616307.xml    

 Description   

This is the essense of the problem:

dpkg: error processing /home/buildbot/buildbot/debs/binary/mariadb-server-5.1_5.1.49-mariadb82_i386.deb (--unpack):
trying to overwrite '/usr/share/mysql/german/errmsg.sys', which is also in package mysql-server-core-5.1 5.1.48-1

Debian 6 splits part of the mysql-server-5.1 package into a separate
mysql-server-core-5.1 package, which causes the conflict as the MariaDB
packages do not handle this correctly with conflicts/replaces.

Note that this same problem was already solved for Ubuntu. So the fix is
merely to apply the same fix to the Debian packages (the fix does a similar
split into mariadb-server-core-5.1). As part of the fix, this part of the
change should be consolidated as far as possible so that a single shared file
is used for Ubuntu+Debian, rather than separate
bakery/debian-5.[12]/dist/

{Debian,Ubuntu}

.



 Comments   
Comment by Kristian Nielsen [ 2010-08-11 ]

Re: Failure to upgrade from MySQL to MariaDB 5.2 on Debian 6.0 "Squeeze"
Here is a sample build from Buildbot showing the problem:

http://buildbot.askmonty.org/buildbot/builders/kvm-deb-debian6-x86/builds/0

Comment by Kristian Nielsen [ 2010-11-23 ]

Re: Failure to upgrade from MySQL to MariaDB on Debian 6.0 "Squeeze"
Fix (and thus Squeeze packages) should be available from MariaDB 5.1.52 and 5.2.4.

Comment by Kristian Nielsen [ 2011-02-15 ]

Re: Failure to upgrade from MySQL to MariaDB on Debian 6.0 "Squeeze"
Fixed in MariaDB 5.2.4 and 5.1.53

Comment by Rasmus Johansson (Inactive) [ 2011-02-15 ]

Launchpad bug id: 616307

Generated at Thu Feb 08 06:40:50 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.