Hello community, here is the log from the commit of package postgresql96 for openSUSE:Leap:15.2 checked in at 2020-03-13 10:55:10 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Leap:15.2/postgresql96 (Old) and /work/SRC/openSUSE:Leap:15.2/.postgresql96.new.3160 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "postgresql96" Fri Mar 13 10:55:10 2020 rev:32 rq:784387 version:9.6.17 Changes: -------- --- /work/SRC/openSUSE:Leap:15.2/postgresql96/postgresql96.changes 2020-01-15 15:44:45.843300199 +0100 +++ /work/SRC/openSUSE:Leap:15.2/.postgresql96.new.3160/postgresql96.changes 2020-03-13 10:55:12.684342113 +0100 @@ -1,0 +2,132 @@ +Sat Feb 15 03:23:25 UTC 2020 - Marcus Rueckert <[email protected]> + +- update to 9.6.17 (CVE-2020-1720) + https://www.postgresql.org/about/news/2011/ + https://www.postgresql.org/docs/9.6/release-9-6-17.html + +------------------------------------------------------------------- +Sun Dec 29 17:11:56 UTC 2019 - Lars Vogdt <[email protected]> + +- use and package the sha256 checksum for for source + +------------------------------------------------------------------- +Fri Dec 20 15:02:14 UTC 2019 - Marcus Rueckert <[email protected]> + +- update to 9.6.16: + https://www.postgresql.org/about/news/1994/ + https://www.postgresql.org/docs/9.6/release-9-6-16.html + +------------------------------------------------------------------- +Tue Oct 22 17:02:45 UTC 2019 - Marcus Rueckert <[email protected]> + +- add requires to the devel package for the libs that are returned + by pg_config --libs + +------------------------------------------------------------------- +Mon Aug 12 14:42:26 UTC 2019 - Reinhard Max <[email protected]> + +- Update to 9.6.15: + * https://www.postgresql.org/about/news/1960/ + * https://www.postgresql.org/docs/9.6/release-9-6-15.html + * CVE-2019-10208, bsc#1145092: TYPE in pg_temp executes arbitrary + SQL during SECURITY DEFINER execution. + +------------------------------------------------------------------- +Fri Aug 2 08:54:34 UTC 2019 - Martin Liška <[email protected]> + +- Use FAT LTO objects in order to provide proper static library. + +------------------------------------------------------------------- +Fri Jun 21 14:37:09 UTC 2019 - Marcus Rueckert <[email protected]> + +- Update to 9.6.14: + https://www.postgresql.org/docs/9.6/release-9-6-14.html + +------------------------------------------------------------------- +Fri May 10 14:14:11 UTC 2019 - Reinhard Max <[email protected]> + +- Update to 9.6.13: + * https://www.postgresql.org/docs/9.6/release-9-6-13.html + * https://www.postgresql.org/about/news/1939/ + * CVE-2019-10130, bsc#1134689: Prevent row-level security + policies from being bypassed via selectivity estimators. + +------------------------------------------------------------------- +Tue Mar 5 10:36:31 UTC 2019 - Reinhard Max <[email protected]> + +- Make the server-devel package exclusive across versions. + +------------------------------------------------------------------- +Mon Feb 25 13:30:52 UTC 2019 - Reinhard Max <[email protected]> + +- Update to 9.6.12: + * https://www.postgresql.org/docs/9.6/release-9-6-12.html + * https://www.postgresql.org/about/news/1920/ + * By default, panic instead of retrying after fsync() failure, + to avoid possible data corruption. + * Numerous other bug fixes. +- Overhaul README.SUSE + +------------------------------------------------------------------- +Fri Nov 9 09:12:43 UTC 2018 - Reinhard Max <[email protected]> + +- Update to 9.6.11: + * Numerous bug fixes, see the release notes: + https://www.postgresql.org/docs/9.6/release-9-6-11.html + * Remove unneeded library dependencies from PGXS. + +------------------------------------------------------------------- +Wed Oct 17 16:23:19 UTC 2018 - Marcus Rueckert <[email protected]> + +- add provides for the new server-devel package that will be + introduced in postgresql 11 + +------------------------------------------------------------------- +Fri Aug 10 16:07:48 UTC 2018 - [email protected] + +- Update to 9.6.10: + https://www.postgresql.org/docs/current/static/release-9-6-10.html + + * CVE-2018-10915, bsc#1104199: Fix failure to reset libpq's state + fully between connection attempts. + + * CVE-2018-10925, bsc#1104202: Fix INSERT ... ON CONFLICT UPDATE + through a view that isn't just SELECT * FROM ... + +------------------------------------------------------------------- +Wed May 16 09:21:53 UTC 2018 - [email protected] + +- Update to 9.6.9: + https://www.postgresql.org/about/news/1851/ + https://www.postgresql.org/docs/current/static/release-9-6-9.html + + A dump/restore is not required for those running 9.6.X. + + However, if you use the adminpack extension, you should update + it as per the first changelog entry below. + + Also, if the function marking mistakes mentioned in the second + and third changelog entries below affect you, you will want to + take steps to correct your database catalogs. + + * CVE-2018-1115, bsc#1091610: Remove public execute privilege + from contrib/adminpack's pg_logfile_rotate() function + + pg_logfile_rotate() is a deprecated wrapper for the core + function pg_rotate_logfile(). When that function was changed + to rely on SQL privileges for access control rather than a + hard-coded superuser check, pg_logfile_rotate() should have + been updated as well, but the need for this was missed. Hence, + if adminpack is installed, any user could request a logfile + rotation, creating a minor security issue. + + After installing this update, administrators should update + adminpack by performing ALTER EXTENSION adminpack UPDATE in + each database in which adminpack is installed. + + * Fix incorrect volatility markings on a few built-in functions + + * Fix incorrect parallel-safety markings on a few built-in + functions. + +------------------------------------------------------------------- Old: ---- postgresql-9.6.8.tar.bz2 New: ---- postgresql-9.6.17.tar.bz2 postgresql-9.6.17.tar.bz2.sha256 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ postgresql96.spec ++++++ --- /var/tmp/diff_new_pack.vnGUMN/_old 2020-03-13 10:55:13.304342555 +0100 +++ /var/tmp/diff_new_pack.vnGUMN/_new 2020-03-13 10:55:13.308342558 +0100 @@ -1,7 +1,7 @@ # # spec file for package postgresql96 # -# Copyright (c) 2018 SUSE LINUX GmbH, Nuernberg, Germany. +# Copyright (c) 2020 SUSE LLC # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed @@ -12,7 +12,7 @@ # license that conforms to the Open Source Definition (Version 1.9) # published by the Open Source Initiative. -# Please submit bugfixes or comments via http://bugs.opensuse.org/ +# Please submit bugfixes or comments via https://bugs.opensuse.org/ # @@ -80,10 +80,11 @@ Summary: Basic Clients and Utilities for PostgreSQL License: PostgreSQL Group: Productivity/Databases/Tools -Version: 9.6.8 +Version: 9.6.17 Release: 0 Source0: https://ftp.postgresql.org/pub/source/v%{version}/postgresql-%{version}.tar.bz2 -Source1: baselibs.conf +Source1: https://ftp.postgresql.org/pub/source/v%{version}/postgresql-%{version}.tar.bz2.sha256 +Source2: baselibs.conf Source3: postgresql-README.SUSE Source17: postgresql-rpmlintrc Patch1: postgresql-conf.patch @@ -93,7 +94,7 @@ Patch6: postgresql-testsuite-int8.sql.patch Patch8: postgresql-testsuite-keep-results-file.patch Patch9: postgresql-var-run-socket.patch -Url: https://www.postgresql.org/ +URL: https://www.postgresql.org/ BuildRoot: %{_tmppath}/%{name}-%{version}-build Provides: postgresql = %version-%release Provides: postgresql-implementation = %version-%release @@ -158,7 +159,10 @@ %package devel Summary: PostgreSQL development header files and libraries Group: Development/Libraries/C and C++ +Provides: postgresql%packageversion-server-devel = %version-%release Provides: postgresql-devel-implementation = %version-%release +Provides: postgresql-server-devel = %version-%release +Provides: postgresql-server-devel-implementation = %version-%release Requires: %libecpg >= %majorversion Requires: %libpq >= %majorversion Requires(post): postgresql-noarch >= %majorversion @@ -166,6 +170,16 @@ # Installation of postgresql??-devel is exclusive Provides: postgresql-devel-exclusive = %majorversion Conflicts: postgresql-devel-exclusive < %majorversion +Provides: postgresql-server-devel-exclusive = %pgmajor +Conflicts: postgresql-server-devel-exclusive < %pgmajor +# all libs returned from pg_config --libs +Requires: openssl-devel +Requires: zlib-devel +%if 0%{?suse_version} == 1110 +Requires: krb5-devel +%else +Requires: pkgconfig(krb5) +%endif %description devel PostgreSQL is an advanced object-relational database management system @@ -335,6 +349,7 @@ find -name .gitignore -delete %build +%global _lto_cflags %{_lto_cflags} -ffat-lto-objects PACKAGE_TARNAME=%name %configure \ --bindir=%pgbindir \ --libdir=%pglibdir \ @@ -477,6 +492,8 @@ ln -sf $f.? $f done popd +# Remove mostly unneeded buildtime requirements for server extensions +sed -i '/^LIBS = /s/= .*/=/' %buildroot/%pglibdir/pgxs/src/Makefile.global %if %buildlibs %find_lang libpq5-%{pg_minor_version} libpq.lang %find_lang ecpglib6-%{pg_minor_version} libecpg.lang @@ -529,6 +546,7 @@ for pl in plperl plpython pltcl; do %find_lang $pl-%{pg_minor_version} $pl.lang done + %endif ln -s /etc/alternatives/postgresql %buildroot/usr/lib/postgresql touch %buildroot/etc/alternatives/postgresql ++++++ postgresql-9.6.8.tar.bz2 -> postgresql-9.6.17.tar.bz2 ++++++ /work/SRC/openSUSE:Leap:15.2/postgresql96/postgresql-9.6.8.tar.bz2 /work/SRC/openSUSE:Leap:15.2/.postgresql96.new.3160/postgresql-9.6.17.tar.bz2 differ: char 11, line 1 ++++++ postgresql-9.6.17.tar.bz2.sha256 ++++++ f6e1e32d32545f97c066f3c19f4d58dfab1205c01252cf85c5c92294ace1a0c2 postgresql-9.6.17.tar.bz2 ++++++ postgresql-README.SUSE ++++++ --- /var/tmp/diff_new_pack.vnGUMN/_old 2020-03-13 10:55:13.404342627 +0100 +++ /var/tmp/diff_new_pack.vnGUMN/_new 2020-03-13 10:55:13.404342627 +0100 @@ -1,22 +1,41 @@ -Newer versions of PostgreSQL come with the pg_upgrade tool that +Unix-Domain Socket Directory +============================ + + + +Upgrading PostgreSQL on openSUSE and SUSE Linux Enterprise Server +================================================================= + +Current versions of PostgreSQL come with the pg_upgrade tool that simplifies and speeds up the migration of a PostgreSQL installation to -a new version. Formerly dump and restore was needed that was much -slower. +a new version. Before version 9.1 dump and restore was needed which +was much slower. pg_upgrade needs to have the server binaries of both versions available. To allow this, we had to change the way PostgreSQL is packaged as well as the naming of the packages, so that two or more -versions of PostgreSQL can be installed in parallel. +versions of PostgreSQL can be installed in parallel. The package +names for PostgreSQL contain numbers indicating the major version. + +In PostgreSQL terms for versions up to 9.6 the major version consisted +of the first two components of the three-component version number, +i.e. 8.3, 8.4, 9.0, or 9.1. So, the packages for Postgresql 9.1 are +named postgresql91, postgresql91-server, etc. Inside the packages the +files were moved from their standard locations to a versioned location +such as /usr/lib/postgresql83/bin or /usr/lib/postgresql91/bin to +avoid file conflicts if packages are installed in parallel. + +Starting with version 10 the PostgreSQL project changed their +versioning scheme from from three components to two, which means one +component for the major version and one for the minor. So, the +sequence of major version across the versioning scheme change will be: +9.4, 9.5, 9.6, 10, 11, 12. For versions that use the new versioning +scheme SUSE only puts the single component major version into the +package name, so the postgresql96 package (containg version 9.6 +according to the old versioning scheme) will be followed by +postgresql10, then postgresql11, and so on. -Starting with version 9.1, PostgreSQL package names contain numbers -indicating the major version. In PostgreSQL terms the major version -consists of the first two components of the version number, i.e. 8.3, -8.4, 9.0, or 9.1. So, the packages for Postgresql 9.1 are named -postgresql91, postgresql91-server, etc. Inside the packages the files -were moved from their standard locations to a versioned location such -as /usr/lib/postgresql83/bin or /usr/lib/postgresql91/bin to avoid -file conflicts if packages are installed in parallel. The -update-alternatives mechanism creates and maintains symbolic links +The update-alternatives mechanism creates and maintains symbolic links that cause one version (by default the highest installed version) to re-appear in the standard locations. By default, database data are stored under /var/lib/pgsql/data on SUSE Linux. @@ -26,14 +45,12 @@ 1. If not already done, the packages of the old PostgreSQL version must be upgraded to the new packaging scheme through a maintenance - update. For SLE11 this means to install the patch that upgrades - PostgreSQL from version 8.3.14 to 8.3.19 or higher. + update. 2. The packages of the new PostgreSQL major version need to be - installed. For SLE11 this means to install postgresql91-server and - all the packages it depends on. As pg_upgrade is contained in - postgresql91-contrib, that one has to be installed as well, at least - until the migration is done. + installed. As pg_upgrade is contained in postgresql91-contrib, that + one has to be installed as well, at least until the migration is + done. 3. Unless pg_upgrade is used in link mode, the server must have enough free disk space to temporarily hold a copy of the database @@ -44,17 +61,20 @@ database in the instance to be migrated, but be aware that it might take very long. -Upstream documentation about pg_upgrade including step by step -instructions for performing a database migration can be found under -file:///usr/share/doc/packages/postgresql91/html/pgupgrade.html (if -the postgresql91-docs package is installed), or online under -http://www.postgresql.org/docs/9.1/static/pgupgrade.html . +The latest upstream documentation for pg_upgrade including step by +step instructions for performing a database migration can be found +online under https://www.postgresql.org/docs/current/pgupgrade.html , +or locally under +file:///usr/share/doc/packages/postgresqlXX/html/pgupgrade.html , if +the postgresqlXX-docs package is installed. XX is a place holder for +the respective major version here. NOTE: The online documentation starts with explaining how you can install PostgreSQL from the upstream sources (which is not necessary -on SLES) and also uses other directory names (/usr/local instead of -the update-alternatives based path as described above). - -For background information about the inner workings of pg_admin and a -performance comparison with the old dump and restore method, see -http://momjian.us/main/writings/pgsql/pg_upgrade.pdf . \ No newline at end of file +when you install the SUSE RPMs) and also uses other directory names +(/usr/local instead of the update-alternatives based path as described +above). + +For background information about the inner workings of pg_upgrade and +a performance comparison with the old dump and restore method, see +http://momjian.us/main/writings/pgsql/pg_upgrade.pdf . ++++++ postgresql-var-run-socket.patch ++++++ --- /var/tmp/diff_new_pack.vnGUMN/_old 2020-03-13 10:55:13.440342652 +0100 +++ /var/tmp/diff_new_pack.vnGUMN/_new 2020-03-13 10:55:13.440342652 +0100 @@ -15,7 +15,7 @@ --- src/bin/pg_upgrade/test.sh.orig +++ src/bin/pg_upgrade/test.sh -@@ -148,6 +148,12 @@ done +@@ -159,6 +159,12 @@ done EXTRA_REGRESS_OPTS="$EXTRA_REGRESS_OPTS --port=$PGPORT" export EXTRA_REGRESS_OPTS @@ -25,12 +25,12 @@ + +POSTMASTER_OPTS="$POSTMASTER_OPTS -c unix_socket_directories='$PGHOST'" + - # enable echo so the user can see what is being executed - set -x + standard_initdb "$oldbindir"/initdb + "$oldbindir"/pg_ctl start -l "$logdir/postmaster1.log" -o "$POSTMASTER_OPTS" -w --- src/backend/utils/misc/guc.c.orig +++ src/backend/utils/misc/guc.c -@@ -3351,7 +3351,7 @@ static struct config_string ConfigureNam +@@ -3360,7 +3360,7 @@ static struct config_string ConfigureNam }, &Unix_socket_directories, #ifdef HAVE_UNIX_SOCKETS @@ -41,7 +41,7 @@ #endif --- src/bin/initdb/initdb.c.orig +++ src/bin/initdb/initdb.c -@@ -1221,7 +1221,7 @@ setup_config(void) +@@ -1229,7 +1229,7 @@ setup_config(void) #ifdef HAVE_UNIX_SOCKETS snprintf(repltok, sizeof(repltok), "#unix_socket_directories = '%s'",
