Your message dated Sun, 06 Dec 2020 22:32:08 +0000 with message-id <e1km2zc-000dmr...@fasolo.debian.org> and subject line Bug#974063: fixed in postgresql-11 11.10-0+deb10u1 has caused the Debian Bug report #974063, regarding postgresql-13: FTBFS: timetz test failure 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 ow...@bugs.debian.org immediately.) -- 974063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: postgresql-13 Version: 13.0-6 Severity: serious Justification: ftbfs Tags: ftbfs User: debian-p...@lists.debian.org Usertags: perl-5.32-transition Control: block 968912 with -1 Similar to postgresql-12 (#974061) postgresql-13 FTBFS on multiple archs, eg: https://buildd.debian.org/status/fetch.php?pkg=postgresql-13&arch=amd64&ver=13.0-6%2Bb1&stamp=1604915618&raw=0 Unfortunately, postgresql-13 wasn't in sid at the point we did our last full rebuild test. plperl does seem to be implicated in the error output: 2020-11-09 09:53:28.680 UTC client backend[31345] pg_regress/event_trigger ERROR: object audit_tbls.schema_two_table_three of type table cannot be dropped 2020-11-09 09:53:28.680 UTC client backend[31345] pg_regress/event_trigger CONTEXT: PL/pgSQL function undroppable() line 14 at RAISE SQL statement "DROP TABLE IF EXISTS audit_tbls.schema_two_table_three" PL/pgSQL function test_evtrig_dropped_objects() line 8 at EXECUTE 2020-11-09 09:53:28.680 UTC client backend[31345] pg_regress/event_trigger STATEMENT: DROP SCHEMA schema_one, schema_two CASCADE; 2020-11-09 09:53:28.818 UTC client backend[31345] pg_regress/event_trigger ERROR: object schema_one.table_three of type table cannot be dropped 2020-11-09 09:53:28.818 UTC client backend[31345] pg_regress/event_trigger CONTEXT: PL/pgSQL function undroppable() line 14 at RAISE 2020-11-09 09:53:28.818 UTC client backend[31345] pg_regress/event_trigger STATEMENT: DROP SCHEMA schema_one, schema_two CASCADE; 2020-11-09 09:53:28.985 UTC client backend[31345] pg_regress/event_trigger ERROR: pg_event_trigger_table_rewrite_oid() can only be called in a table_rewrite event trigger function 2020-11-09 09:53:28.985 UTC client backend[31345] pg_regress/event_trigger STATEMENT: select pg_event_trigger_table_rewrite_oid(); 2020-11-09 09:53:28.998 UTC client backend[31345] pg_regress/event_trigger ERROR: rewrites not allowed 2020-11-09 09:53:28.998 UTC client backend[31345] pg_regress/event_trigger CONTEXT: PL/pgSQL function test_evtrig_no_rewrite() line 3 at RAISE 2020-11-09 09:53:28.998 UTC client backend[31345] pg_regress/event_trigger STATEMENT: alter table rewriteme alter column foo type numeric; 2020-11-09 09:53:29.024 UTC client backend[31345] pg_regress/event_trigger ERROR: cannot alter type "rewritetype" because column "rewritemetoo3.a" uses it 2020-11-09 09:53:29.024 UTC client backend[31345] pg_regress/event_trigger STATEMENT: alter type rewritetype alter attribute a type varchar cascade; 2020-11-09 09:53:30.668 UTC client backend[31354] pg_regress/stats LOG: wait_for_stats delayed 0.543818 seconds 2020-11-09 09:53:30.668 UTC client backend[31354] pg_regress/stats CONTEXT: PL/pgSQL function wait_for_stats() line 48 at RAISE 2020-11-09 09:53:30.668 UTC client backend[31354] pg_regress/stats STATEMENT: SELECT wait_for_stats(); 2020-11-09 09:53:30.836 UTC postmaster[29982] LOG: received fast shutdown request 2020-11-09 09:53:30.836 UTC postmaster[29982] LOG: aborting any active transactions 2020-11-09 09:53:30.839 UTC postmaster[29982] LOG: background worker "logical replication launcher" (PID 29991) exited with exit code 1 2020-11-09 09:53:30.840 UTC checkpointer[29986] LOG: shutting down 2020-11-09 09:53:30.840 UTC checkpointer[29986] LOG: checkpoint starting: shutdown immediate 2020-11-09 09:53:31.100 UTC checkpointer[29986] LOG: checkpoint complete: wrote 10551 buffers (64.4%); 0 WAL file(s) added, 0 removed, 13 recycled; write=0.227 s, sync=0.000 s, total=0.259 s; sync files=0, longest=0.000 s, average=0.000 s; distance=220237 kB, estimate=220237 kB 2020-11-09 09:53:31.131 UTC postmaster[29982] LOG: database system is shut down Please could you take a look? Cheers Dominic
--- End Message ---
--- Begin Message ---Source: postgresql-11 Source-Version: 11.10-0+deb10u1 Done: Christoph Berg <m...@debian.org> We believe that the bug you reported is fixed in the latest version of postgresql-11, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 974...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg <m...@debian.org> (supplier of updated postgresql-11 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Tue, 01 Dec 2020 10:04:12 +0100 Source: postgresql-11 Architecture: source Version: 11.10-0+deb10u1 Distribution: buster Urgency: medium Maintainer: Debian PostgreSQL Maintainers <team+postgre...@tracker.debian.org> Changed-By: Christoph Berg <m...@debian.org> Closes: 974063 Changes: postgresql-11 (11.10-0+deb10u1) buster; urgency=medium . * New upstream version. + Fixes timetz regression test failures. (Closes: #974063) . + Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries (Noah Misch) . This is essentially a leak in the security restricted operation sandbox mechanism. An attacker having permission to create non-temporary SQL objects could parlay this leak to execute arbitrary SQL code as a superuser. . The PostgreSQL Project thanks Etienne Stalmans for reporting this problem. (CVE-2020-25695) . + Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb (Tom Lane) . The -d parameter of pg_dump and pg_restore, or the --maintenance-db parameter of the other programs mentioned, can be a connection string containing multiple connection parameters rather than just a database name. In cases where these programs need to initiate additional connections, such as parallel processing or processing of multiple databases, the connection string was forgotten and just the basic connection parameters (database name, host, port, and username) were used for the additional connections. This could lead to connection failures if the connection string included any other essential information, such as non-default SSL or GSS parameters. Worse, the connection might succeed but not be encrypted as intended, or be vulnerable to man-in-the-middle attacks that the intended connection parameters would have prevented. (CVE-2020-25694) . + When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used (Tom Lane) . This avoids cases where reconnection might fail due to omission of relevant parameters, such as non-default SSL or GSS options. Worse, the reconnection might succeed but not be encrypted as intended, or be vulnerable to man-in-the-middle attacks that the intended connection parameters would have prevented. This is largely the same problem as just cited for pg_dump et al, although psql's behavior is more complex since the user may intentionally override some connection parameters. (CVE-2020-25694) . + Prevent psql's \gset command from modifying specially-treated variables (Noah Misch) . \gset without a prefix would overwrite whatever variables the server told it to. Thus, a compromised server could set specially-treated variables such as PROMPT1, giving the ability to execute arbitrary shell code in the user's session. . The PostgreSQL Project thanks Nick Cleaton for reporting this problem. (CVE-2020-25696) Checksums-Sha1: 215fab141ba76bc290e2d3a78aee7d8943d6d10f 3745 postgresql-11_11.10-0+deb10u1.dsc 97bc8d07d30229b52bac57241cd48bcf6116ef44 20003842 postgresql-11_11.10.orig.tar.bz2 110e25c15a16fcc966ab3c3a3bedd15b3485b636 26252 postgresql-11_11.10-0+deb10u1.debian.tar.xz Checksums-Sha256: 088a20ee67d5f296ad2d608e35f9aaa685cf4afe6be348b0d4bdca3089c7fbdf 3745 postgresql-11_11.10-0+deb10u1.dsc 13e6d2f80662fe463bc7718cdf0de6a9ec67fc78afcc7a3ae66b9ea19bb97899 20003842 postgresql-11_11.10.orig.tar.bz2 638afc81e8ed4baac1814051ddd087d7e93612a5d5c2891dbdfb5ce67d04f611 26252 postgresql-11_11.10-0+deb10u1.debian.tar.xz Files: 8912adbe88b91e026137f0a0eebd7f91 3745 database optional postgresql-11_11.10-0+deb10u1.dsc c9dbf5ae42a08b937d1b6cf7921e4669 20003842 database optional postgresql-11_11.10.orig.tar.bz2 9cd116660ae21070bfcd2da04239ca24 26252 database optional postgresql-11_11.10-0+deb10u1.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl/GIeEACgkQTFprqxLS p64xuRAAtVKeQSLdINLmdrsumqOTft+AOFit6Np5jGMcGpi2uLTBxeLRjEMv8d6q JVLJNr3hRC+HhyYBANzCkpX4hDklrQAYsHXM/j/QKkEoYS53RRF4KtDpSheo0fSf +SJmmtiGluw5r2FfT0YcIxO+olp7wEnnZkUsylVhN7LSwsWmAQfYSbbEwzOyBsfT 6m5x84auO4neWRIghjQ7rl86sWtB+T1T36HGxRGbV7BxOvhG22bmO1AUZNMs4k4V xeum9WrOMwG0jhTH1sUoDkfZ2ItJQrEh5O12pl6oMeEGKem0fFd3+RilnAaGbn3v fjHlOhIMa3hC5f0vDyjQTcyDPtxqBOi/oywLu5EhdX8v9c3/a+iIIQAnxu6FApdP CvbtryGmWVgFgDsOQ8+S4NORm/BUroNNSNT2RUFP+/4VLA5IBBG/wInoEBmPBth0 kettOQFUENfyI6ne0ZKXs3qWPJo0bdLmP0wlT/CBNtrvznjWWzXF7uoTCHpxmbuR mt1lmktRCPabhs6sEA7wCCGng3XmoA3K43+tu9ixIPS9yBB1WbNk4SzsjJPdAh82 jHJOr0RduWUDh+G7DJ1ObS7P1hnH186SlgPPJNEamzUuFBVmeu5l/WCj9ibWUanE Ew9SoRxUCS4cfWDZeVAIBoMl8nAFjrQJXW6iGEUhdHVGA8lwJn0= =YXya -----END PGP SIGNATURE-----
--- End Message ---
