Merge lp:~ignacio-nin/percona-server/5.1-bug1002500 into lp:percona-server/5.1

Proposed by Ignacio Nin
Status: Merged
Approved by: Alexey Kopytov
Approved revision: no longer in the source branch.
Merged at revision: 592
Proposed branch: lp:~ignacio-nin/percona-server/5.1-bug1002500
Merge into: lp:percona-server/5.1
Diff against target: 28 lines (+9/-1)
2 files modified
build/debian/changelog (+8/-0)
build/debian/rules (+1/-1)
To merge this branch: bzr merge lp:~ignacio-nin/percona-server/5.1-bug1002500
Reviewer Review Type Date Requested Status
Ignacio Nin (community) Needs Resubmitting
Alexey Kopytov (community) Approve
Laurynas Biveinis (community) Needs Information
Stewart Smith Pending
Review via email: mp+176509@code.launchpad.net

Description of the change

Fix for bug #1002500

To post a comment you must log in.
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

Does Stewart's 5.6 review comment apply on the lower branches too?

review: Needs Information
Revision history for this message
Ignacio Nin (ignacio-nin) wrote :

It does. Resubmitting with change.

review: Needs Resubmitting
Revision history for this message
Alexey Kopytov (akopytov) wrote :

Since PS 5.1.70-rel14.8 has already been released, the version in the changelog needs to be updated.

review: Needs Fixing
Revision history for this message
Ignacio Nin (ignacio-nin) wrote :

> Since PS 5.1.70-rel14.8 has already been released, the version in the
> changelog needs to be updated.

I'm struggling thinking what would be a sensitive version number? According to http://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog, that's the version of the upstream package, and the changelog details what differences we do make in respect to the upstream package. We obviously haven't got an equivalent of an upstream package, but the version of the package to which this change was applied to was 5.1.70-14.8, because we patch the 5.1 version at its lowest common denominator with 5.5.

Patching it with the latest release (5.1.71-14.9) wouldn't make too much sense as well, and patching it with the number of the next release is impossible in much of the cases since we don't know the next release number (in most cases).

Revision history for this message
Alexey Kopytov (akopytov) wrote :

I don't understand how we could apply this change to 5.1.70-14.8 if this patch has not been merged yet? Was this MP merged to its release branch? If so, I agree, 5.1.70-rel14.8 is the right version and this MP can be considered approved.

review: Approve
Revision history for this message
Ignacio Nin (ignacio-nin) wrote :

Resubmitting with the debian changelog updated to the milestone targeted by the bug.

review: Needs Resubmitting

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'build/debian/changelog'
2--- build/debian/changelog 2012-01-04 18:48:32 +0000
3+++ build/debian/changelog 2013-09-25 16:33:21 +0000
4@@ -1,3 +1,11 @@
5+percona-server-5.1 (5.1.72-rel14.10) unstable; urgency=low
6+
7+ * Added --error-handler=: to dh_installinit in order to
8+ avoid an error when the server wouldn't start for any
9+ reasons other than bad installation.
10+
11+ -- Ignacio Nin <ignacio.nin@percona.com> Wed, 24 Jul 2013 11:20:00 -0300
12+
13 percona-server-5.1 (5.1.60-rel13.1) unstable; urgency=low
14
15 * Changed name to percona-server-5.1.
16
17=== modified file 'build/debian/rules'
18--- build/debian/rules 2013-08-27 15:05:45 +0000
19+++ build/debian/rules 2013-09-25 16:33:21 +0000
20@@ -302,7 +302,7 @@
21 dh_installlogrotate -a --name percona-server-server
22 # Start mysql in runlevel 19 before 20 where apache, proftpd etc gets
23 # started which might depend on a running database server.
24- dh_installinit -a --name=mysql -- defaults 19 21
25+ dh_installinit -a --name=mysql --error-handler=: -- defaults 19 21
26 dh_installcron -a --name percona-server-server
27 dh_installman -a
28 dh_installinfo -a

Subscribers

People subscribed via source and target branches