[Bug 520872] [NEW] dbconfig-common: mysqldump must dump routines during upgrade, or risk data loss
You have been subscribed to a public bug by Robie Basak (racb): 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 ** Affects: dbconfig-common (Ubuntu) Importance: Medium Status: Triaged ** Affects: dbconfig-common (Debian) Importance: Unknown Status: Fix Released ** Tags: apport-bug -- dbconfig-common: mysqldump must dump routines during upgrade, or risk data loss https://bugs.launchpad.net/bugs/520872 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 520872] [NEW] dbconfig-common: mysqldump must dump routines during upgrade, or risk data loss
Public bug reported: 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 ** Affects: dbconfig-common (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- dbconfig-common: mysqldump must dump routines during upgrade, or risk data loss https://bugs.launchpad.net/bugs/520872 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
