[MDEV-346] 5.5 upgrade test fails on precise Created: 2012-06-16  Updated: 2012-06-18  Due: 2012-06-19  Resolved: 2012-06-18

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

Type: Bug Priority: Major
Reporter: Sergei Golubchik Assignee: Kristian Nielsen
Resolution: Fixed Votes: 0
Labels: None


 Description   

upgrade test fails on precise (both x86 and amd64) as

+ sudo sh -c 'DEBIAN_FRONTEND=noninteractive MYSQLD_STARTUP_TIMEOUT=180 apt-get install --allow-unauthenticated -y mariadb-server'
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
 
The following packages have unmet dependencies:
 mariadb-server : Depends: mariadb-server-5.5 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.



 Comments   
Comment by Kristian Nielsen [ 2012-06-16 ]

I think it is just because the standard MySQL package has a higher version number than the mariadb packages.
So it will be fixed when we do the next release an increase the version number.

Comment by Sergei Golubchik [ 2012-06-16 ]

buildbot tries to upgrade to mariadb-5.5.25.
on precise-amd64-update image we have mysql-5.5.22 installed.

It doesn't look like a higher version number to me

Comment by Kristian Nielsen [ 2012-06-16 ]

Yes, what I meant is - I think a higher version is available in the upstream repos.
After Oracle stopped releasing security vulnerability information, Ubuntu had to switch to
not backpatching, but grabbing latest upstream release. So they would have 5.5.25 to get the
recent security hole fixed.

Comment by Sergei Golubchik [ 2012-06-17 ]

upstream repo has 5.5.24 (I've tried apt-get upgrade in this VM). Still less than 5.5.25.

Comment by Kristian Nielsen [ 2012-06-18 ]

It looked like we were missing some replaces: and conflicts: headers for mysql-server-5.5
and mysql-client-5.5.

I added them and pushed to 5.5-serg, we will see if it makes a difference.

Comment by Sergei Golubchik [ 2012-06-18 ]

pushed

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