Unintentional change of innodb_version format in 5.1.60
Bug #917246 reported by
Alexey Kopytov
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
High
|
Ignacio Nin | ||
Bug Description
https:/
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
- Alexey Kopytov (community): Approve
-
Diff: 71 lines (+12/-6)3 files modifiedbuild/build-binary.sh (+4/-2)
build/build-dpkg.sh (+4/-2)
build/build-rpm.sh (+4/-2)
lp:~akopytov/percona-server/bug917246-5.1
- Oleg Tsarev (community): Approve
-
Diff: 20 lines (+11/-0)2 files modifiedPercona-Server/mysql-test/r/percona_innodb_version.result (+3/-0)
Percona-Server/mysql-test/t/percona_innodb_version.test (+8/-0)
lp:~akopytov/percona-server/bug917246-5.5
- Oleg Tsarev (community): Approve
-
Diff: 30 lines (+18/-0)2 files modifiedpatches/bug917246.patch (+17/-0)
patches/series (+1/-0)
| 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 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/