package mariadb-server-5.5 5.5.39-0ubuntu0.14.04.1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

Bug #1392539 reported by Doug
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mariadb-10.0 (Debian)
Fix Released
Unknown
mariadb-5.5 (Ubuntu)
Fix Released
Undecided
Otto Kekäläinen

Bug Description

I did not elect to migrate from MYSQL.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: mariadb-server-5.5 5.5.39-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
Date: Thu Nov 13 19:23:22 2014
DuplicateSignature: package:mariadb-server-5.5:5.5.39-0ubuntu0.14.04.1:subprocess new pre-installation script returned error exit status 1
ErrorMessage: subprocess new pre-installation script returned error exit status 1
InstallationDate: Installed on 2014-10-09 (35 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: mariadb-5.5
Title: package mariadb-server-5.5 5.5.39-0ubuntu0.14.04.1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Doug (deaton658) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Otto Kekäläinen (otto) wrote :

Hello!

This kind of by design how the mysql and mariadb packages work. If there is an issue with the /var/lib/mysql/*.flag file or data migration, the dpkg process simply stops and an unwanted upgrade is not performed.

Unfortunately the exit code is not handled very well and Apport thinks this is a bug, which it is actually not.

Revision history for this message
Otto Kekäläinen (otto) wrote :

I got a proper bug report in upstream Debian and was able to pinpoint the issue. A fix is possible to produce now.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770177

Changed in mariadb-5.5 (Ubuntu):
assignee: nobody → Otto Kekäläinen (otto)
status: New → Confirmed
Changed in mariadb-10.0 (Debian):
status: Unknown → New
Changed in mariadb-10.0 (Debian):
status: New → Fix Released
Revision history for this message
Otto Kekäläinen (otto) wrote :

For the record: this was fixed in http://anonscm.debian.org/cgit/pkg-mysql/mariadb-5.5.git/commit/?id=19cda85f117d914626ad77d3027327b7803dfa98 and will flow back to Ubuntu 14.04 and 14.10 wehn 5.5.40 enters via the stable updates channel.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mariadb-5.5 - 5.5.41-0ubuntu0.14.10.2

---------------
mariadb-5.5 (5.5.41-0ubuntu0.14.10.2) utopic-security; urgency=medium

  * SECURITY UPDATE: Update to 5.5.41 to fix security issues (LP: #1414755)
    - CVE-2015-0411
    - CVE-2015-0382
    - CVE-2015-0381
    - CVE-2015-0432
    - CVE-2014-6568
    - CVE-2015-0374
  * As approved by Seth Arnold, this security update also imports the latest
    mariadb-5.5 packaging from Debian which includes useful and low-risk
    fixes:
    - Updated Dutch translation by Frans Spiesschaert
    - Updated control file so that mariadb-client-5.5 breaks and replaces
      the package mariadb-server-5.5 to allow overwriting the innochecksum
      man page file which has changed location (LP: #1368124) as per
      doc https://www.debian.org/doc/debian-policy/ch-relationships.html#s7.6.1
    - Backported the fix of #770177 from 10.0 to 5.5 so that the migration
      question will not be asked repeatedly. (LP: #1392539)
  * Backported new cacert.pem etc from 5.5 the replace the expired ones
 -- Otto Kekaelaeinen <email address hidden> Mon, 26 Jan 2015 21:15:00 +0200

Changed in mariadb-5.5 (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.