Activity log for bug #917246
Date | Who | What changed | Old value | New value | Message |
---|---|---|---|---|---|
2012-01-16 16:34:50 | Alexey Kopytov | bug | added bug | ||
2012-01-16 16:35:09 | Alexey Kopytov | percona-server: assignee | Ignacio Nin (ignacio-nin) | ||
2012-01-16 16:35:16 | Alexey Kopytov | percona-server: milestone | 5.1.61-13.2 | ||
2012-01-16 16:35:20 | Alexey Kopytov | percona-server: status | New | Confirmed | |
2012-01-16 16:44:47 | Alexey Kopytov | description | https://code.launchpad.net/~percona-dev/percona-server/release-5.1.60-13.1/+merge/86334 has introduced a changed 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. | 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. | |
2012-01-16 19:47:12 | Ignacio Nin | percona-server: importance | Undecided | High | |
2012-01-16 21:41:37 | Launchpad Janitor | branch linked | lp:~ignacio-nin/percona-server/5.1.60-bug917246 | ||
2012-01-18 00:07:14 | Ignacio Nin | percona-server: status | Confirmed | Fix Committed | |
2012-01-19 09:40:47 | Alexey Kopytov | branch linked | lp:~akopytov/percona-server/bug917246-5.1 | ||
2012-01-19 09:41:01 | Alexey Kopytov | branch linked | lp:~akopytov/percona-server/bug917246-5.5 | ||
2012-01-19 19:39:57 | Alexey Kopytov | percona-server: status | Fix Committed | Fix Released |