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
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.
--
You received this bug notification because you are a
** Changed in: mariadb-10.0 (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1392539
Title:
package mariadb-server-5.5 5.5.39-0ubuntu0.14.04.1 failed to
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: (unassigned) = Otto Kekäläinen (otto)
** Changed in: mariadb-5.5
** Changed in: mariadb-10.0 (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1392539
Title:
package mariadb-server-5.5 5.5.39-0ubuntu0.14.04.1 failed to
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
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1392539
Title:
package mariadb-server-5.5 5.5.39-0ubuntu0.14.04.1 failed to
install/upgrade: subprocess new
