Make XtraDB honor version information from the VERSION file
Bug #1333212 reported by
Alexey Kopytov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.1 |
Won't Fix
|
Medium
|
Unassigned | |||
5.5 |
Triaged
|
Medium
|
Unassigned | |||
5.6 |
Triaged
|
Medium
|
Unassigned | |||
5.7 |
Triaged
|
Medium
|
Unassigned |
Bug Description
This is what I see in 5.5:
VERSION contains:
MYSQL_VERSION_
MYSQL_VERSION_
MYSQL_VERSION_
MYSQL_VERSION_
but in univ.i:
#ifndef PERCONA_
#define PERCONA_
#endif
Likewise in 5.6, VERSION:
MYSQL_VERSION_
MYSQL_VERSION_
MYSQL_VERSION_
MYSQL_VERSION_
but in univ.i:
#ifndef PERCONA_
#define PERCONA_
#endif
tags: | added: pkg |
summary: |
- PERCONA_INNODB_VERSION is outdated (again) + Remove PERCONA_INNODB_VERSION from univ.i |
summary: |
- Remove PERCONA_INNODB_VERSION from univ.i + Make XtraDB honor version information from the VERSION file |
To post a comment you must log in.
Hi Alexey, INNODB_ VERSION 35.1
we are updating version in univ.i and also checking version in VERSION file on the release branch for every release.
for 5.5 in the trunk (file univ.i) I see:
#define PERCONA_
which seems fine
and for 5.6 I see in the trunk in univ.i file> INNODB_ VERSION 66.0
#define PERCONA_
which was ok for the last release.
There can be bigger version in VERSION file but that's because Laurynas merged upstream and bumped the version - we will change in the univ.i file also on the release branch for the next release.
Is that ok?