Incorrect version shown in version string
Bug #1190308 reported by
Ignacio Nin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona Server moved to https://jira.percona.com/projects/PS |
Invalid
|
Undecided
|
Unassigned | ||
| 5.1 |
Won't Fix
|
Medium
|
Ignacio Nin | ||
| 5.5 |
Invalid
|
Undecided
|
Unassigned | ||
| 5.6 |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
The version string for 5.1.69-14.7 shows 5.1.70-rel14.7.
This comes from configure.in, which for that release contains [5.1.70] as configure parameter.
Related branches
lp:~percona-core/percona-server/release-5.1.69-14.7
- Laurynas Biveinis (community): Approve
-
Diff: 41 lines (+4/-4)3 files modifiedbuild/debian/rules (+1/-1)
build/percona-server.spec (+2/-2)
build/percona-shared-compat.spec (+1/-1)
| Changed in percona-server: | |
| importance: | Undecided → High |
Revision history for this message
| Laurynas Biveinis (laurynas-biveinis) wrote | #1 |
Revision history for this message
| Laurynas Biveinis (laurynas-biveinis) wrote | #2 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #3 |
To post a comment you must log in.
The issue here is that mysql-5.1.69 tag is placed *after* the mysql-5.1.69 actual release contents. There is another tag, mysql-5.1.69-tag, at an earlier revision, which, presumably corresponds to the actual release.
Since bumping the version number down would not be truthful neither nor IMHO it is actually critical, I'd say we just release the actual 5.1.70 and be done with this.