maria-discuss team mailing list archive

[Arjen Lentz <arjen@xxxxxxxxxxxxx>]

Daniel, isn't this "simply" a RPM SPEC bug that needs to be reported in the launchpad bug system and dealt with, rather than just documented as a knowledge base item?


----- Original Message -----
> From: "Daniel Bartholomew" <dbart@xxxxxxxxxxxxxxxx>
> To: "Maria Discuss" <maria-discuss@xxxxxxxxxxxxxxxxxxx>
> Sent: Friday, 30 September, 2011 2:25:12 AM
> Subject: [Maria-discuss] New KB Question: MariaDB 5.2.x server RPM fails on upgrades - error: scriptlet failed, exit
> status 1
> A new question has been posted to the Knowledgebase:
> 
> MariaDB 5.2.x server RPM fails on upgrades - error: scriptlet failed,
> exit status 1
> 
> http://kb.askmonty.org/en/mariadb-52x-server-rpm-fails-on-upgrades-error-scriptlet-failed-exit-status
> 
> ---------------------------------------------------------------------
> 
> This problem occurs on CentOS 5.5/5.6/6.0 32bit and 64bit from first
> time I used MariaDB 5.2.3 all the way to 5.2.9 upgrade. It happens
> 
> 1) via manual RPM upgrade from RPM downloaded at
> http://downloads.askmonty.org/mariadb/5.2/#file_type=rpm
> 
> or
> 
> 2) via ourdelta YUM REPO update http://ourdelta.org/centos (yum update
> MariaDB*).
> 
> Problem, MariaDB-server-5.2.x RPM updates fails and needs manually
> removing previous version MariaDB-server-5.2.x RPM before the new
> update installs.
> 
> error
> 
> error: %pre(MariaDB-server-5.2.9-102.el5.x86_64) scriptlet failed,
> exit
> status 1
> error: install: %pre scriptlet failed (2), skipping
> MariaDB-server-5.2.9-102.el5
> 
> full details below ... (continued in the KB)
> ---------------------------------------------------------------------
> 
> Thanks.
> 
> --
> Daniel Bartholomew
> MariaDB - http://mariadb.org
> Monty Program - http://montyprogram.com
> AskMonty Knowledgebase - http://kb.askmonty.org


-- 
Arjen Lentz, Exec.Director @ Open Query (http://openquery.com)
Remote expertise & maintenance for MySQL/MariaDB server environments.

Follow us at http://openquery.com/blog/ & http://twitter.com/openquery