[MDEV-6200] RPM yum upgrade of MariaDB 5.5 server to 10.0 not possible Created: 2014-05-02  Updated: 2014-05-02  Resolved: 2014-05-02

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

Type: Bug Priority: Minor
Reporter: Arjen Lentz Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: None


 Description   

yum update of MariaDB 10.0 server (from MariaDB 5.5) chucks complaints and also appears to show some bugs/typos in the spec file - sorry I didn't capture the latter bit.

Uninistalling 5.5 then installing 10.0 works perfectly.

But the yum "complaint" is the usual msg of the installed version not being from Monty Program - that is of course incorrect, as MariaDB 5.5 is definitely from Monty Program.



 Comments   
Comment by Arjen Lentz [ 2014-05-02 ]

Ok here's the output from yum (slightly redacted for client confidentiality):

  1. yum localupdate MariaDB-10.0.10-rhel5-x86_64-*.rpm
    Setting up Local Package Process
    Examining MariaDB-10.0.10-rhel5-x86_64-client.rpm: MariaDB-client-10.0.10-1.x86_64
    Marking MariaDB-10.0.10-rhel5-x86_64-client.rpm as an update to MariaDB-client-5.5.36-1.x86_64
    [...]
    Examining MariaDB-10.0.10-rhel5-x86_64-common.rpm: MariaDB-common-10.0.10-1.x86_64
    Marking MariaDB-10.0.10-rhel5-x86_64-common.rpm as an update to MariaDB-common-5.5.36-1.x86_64
    Examining MariaDB-10.0.10-rhel5-x86_64-compat.rpm: MariaDB-compat-10.0.10-1.x86_64
    Marking MariaDB-10.0.10-rhel5-x86_64-compat.rpm as an update to MariaDB-compat-5.5.36-1.x86_64
    Examining MariaDB-10.0.10-rhel5-x86_64-server.rpm: MariaDB-server-10.0.10-1.x86_64
    Marking MariaDB-10.0.10-rhel5-x86_64-server.rpm as an update to MariaDB-server-5.5.36-1.x86_64
    Examining MariaDB-10.0.10-rhel5-x86_64-shared.rpm: MariaDB-shared-10.0.10-1.x86_64
    Marking MariaDB-10.0.10-rhel5-x86_64-shared.rpm as an update to MariaDB-shared-5.5.36-1.x86_64
    Resolving Dependencies
    --> Running transaction check
    ---> Package MariaDB-client.x86_64 0:10.0.10-1 set to be updated
    ---> Package MariaDB-common.x86_64 0:10.0.10-1 set to be updated
    ---> Package MariaDB-compat.x86_64 0:10.0.10-1 set to be updated
    ---> Package MariaDB-server.x86_64 0:10.0.10-1 set to be updated
    ---> Package MariaDB-shared.x86_64 0:10.0.10-1 set to be updated
    --> Finished Dependency Resolution

Transaction Summary
====================================================================================================================================================================================================================
Install 0 Package(s)
Upgrade 5 Package(s)

Total size: 228 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Updating : MariaDB-common 1/10
sed: invalid option – 1
Usage: sed [OPTION]...

{script-only-if-no-other-script}

[input-file]...

-n, --quiet, --silent
suppress automatic printing of pattern space
-e script, --expression=script
add the script to the commands to be executed
-f script-file, --file=script-file
add the contents of script-file to the commands to be executed
-i[SUFFIX], --in-place[=SUFFIX]
edit files in place (makes backup if extension supplied)
-c, --copy
use copy instead of rename when shuffling files in -i mode
(avoids change of input file ownership)
-l N, --line-length=N
specify the desired line-wrap length for the `l' command
--posix
disable all GNU extensions.
-r, --regexp-extended
use extended regular expressions in the script.
-s, --separate
consider files as separate rather than as a single continuous
long stream.
-u, --unbuffered
load minimal amounts of data from the input files and flush
the output buffers more often
--help display this help and exit
--version output version information and exit

******************************************************************
A MySQL or MariaDB server package () is installed.

The current MariaDB server package is provided by a different
vendor (package is not installed) than Monty Program AB. Some files may be installed
to different locations, including log files and the service
startup script in /etc/init.d/.

Upgrading directly from MySQL <unrecognized version package is not installed> to MariaDB 10.0 may not
be safe in all cases. A manual dump and restore using mysqldump is
recommended. It is important to review the MariaDB manual's Upgrading
section for version-specific incompatibilities.

A manual upgrade is required.

  • Ensure that you have a complete, working backup of your data and my.cnf
    files
  • Shut down the MySQL server cleanly
  • Remove the existing MySQL packages. Usually this command will
    list the packages you should remove:
    rpm qa | grep -i '^mysql'

You may choose to use 'rpm --nodeps -ev <package-name>' to remove
the package which contains the mysqlclient shared library. The
library will be reinstalled by the MariaDB-shared package.

  • Install the new MariaDB packages supplied by Monty Program AB
  • Ensure that the MariaDB server is started
  • Run the 'mysql_upgrade' program

This is a brief description of the upgrade process. Important details
can be found in the MariaDB manual, in the Upgrading section.
******************************************************************
Error in PREIN scriptlet in rpm package MariaDB-server-10.0.10-1.x86_64
error: %pre(MariaDB-server-10.0.10-1.x86_64) scriptlet failed, exit status 1
error: install: %pre scriptlet failed (2), skipping MariaDB-server-10.0.10-1
Updating : MariaDB-compat 3/10
Updating : MariaDB-shared 4/10
Updating : MariaDB-client 5/10
Cleanup : MariaDB-common 6/10
Cleanup : MariaDB-client 7/10
Cleanup : MariaDB-compat 8/10
Cleanup : MariaDB-shared 9/10

Updated:
MariaDB-client.x86_64 0:10.0.10-1 MariaDB-common.x86_64 0:10.0.10-1 MariaDB-compat.x86_64 0:10.0.10-1 MariaDB-shared.x86_64 0:10.0.10-1

Failed:
MariaDB-server.x86_64 0:10.0.10-1

Complete!

Comment by Elena Stepanova [ 2014-05-02 ]

It has been fixed in MDEV-5986, the fix should appear in the upcoming 10.0.11 release.

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