* next:
  X redis: v↑  (2.8.23)
  component/postgresql: v↑ postgresql92  (9.2.14)
  component/postgresql: Factor out common build stuff to postgresql-common
  software/postgresql: Don't build postgresql twice

* redis-vup:
  X redis: v↑  (2.8.23)

* pg-vup:
  component/postgresql: v↑ postgresql92  (9.2.14)
  component/postgresql: Factor out common build stuff to postgresql-common
  software/postgresql: Don't build postgresql twice

- update Redis software to latest upstream in 2.8.* series (which now
  supports IPv6 out of the box);

- update Redis instance template to the one from 2.8.23 and re-merge our
  templating changes to it (file/dir locations, port and binding, master
  password).

  The whole diff to pristine 2.8.23 redis conf is now this:

  diff --git a/.../redis-2.8.23/redis.conf b/slapos/recipe/redis/template/redis.conf.in
  index 870959f..2895539 100644
  --- a/.../redis-2.8.23/redis.conf
  +++ b/slapos/recipe/redis/template/redis.conf.in
  @@ -46 +46 @@ daemonize no
  -pidfile /var/run/redis.pid
  +pidfile %(pid_file)s
  @@ -50 +50 @@ pidfile /var/run/redis.pid
  -port 6379
  +port %(port)s
  @@ -69,0 +70 @@ tcp-backlog 511
  +bind %(ipv6)s
  @@ -108 +109 @@ loglevel notice
  -logfile ""
  +logfile %(log_file)s
  @@ -174 +175 @@ rdbcompression yes
  -# hit to pay (around 10%) when saving and loading RDB files, so you can disable it
  +# hit to pay (around 10%%) when saving and loading RDB files, so you can disable it
  @@ -192 +193 @@ dbfilename dump.rdb
  -dir ./
  +dir %(server_dir)s
  @@ -217 +218 @@ dir ./
  -# masterauth <master-password>
  +%(master_passwd)s

XXX tests failure https://github.com/antirez/redis/issues/2715

XXX 2.8 because GitLab uses this series

/cc @alain.takoudjou

* master:
  Advertise development of new version
  use slapos.cookbook 1.0.16 and slapos.core 1.3.14
  Release 1.0.16
  kvm recipe fixup: disk creation and image download
  component/xz: v↑  (5.2.2)

Compared to 9.2.8 postgresql 9.2.14 contains a lot of fixes including
security ones:

    http://www.postgresql.org/docs/current/static/release-9-2-9.html
    http://www.postgresql.org/docs/current/static/release-9-2-10.html
    http://www.postgresql.org/docs/current/static/release-9-2-11.html
    http://www.postgresql.org/docs/current/static/release-9-2-12.html
    http://www.postgresql.org/docs/current/static/release-9-2-13.html
    http://www.postgresql.org/docs/current/static/release-9-2-14.html

Currently we have recipes to build both postgresql 9.1 and 9.2 (see
9f1f0759 "provide both postgres 9.1 and 9.2") which mostly duplicate
each other with minor difference that 9.1 is built with perl and 9.2
without (perl added to 9.1 in dbbd9a96 "Include Perl in Postgres").

To reduce the duplication let's move common compilation bits to common
section.

NOTE I've tried to add perl to postgresql 9.2 as well and got the
following compilation error:

    ld: .../perl/libs-c/libperl.a(op.o): relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a shared object; recompile with -fPIC
    .../parts/perl/libs-c/libperl.a: could not read symbols: Bad value

which happens because libperl.a is not compiled with fPIC.

For now we don't need perl in postgresql92 and this is not handled, and
we just deduplicate building recipes without any actual change for
resulting commands how the software is built.

component/postgresql/buildout.cfg defines both postgresql92 and
postgresql sections, with postgresql being just

    [postgresql]
    <= postgresql92

On the other hand, software/postgresql uses postgresql92 in parts, but
bin = ${postgresql:location}/bin in instance, which leads to _both_
postgresql and postgresql92 being built, and postgresql92 not used at all.

Let's fix it and use postgresql92 everywhere.

/cc @kazuhiko

/reviewed-by @kazuhiko  (on !21)

Commit 6f009a9f broke generation of zope-*.conf

Partition root should be used to control overall permissions, which is
typically a safe-enough 0750 (depending on slapformat and sysadmin).
umask is applied at libc mkdir level, so this typically results in 0755
actual permission.
More restrictive permissions should only be used when really needed.

/reviewed-by @kazuhiko

This is a follow-up of commit 6f009a9f