dbconfig-common: mysqldump must dump routines during upgrade, or risk data loss

Bug #520872 reported by pdf
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dbconfig-common (Debian)
Fix Released
Unknown
dbconfig-common (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: dbconfig-common

If an upgrade script alters or deletes a routine (FUNCTION/PROCEDURE) during upgrade, and the current or subsequent upgrade fails, the user is unable to recover routines using the created database backups, so the affected routine(s) may be permanently lost/damaged, and the upgrade permanently wedged.

This is severe, and the way to recover is for the user to have intricate knowledge of the package, and be able to extract the affected procedure from previous install/update scripts if available.

This should obviously be reported upstream, but I'm not sure what the protocol is for reporting to Debian from derivative distributions.

Attached patch resolves by enabling 'routines' option for mysqldump.

ProblemType: Bug
Architecture: amd64
Date: Fri Feb 12 20:34:49 2010
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: dbconfig-common 1.8.41
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_AU.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: dbconfig-common
Uname: Linux 2.6.31-19-generic x86_64

Tags: apport-bug
Revision history for this message
pdf (pdffs) wrote :
Revision history for this message
Chuck Short (zulcss) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570098

Changed in dbconfig-common (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Changed in dbconfig-common (Debian):
status: Unknown → New
Changed in dbconfig-common (Debian):
status: New → Fix Released
Revision history for this message
pdf (pdffs) wrote :

Can we please get 1.8.48 released in Ubuntu?

Revision history for this message
Robie Basak (racb) wrote :

dbconfig-common >= 1.8.48 is still in experimental in Debian. I don't want to sync it to Ubuntu without knowing why this is the case. When Debian upload it to unstable, Ubuntu should autosync it soon after unless we're in freeze by then.

Revision history for this message
Paul Gevers (paul-climbing) wrote : Re: [Bug 520872] Re: dbconfig-common: mysqldump must dump routines during upgrade, or risk data loss

Upload of 1.8.51 will happen in about two weeks time. That gives
translators the time to update the templates.

It will be synced automatically to Ubuntu after that.

Paul

On 20-05-15 10:07, Robie Basak wrote:
> dbconfig-common >= 1.8.48 is still in experimental in Debian. I don't
> want to sync it to Ubuntu without knowing why this is the case. When
> Debian upload it to unstable, Ubuntu should autosync it soon after
> unless we're in freeze by then.
>

Revision history for this message
Robie Basak (racb) wrote :

Thank you for the update, Paul.

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

This bug was fixed in the package dbconfig-common - 1.8.52

---------------
dbconfig-common (1.8.52) unstable; urgency=medium

  * Forgot to install dbconfig-common for the CI tests
  * Update French translation by Julien Patriarca (Closes: #789908)

 -- Paul Gevers <email address hidden> Fri, 26 Jun 2015 13:42:50 +0200

Changed in dbconfig-common (Ubuntu):
status: Triaged → 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.