Unintentional change of innodb_version format in 5.1.60

Bug #917246 reported by Alexey Kopytov on 2012-01-16
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Percona Server
High
Ignacio Nin

Bug Description

https://code.launchpad.net/~percona-dev/percona-server/release-5.1.60-13.1/+merge/86334 has introduced a change in the innodb_version format. Previously, it was reported as "1.0.x-x.x". In 5.1.60 it is reported as "1.0.17-rel13.1".

That has broken XtraBackup automatic version detection, see XtraBackup bug #910206. I'm going to add a workaround to XtraBackup, but it would be good to have a consistent format for innodb_version.

Related branches

lp:~ignacio-nin/percona-server/5.1.60-bug917246
Merged into lp:percona-server/5.1 at revision 417
Alexey Kopytov: Approve on 2012-01-19
lp:~akopytov/percona-server/bug917246-5.1
Merged into lp:percona-server/5.1 at revision 418
Oleg Tsarev (community): Approve on 2012-01-20
lp:~akopytov/percona-server/bug917246-5.5
Merged into lp:percona-server/5.5 at revision 212
Oleg Tsarev (community): Approve on 2012-01-20
Changed in percona-server:
assignee: nobody → Ignacio Nin (ignacio-nin)
milestone: none → 5.1.61-13.2
status: New → Confirmed
description: updated
Changed in percona-server:
importance: Undecided → High
Changed in percona-server:
status: Confirmed → Fix Committed
Changed in percona-server:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers