From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/postgresql: bump to version 11.2
Date: Mon, 18 Feb 2019 21:08:18 +0100 [thread overview]
Message-ID: <20190218210818.1e93e0ca@gmx.net> (raw)
In-Reply-To: <20190217171908.30080-1-peter@korsgaard.com>
Hello Peter,
On Sun, 17 Feb 2019 18:19:07 +0100, Peter Korsgaard <peter@korsgaard.com> wrote:
> Fixes a long standing fsync issue and a number of other bugs:
> https://www.postgresql.org/docs/11/release-11-2.html
>
> https://wiki.postgresql.org/wiki/Fsync_Errors
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> package/postgresql/postgresql.hash | 10 +++++-----
> package/postgresql/postgresql.mk | 2 +-
> 2 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/package/postgresql/postgresql.hash b/package/postgresql/postgresql.hash
> index 28d4a988d2..c4d7ab55bb 100644
> --- a/package/postgresql/postgresql.hash
> +++ b/package/postgresql/postgresql.hash
> @@ -1,7 +1,7 @@
> -# From https://ftp.postgresql.org/pub/source/v11.1/postgresql-11.1.tar.bz2.md5
> -md5 5e45f6d5b859cc76b5d62f1e328e9711 postgresql-11.1.tar.bz2
> -# From https://ftp.postgresql.org/pub/source/v11.1/postgresql-11.1.tar.bz2.sha256
> -sha256 90815e812874831e9a4bf6e1136bf73bc2c5a0464ef142e2dfea40cda206db08 postgresql-11.1.tar.bz2
> +# From https://ftp.postgresql.org/pub/source/v11.2/postgresql-11.2.tar.bz2.md5
> +md5 19d43be679cb0d55363feb8926af3a0f postgresql-11.2.tar.bz2
> +# From https://ftp.postgresql.org/pub/source/v11.2/postgresql-11.2.tar.bz2.sha256
> +sha256 2676b9ce09c21978032070b6794696e0aa5a476e3d21d60afc036dc0a9c09405 postgresql-11.2.tar.bz2
>
> # License file, Locally calculated
> -sha256 24cfc70cf16b3a23242c49ffce39510683bdd48cbedb8a46fe03976ee5f5c21e COPYRIGHT
> +sha256 c4c86d683970b22b9fab53320ee1b3a30ef4e8223122b4fb6be53ea62ecee8b3 COPYRIGHT
$ diff -u build/postgresql-11.1/COPYRIGHT build/postgresql-11.2/COPYRIGHT
--- build/postgresql-11.1/COPYRIGHT 2018-11-07 00:56:26.000000000 +0100
+++ build/postgresql-11.2/COPYRIGHT 2019-02-11 22:17:27.000000000 +0100
@@ -1,7 +1,7 @@
PostgreSQL Database Management System
(formerly known as Postgres, then as Postgres95)
-Portions Copyright (c) 1996-2018, PostgreSQL Global Development Group
+Portions Copyright (c) 1996-2019, PostgreSQL Global Development Group
Portions Copyright (c) 1994, The Regents of the University of California
Only update of the copyright year (worth mentioning in the commit log?)...
Reviewed-by: Peter Seiderer <ps.report@gmx.net>
Regards,
Peter
> diff --git a/package/postgresql/postgresql.mk b/package/postgresql/postgresql.mk
> index fefbcf5f06..c7e9f526fc 100644
> --- a/package/postgresql/postgresql.mk
> +++ b/package/postgresql/postgresql.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -POSTGRESQL_VERSION = 11.1
> +POSTGRESQL_VERSION = 11.2
> POSTGRESQL_SOURCE = postgresql-$(POSTGRESQL_VERSION).tar.bz2
> POSTGRESQL_SITE = http://ftp.postgresql.org/pub/source/v$(POSTGRESQL_VERSION)
> POSTGRESQL_LICENSE = PostgreSQL
next prev parent reply other threads:[~2019-02-18 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 17:19 [Buildroot] [PATCH] package/postgresql: bump to version 11.2 Peter Korsgaard
2019-02-18 20:08 ` Peter Seiderer [this message]
2019-02-18 21:33 ` Peter Korsgaard
2019-02-18 22:12 ` Thomas Petazzoni
2019-02-22 12:05 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190218210818.1e93e0ca@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox