[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#903052: marked as done (stretch-pu: package check-postgres/2.22.0-2+deb9u1)

Your message dated Sat, 14 Jul 2018 11:21:20 +0100
with message-id <1531563680.2095.30.camel@adam-barratt.org.uk>
and subject line Closing bugs for updates included in 9.5
has caused the Debian Bug report #903052,
regarding stretch-pu: package check-postgres/2.22.0-2+deb9u1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
903052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903052
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian.org@packages.debian.org
Usertags: pu

Please unblock check-postgres/2.22.0-2+deb9u1. The new version fixes a
FTBFS caused by the last PostgreSQL security update.


diff -Nru check-postgres-2.22.0/debian/changelog check-postgres-2.22.0/debian/changelog
--- check-postgres-2.22.0/debian/changelog	2016-09-22 15:18:36.000000000 +0200
+++ check-postgres-2.22.0/debian/changelog	2018-07-05 14:45:54.000000000 +0200
@@ -1,3 +1,10 @@
+check-postgres (2.22.0-2+deb9u1) stretch; urgency=high
+
+  * PostgreSQL 9.6.8 changes pg_get_indexdef() to always include the schema
+    name. Cope with that in the testsuite.  Closes: #897523.
+
+ -- Christoph Berg <christoph.berg@credativ.de>  Thu, 05 Jul 2018 14:45:54 +0200
+
 check-postgres (2.22.0-2) unstable; urgency=medium
 
   * t/02_disk_space.t: Relax requirements on device name.
diff -Nru check-postgres-2.22.0/debian/patches/798d696ccb8297da233bcc6ab796071c7b35374c check-postgres-2.22.0/debian/patches/798d696ccb8297da233bcc6ab796071c7b35374c
--- check-postgres-2.22.0/debian/patches/798d696ccb8297da233bcc6ab796071c7b35374c	1970-01-01 01:00:00.000000000 +0100
+++ check-postgres-2.22.0/debian/patches/798d696ccb8297da233bcc6ab796071c7b35374c	2018-07-05 14:45:54.000000000 +0200
@@ -0,0 +1,26 @@
+PostgreSQL 9.6.8 changes pg_get_indexdef() to always include the schema name.
+Cope with that in the testsuite.
+
+Closes: #897523
+
+commit 798d696ccb8297da233bcc6ab796071c7b35374c
+Author: David Christensen <david@endpoint.com>
+Date:   Thu Apr 5 11:46:49 2018 -0500
+
+    Allow public-qualified difference (fixes issue with Pg 10)
+
+diff --git a/t/02_same_schema.t b/t/02_same_schema.t
+index e5517d1..218712e 100644
+--- a/t/02_same_schema.t
++++ b/t/02_same_schema.t
+@@ -621,8 +621,8 @@ like ($cp1->run($connect2),
+       qr{^$label CRITICAL.*Items not matched: 1 .*
+ \s*Index "public.valen":
+ \s*"indexdef" is different:
+-\s*Database 1: CREATE INDEX valen ON gkar USING btree \(garibaldi\)
+-\s*Database 2: CREATE UNIQUE INDEX valen ON gkar USING btree \(garibaldi\)
++\s*Database 1: CREATE INDEX valen ON (?:public\.)?gkar USING btree \(garibaldi\)
++\s*Database 2: CREATE UNIQUE INDEX valen ON (?:public\.)?gkar USING btree \(garibaldi\)
+ \s*"indisunique" is different:
+ \s*Database 1: f
+ \s*Database 2: t\s*$}s,
diff -Nru check-postgres-2.22.0/debian/patches/series check-postgres-2.22.0/debian/patches/series
--- check-postgres-2.22.0/debian/patches/series	2016-09-22 15:18:31.000000000 +0200
+++ check-postgres-2.22.0/debian/patches/series	2018-07-05 14:45:54.000000000 +0200
@@ -1,3 +1,4 @@
 no-tests-on-clean
 disable_replicate_row
 disk_space
+798d696ccb8297da233bcc6ab796071c7b35374c

Christoph

--- End Message ---
--- Begin Message --- 
Version: 9.5

Hi,

The update referenced by each of these bugs was included in this
morning's stretch point release.

Regards,

Adam

--- End Message ---
Reply to: