[debian-mysql] Preliminary Percona Server 5.5 packaging

[Stewart Smith]

James Page <james.page at ubuntu.com> writes:
> On 05/12/13 04:39, Stewart Smith wrote:
>> I've been working on Percona Server 5.5 packaging for Debian and 
>> Ubuntu. I have something that's worth sharing with others, mostly
>> for soliciting some help and feedback.
>> 
>> I've had to change things in Percona Server itself so that we build
>> more correct source tarballs (we've been building from BZR trees
>> rather than source tarballs up until this point, which is going to
>> change when my changes are merged).
>
> How do you envisage managing this in the future?  Do you want to still
> release your packaging from the Percona upstream branches? or should
> we do like we did for MariaDB and setup approapriate git repo's on
> Alioth and manage the upstream/packaging split that way.

I think we're going to still want to release from the Percona branches
simply because we'll continue to have our own APT repo too.

That being said, we're probably open to it, we'd just have to figure out
our workflow a bit more for producing our own packages.

> FWIW: I'm a big fan of this as it means any of the team can make
> packaging changes and commit to the correct repository; but I know
> that you have some objectives to make alot of this automated in sync
> with the percona release process so it might not fit so well here.
>
>> I've attempted to keep progress synchronised across Percona Server
>> 5.1, 5.5 and 5.6: 5.1 being optional and 5.5 and 5.6 being the main
>> targets.
>
> Agreed - I'd rather not have 5.1 in Debian as well if possible; 5.5
> and 5.6 is sufficient!  All released versions will need to be
> supported when the current dev release ships so if we can constrain
> version sprawl we might have a chance!

As it is we'll end up with PS 5.5, PS 5.6 and PXC 5.5 and PXC 5.6.

>> I've taken the approach of libperconaserverclient (like
>> libmariadbclient that the maria packages have) so that we don't
>> conflict with the Oracle ones.
>> 
>> If you install libperconaserverclient-dev then you get teh Percona 
>> Server copy of mysql_config, and as such things will build against 
>> libperconaserverclient rather than libmysqlclient.
>
> That sounds OK.
>
>> Due to mysql-common from the Oracle packaging being dragged in for 
>> dependencies, I don't think I can include Percona Server 5.1 unless
>> we change the mysql-common provided /etc/my.cnf to prepend "loose-"
>> to config options that 5.1 servers cannot understand (otherwise
>> the out-of-the-box experience for 5.1 users is a server that fails
>> to start). The value of adding 5.1 is probably rather small
>> though.
>
> Agreed
>
>> For Percona Server 5.5, I've tried to make our packaging
>> relatively close to the MySQL packaging and at least partially
>> succeeded. There's still a few TODOs (labeled as such) and I'm
>> having a few lintian issues.
>
> Here's another one - drop "gcc-4.4 [any-i386], g++-4.4 [any-i386]"
>
> The requirement for this was fixed up in the main mysql package - I
> believe the offending ASM is disabled for the i386 builds.

Excellent, I'll go and have a look at that.

> I've not dug that deep into the packaging yet but will do over the
> next few weeks so expect some further feedback.

thanks! And now I get back to ensuring RPMs can still be built from my
modified source trees and getting my modified source trees merged into
our main repo. Sometimes it feels like it never ends :)

>> PPA: 
>> https://launchpad.net/~stewart/+archive/percona-server-playground
>
> I grabbed your 5.5 package and backported it for 12.04 and 14.04 in:
>
>    ppa:mysql-ubuntu/percona

Awesome, thanks! I've tested with a few Ubuntu releases and it's all
fairly release agnostic (which is rather nice)

-- 
Stewart Smith
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20131220/c577aa4b/attachment.sig>