[Pkg-postgresql-public] Processed (with 1 error): asciidoc: deprecate in debian - blocked by bugs
Processing commands for cont...@bugs.debian.org: > block 895462 by 884213 893467 895186 895187 894192 894194 894188 894697 894700 Bug #895462 [asciidoc] asciidoc: deprecate in Debian 895462 was not blocked by any bugs. 895462 was not blocking any bugs. Added blocking bug(s) of 895462: 893467, 894697, 895187, 895186, 894194, 884213, 894700, 894188, and 894192 > 894710 895165 895166 895167 895168 Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 895462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895462 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#892116: marked as done ([PATCH] Please set Built-Using field)
Your message dated Tue, 10 Apr 2018 19:57:03 +
with message-id <e1f5zo3-000f6d...@fasolo.debian.org>
and subject line Bug#892116: fixed in prometheus-sql-exporter 0.2.0.ds-4
has caused the Debian Bug report #892116,
regarding [PATCH] Please set Built-Using field
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.)
--
892116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prometheus-sql-exporter
Severity: wishlist
Tags: patch
Please consider merging the attached patch. Thanks!
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel, mipsel, arm64
Kernel: Linux 4.13.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
>From bd95f9fb8afdc6c3fe3c00307b85ac4b8a78503f Mon Sep 17 00:00:00 2001
From: Michael Stapelberg <stapelb...@debian.org>
Date: Mon, 5 Mar 2018 20:10:53 +0100
Subject: [PATCH] Set Built-Using
---
debian/control | 1 +
1 file changed, 1 insertion(+)
diff --git a/debian/control b/debian/control
index a8e1947..8db4c01 100644
--- a/debian/control
+++ b/debian/control
@@ -23,6 +23,7 @@ Depends:
postgresql-common,
${shlibs:Depends},
${misc:Depends},
+Built-Using: ${misc:Built-Using}
Description: Flexible SQL Exporter for Prometheus
This Prometheus exporter extracts various metrics from PostgreSQL, MySQL, and
MSSQL databases. The metrics are configurable via a YAML file.
--
2.15.1
--- End Message ---
--- Begin Message ---
Source: prometheus-sql-exporter
Source-Version: 0.2.0.ds-4
We believe that the bug you reported is fixed in the latest version of
prometheus-sql-exporter, 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 892...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christoph Berg <christoph.b...@credativ.de> (supplier of updated
prometheus-sql-exporter 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, 10 Apr 2018 13:34:56 +0200
Source: prometheus-sql-exporter
Binary: prometheus-sql-exporter
Architecture: source
Version: 0.2.0.ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Christoph Berg <christoph.b...@credativ.de>
Description:
prometheus-sql-exporter - Flexible SQL Exporter for Prometheus
Closes: 892116
Changes:
prometheus-sql-exporter (0.2.0.ds-4) unstable; urgency=medium
.
[ Michael Stapelberg ]
* Port to use dh-golang.
* Set Built-Using field. (Closes: #892116)
.
[ Christoph Berg ]
* Remove debug logging from our synchronous-jobs patch.
Checksums-Sha1:
ee3e86663058ba69c55336a1efc67037b03a1f14 2378
prometheus-sql-exporter_0.2.0.ds-4.dsc
928eb54707d4db8c51a2a05e3a8cbd4a99bf3570 4504
prometheus-sql-exporter_0.2.0.ds-4.debian.tar.xz
8e49b0dde91fe7e28723b3255af4f45c95b0996b 8087
prometheus-sql-exporter_0.2.0.ds-4_source.buildinfo
Checksums-Sha256:
dbd17a18183368e59e5ccd4950c2e64bf66e0dd98ce16d4ced6545eabe92dca9 2378
prometheus-sql-exporter_0.2.0.ds-4.dsc
b421eeff8084fd379c479527a8049f0d5443eefc385c8f8d9296bf49ca5db371 4504
prometheus-sql-exporter_0.2.0.ds-4.debian.tar.xz
b5e3ca2d151f02b82fb8e61a00be470d161c98b9fcd0704ea27def79e6f20c0b 8087
prometheus-sql-exporter_0.2.0.ds-4_source.buildinfo
Files:
8d278aa994f6863eb94d7ef198face4d 2378 database optional
prometheus-sql-exporter_0.2.0.ds-4.dsc
5ecc3978b019651b0ab33223873402dc 4504 database optional
prometheus-sql-exporter_0.2.0.ds-4.debian.tar.xz
cb076f27f1499a21b6d5129043e69842 8087 database optional
prometheus-sql-exporter_0.2.0.ds-4_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlrMpVkACgkQTFprqxLS
p67BNxAAkClMxG4IL3i78iKvhPEZF4KmlA0poCo8kRloejhlI+BS1x9Jkum2L7MF
cUUlYOKeb6SwTv00kDGCBY+3YodqYU0Bu3zn/
[Pkg-postgresql-public] Bug#894841: marked as done (pg-repack: fix failing dep8 tests with postgresql 10.3)
Your message dated Fri, 06 Apr 2018 13:06:34 + with message-id <e1f4r4c-0006pr...@fasolo.debian.org> and subject line Bug#894841: fixed in pg-repack 1.4.2-2 has caused the Debian Bug report #894841, regarding pg-repack: fix failing dep8 tests with postgresql 10.3 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.) -- 894841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pg-repack Version: 1.4.2-1 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu bionic ubuntu-patch Dear Maintainer, In Ubuntu, the attached patch was applied to fix DEP8 regressions with Postgresql 10.3. * debian/patches/always_qualify_relation_names.patch: Always qualify relation names. Thanks to Masahiko Sawada <sawada.m...@gmail.com>. Thanks for considering the patch. *** /tmp/tmpB3TGJW/pg-repack_1.4.2-1ubuntu1.debdiff diff -Nru pg-repack-1.4.2/debian/patches/always_qualify_relation_names.patch pg-repack-1.4.2/debian/patches/always_qualify_relation_names.patch --- pg-repack-1.4.2/debian/patches/always_qualify_relation_names.patch 1969-12-31 16:00:00.0 -0800 +++ pg-repack-1.4.2/debian/patches/always_qualify_relation_names.patch 2018-04-04 10:22:56.0 -0700 @@ -0,0 +1,2905 @@ +Description: Always qualify relation names + Due to change at PostgreSQL 10.3, 9.6.8, 9.5.12, 9.4.17 and 9.3.22, + relation names passed by PostgreSQL function such as + pg_get_indexdef_string() are schema-qualified, which could be cause + of a parse error. +Author: Masahiko Sawada <sawada.m...@gmail.com> +Origin: upstream, https://github.com/reorg/pg_repack/pull/172 +Bug: https://github.com/reorg/pg_repack/issues/169 +Bug: https://github.com/reorg/pg_repack/issues/174 +Forwarded: not-needed +Last-Update: 2018-04-04 + +--- a/lib/pg_repack.sql.in b/lib/pg_repack.sql.in +@@ -16,6 +16,30 @@ + $$SELECT 'pg_repack REPACK_VERSION'::text$$ + LANGUAGE SQL IMMUTABLE STRICT; + ++CREATE FUNCTION repack.pg_version(version_str text DEFAULT NULL) RETURNS integer ++AS $$ ++-- Return the server version number in a format similar to PG_VERSION_NUM. ++-- Call with no argument for the server version, pass an argument for testing ++select (case ++when array_length(tokens, 1) = 2 then ++to_char(tokens[1], 'FM00') || ++'00' || to_char(tokens[2], 'FM00') ++when array_length(tokens, 1) = 3 then ++to_char(tokens[1], 'FM00') || ++to_char(tokens[2], 'FM00') || ++to_char(tokens[3], 'FM00') ++else ++-- This will raise an error which we can read ++'unexpected version string: ' || coalesce($1, version()) ++end)::int ++from ( ++select string_to_array(substring( ++split_part(coalesce($1, version()), ' ', 2) ++from '\d+\.\d+(?:\.\d+)?'), '.')::int[] ++) as x (tokens); ++$$ ++LANGUAGE SQL IMMUTABLE; ++ + CREATE AGGREGATE repack.array_accum ( + sfunc = array_append, + basetype = anyelement, +--- a/lib/repack.c b/lib/repack.c +@@ -354,11 +354,30 @@ + Oid nsp = get_rel_namespace(relid); + char *nspname; + ++ /* ++ * Relation names given by PostgreSQL core are always ++ * qualified since some minor releases. Note that this change ++ * doesn't introduce to PostgreSQL 9.2 and 9.1 releases. ++ */ ++#if ((PG_VERSION_NUM >= 10 && PG_VERSION_NUM < 13) || \ ++ (PG_VERSION_NUM >= 90600 && PG_VERSION_NUM < 90608) || \ ++ (PG_VERSION_NUM >= 90500 && PG_VERSION_NUM < 90512) || \ ++ (PG_VERSION_NUM >= 90400 && PG_VERSION_NUM < 90417) || \ ++ (PG_VERSION_NUM >= 90300 && PG_VERSION_NUM < 90322) || \ ++ (PG_VERSION_NUM >= 90200 && PG_VERSION_NUM < 90300) || \ ++ (PG_VERSION_NUM >= 90100 && PG_VERSION_NUM < 90200)) + /* Qualify the name if not visible in search path */ + if (RelationIsVisible(relid)) + nspname = NULL; + else + nspname = get_namespace_name(nsp); ++#else ++ /* Qualify the name */ ++ if (OidIsValid(nsp)) ++ nspname = get_namespace_name(nsp); ++ else ++ nspname = NULL; ++#endif + + return quote_qualified_identifier(nspname, get_rel_name(relid)); + } +--- a/regress/expected/repack.out b/regress/expected/repack.out +@@ -1,14 +1,19 @@ + -- Test output fi
[Pkg-postgresql-public] Bug#894235: marked as done (patroni fails it's autopkg tests)
Your message dated Fri, 06 Apr 2018 12:19:54 + with message-id <e1f4qls-000glu...@fasolo.debian.org> and subject line Bug#894235: fixed in patroni 1.4.3-1 has caused the Debian Bug report #894235, regarding patroni fails it's autopkg tests 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.) -- 894235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894235 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:patroni Version: 1.4.2-2 Severity: important Tags: sid buster patch the autopkg tests are missing a dependency, patch at http://launchpadlibrarian.net/362272213/patroni_1.4.2-2_1.4.2-2ubuntu1.diff.gz please note the autopkg tests still fail on amd64 (at least in Ubuntu): http://autopkgtest.ubuntu.com/packages/p/patroni/bionic/amd64 Please keep an eye on failing autopkg tests. --- End Message --- --- Begin Message --- Source: patroni Source-Version: 1.4.3-1 We believe that the bug you reported is fixed in the latest version of patroni, 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 894...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg <christoph.b...@credativ.de> (supplier of updated patroni 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: Fri, 06 Apr 2018 12:13:27 +0200 Source: patroni Binary: patroni Architecture: source Version: 1.4.3-1 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public@lists.alioth.debian.org> Changed-By: Christoph Berg <christoph.b...@credativ.de> Description: patroni- Template for PostgreSQL High Availability Closes: 894235 Changes: patroni (1.4.3-1) unstable; urgency=medium . * New upstream version. * Add python3-coverage to acceptance test depends. Reported by Matthias Klose, thanks! Closes: #894235. Checksums-Sha1: fae8e9f9cf46fc42b2d2789e8109079ef2d51541 2786 patroni_1.4.3-1.dsc 00ca90d1810ddfa3f45c3673da430e2746c5cad5 665092 patroni_1.4.3.orig.tar.gz 36ab1cdbc5b59931c2065eca0c5c66ef352bd5e2 7220 patroni_1.4.3-1.debian.tar.xz cfc31001ba2299b36f567981f7c161fa23aae7cf 8782 patroni_1.4.3-1_source.buildinfo Checksums-Sha256: 581ac2a4b5963971ac890a63e46d49073abf48d001621d5d1531dcaf6e7126d7 2786 patroni_1.4.3-1.dsc 0fff3452555f1f0fde4a2de22d18c08652ef396a30428a5cf679e9f5c8b2a675 665092 patroni_1.4.3.orig.tar.gz ab44860f4988aed11fe2baae7d25d3699e64c08a5aac78f75b7d54a29ce30fc9 7220 patroni_1.4.3-1.debian.tar.xz 34ba463a252bef5467281c332e473d263980cae833d7ccca4a347a200cc41dc4 8782 patroni_1.4.3-1_source.buildinfo Files: a0638fd7aa10b90760bd8ff30cf9d984 2786 database optional patroni_1.4.3-1.dsc 2e1ccc4d2aab176c5b560e9c013d 665092 database optional patroni_1.4.3.orig.tar.gz 926477ef54c78af829a3c1f146ee2061 7220 database optional patroni_1.4.3-1.debian.tar.xz f552a6f66cbcc255f53ef8619afb2707 8782 database optional patroni_1.4.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlrHX/AACgkQTFprqxLS p64pexAAticqwvhg9gGILi8AfZWXio8TAn0sLLjEp0OO4camZyBsxDCxgSVnQKaI 43OTeMEwmt/WHA+Zvrmkw6hpGldWxdKIBi3SEh6fosGeq7pVkUhDs77MPWp+j6Gv 3s4Vh2AaLs16+r2q2MF1E72MY/z4q1HuZ5hkGeP/1FegqrdTUv1hhl5MA7g+UeRT 3eqNEMOMiw7jS2aCEq7J0LVqLZtUXqHsgEm1DArS2SRxj0USO0+p/2RfBboBbqYh +tMyDt2pXaKyEoI3OIl7vXvU/k6LVnqX29I2/aJbCYJQ3+tI/8mVlshvB0u5yy/Z tW73u//s8TCn+jDCQqmABvNeVrhrOJyXlP5bPfdjgnyvi4eUGSfCi7OFUDq9VPl9 WhlawJIwdIaN7P9wcKqHj+Ns5QPoToWW5BSepImdfg6v9V4BPH0aPrrJ8L+a2IWy /Z47JYdQEI19YRHnHCcyfgNbR5q69X+jEYG/9IAtenGppeUWeCv1Ijk0G3LROm/K HmIh6RHwHg3iDr3VgBhSCuJ8+OVRUyJ5Ckietunt+xH945o5fukKYw48L8+Xre3w UeO3pZ9f6q3bI+8as4mcGs7HpZE1qrlBBloNPuMEpMib8NCmaSEdaEG4C7Ysp+7Y ly6EoHGJNHvf6G/Mqgucx2ai1HGcD+XDkc3Ll096plyGE0M0/t4= =XPZe -END PGP SIGNATURE End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: apgdiff: move out of asciidoc - patch
Processing control commands: > tags -1 + patch Bug #894697 [apgdiff] apgdiff: move out of asciidoc Added tag(s) patch. -- 894697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#892807: marked as done (postgresl-10: please disable spinlocks on riscv64)
Your message dated Wed, 21 Mar 2018 13:36:59 + with message-id <e1eydvh-0008sa...@fasolo.debian.org> and subject line Bug#892807: fixed in postgresql-10 10.3-2 has caused the Debian Bug report #892807, regarding postgresl-10: please disable spinlocks on riscv64 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.) -- 892807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: postgresl-10 Version: 10.3-1 Severity: wishlist Tags: patch User: debian-ri...@lists.debian.org Usertags: riscv64 Hello, We are in the process of bootstrapping a Debian port for the riscv64 architecture (https://wiki.debian.org/RISC-V). It happens that native spinlocks are not yet supported on RISC-V. Would it be possible to pass --disable-spinlocks to the configure script like already done on alpha? This is a first step which allows postgresql to be compiled and pass the testsuite on riscv64. Thanks, Aurelien diff -Nru postgresql-10-10.3/debian/rules postgresql-10-10.3/debian/rules --- postgresql-10-10.3/debian/rules 2018-01-20 10:49:03.0 +0100 +++ postgresql-10-10.3/debian/rules 2018-03-12 23:24:03.0 +0100 @@ -42,7 +42,7 @@ export DPKG_GENSYMBOLS_CHECK_LEVEL=4 # PostgreSQL 9.5+ does not have native spinlock support on this platform -ifneq ($(findstring $(DEB_HOST_ARCH), alpha),) +ifneq ($(findstring $(DEB_HOST_ARCH), alpha riscv64),) SPINLOCK_FLAGS = --disable-spinlocks endif --- End Message --- --- Begin Message --- Source: postgresql-10 Source-Version: 10.3-2 We believe that the bug you reported is fixed in the latest version of postgresql-10, 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 892...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg <christoph.b...@credativ.de> (supplier of updated postgresql-10 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: Wed, 21 Mar 2018 13:56:34 +0100 Source: postgresql-10 Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3 postgresql-10 postgresql-client-10 postgresql-server-dev-10 postgresql-doc-10 postgresql-plperl-10 postgresql-plpython-10 postgresql-plpython3-10 postgresql-pltcl-10 Architecture: source Version: 10.3-2 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public@lists.alioth.debian.org> Changed-By: Christoph Berg <christoph.b...@credativ.de> Description: libecpg-compat3 - older version of run-time library for ECPG programs libecpg-dev - development files for ECPG (Embedded PostgreSQL for C) libecpg6 - run-time library for ECPG programs libpgtypes3 - shared library libpgtypes for PostgreSQL 10 libpq-dev - header files for libpq5 (PostgreSQL library) libpq5 - PostgreSQL C client library postgresql-10 - object-relational SQL database, version 10 server postgresql-client-10 - front-end programs for PostgreSQL 10 postgresql-doc-10 - documentation for the PostgreSQL database management system postgresql-plperl-10 - PL/Perl procedural language for PostgreSQL 10 postgresql-plpython-10 - PL/Python procedural language for PostgreSQL 10 postgresql-plpython3-10 - PL/Python 3 procedural language for PostgreSQL 10 postgresql-pltcl-10 - PL/Tcl procedural language for PostgreSQL 10 postgresql-server-dev-10 - development files for PostgreSQL 10 server-side programming Closes: 891898 892807 Changes: postgresql-10 (10.3-2) unstable; urgency=medium . * Improve wording of NEWS entry on search_path changes. Thanks Chris Lamb! (Closes: #891898) * Disable spinlocks on riscv64, thanks Aurelien Jarno! (Closes: #892807) * B-D on python3-distutils | python3-dev (<< 3.6.4~rc1-2). Checksums-Sha1: 705d70eee482655783a6c672895b87622969c5db 3524 postgresql-10_10.3-2.dsc 02fa752b1b72bc81d488080d2971f634a88dc180 23032 postgresql-10_10.3-2.debian.tar.xz ba3cdf8aa980b6eb16b4e774d23a8dc942084563 8184 postgre
[Pkg-postgresql-public] Bug#891898: marked as done (postgresql-10: Please update NEWS entry for 10.3-1)
Your message dated Wed, 21 Mar 2018 13:36:59 + with message-id <e1eydvh-0008s4...@fasolo.debian.org> and subject line Bug#891898: fixed in postgresql-10 10.3-2 has caused the Debian Bug report #891898, regarding postgresql-10: Please update NEWS entry for 10.3-1 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.) -- 891898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: postgresql-10 Version: 10.3-1 Severity: wishlist Tags: patch Hi, Thank you so much for caring about users etc. and including NEWS entries for display by apt-listchanges. However, I did feel that the most recent entry could be slightly improved. I have attached a patch with my suggested changes; they should be self-explanatory. :) Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/debian/postgresql-10.NEWS b/debian/postgresql-10.NEWS index a7a639b..bf9aa00 100644 --- a/debian/postgresql-10.NEWS +++ b/debian/postgresql-10.NEWS @@ -1,14 +1,16 @@ postgresql-10 (10.3-1) unstable; urgency=medium - If you run an installation in which not all users are mutually trusting, or - if you maintain an application or extension that is intended for use in - arbitrary situations, it is strongly recommended that you read the release - notes regarding changes around "search_path", and take suitable steps to - ensure that your installation or code is secure. - - Also, these changes may cause functions used in index expressions or - materialized views to fail during auto-analyze, or when reloading from a - dump. After upgrading, monitor the server logs for such problems, and fix + If you run an installation where the users are mutually trusting or if you + maintain an application or extension that is intended for use in arbitrary + situations, it is highly recommended that you read the release notes + regarding changes around "search_path", and take suitable steps to ensure + that your installation or code is secure: + +https://www.postgresql.org/docs/10/static/release-10-3.html#id-1.11.6.5.5 + + In addition, these changes may cause functions used in index expressions or + materialized views to fail during auto-analyze or when reloading from a dump. + After upgrading, please monitor the server logs for such problems and fix any affected functions. -- Christoph Berg <christoph.b...@credativ.de> Tue, 27 Feb 2018 12:57:11 +0100 --- End Message --- --- Begin Message --- Source: postgresql-10 Source-Version: 10.3-2 We believe that the bug you reported is fixed in the latest version of postgresql-10, 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 891...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg <christoph.b...@credativ.de> (supplier of updated postgresql-10 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: Wed, 21 Mar 2018 13:56:34 +0100 Source: postgresql-10 Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3 postgresql-10 postgresql-client-10 postgresql-server-dev-10 postgresql-doc-10 postgresql-plperl-10 postgresql-plpython-10 postgresql-plpython3-10 postgresql-pltcl-10 Architecture: source Version: 10.3-2 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public@lists.alioth.debian.org> Changed-By: Christoph Berg <christoph.b...@credativ.de> Description: libecpg-compat3 - older version of run-time library for ECPG programs libecpg-dev - development files for ECPG (Embedded PostgreSQL for C) libecpg6 - run-time library for ECPG programs libpgtypes3 - shared library libpgtypes for PostgreSQL 10 libpq-dev - header files for libpq5 (PostgreSQL library) libpq5 - PostgreSQL C client library postgresql-10 - object-relational SQL database, version 10 server postgresql-client-10 - front-end programs for PostgreSQL 10 postgresql-doc-10 - documentation for the PostgreSQL database management system postgresql-plperl-
[Pkg-postgresql-public] Bug#881498: marked as done (postgresql-mysql-fdw: autopkgtests fail with postgresql-10)
Your message dated Sat, 17 Mar 2018 21:03:59 +0100 with message-id <20180317200359.ga14...@msg.df7cb.de> and subject line Re: Bug#881498: [Pkg-postgresql-public] Bug#881498: postgresql-mysql-fdw: autopkgtests fail with postgresql-10 has caused the Debian Bug report #881498, regarding postgresql-mysql-fdw: autopkgtests fail with postgresql-10 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.) -- 881498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: postgresql-mysql-fdw Version: 2.3.0-1 Severity: important The autopkgtests for postgresql-mysql-fdw started failing once postgresql-10 was used by default. https://ci.debian.net/packages/p/postgresql-mysql-fdw/unstable/amd64/ http://autopkgtest.ubuntu.com/packages/p/postgresql-mysql-fdw Ubuntu uses autopkgtests before allowing packages to migrate from -proposed so this is one of the blockers for Ubuntu's postgresql-10 transition. Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- Version: 2.3.0-2 Re: To Jeremy Bicha 2017-11-12 <20171112150528.ovgk5egw2u67r...@msg.df7cb.de> > > The autopkgtests for postgresql-mysql-fdw started failing once > > postgresql-10 was used by default. > > > > https://ci.debian.net/packages/p/postgresql-mysql-fdw/unstable/amd64/ > > http://autopkgtest.ubuntu.com/packages/p/postgresql-mysql-fdw > > I've reported that upstream: > https://github.com/EnterpriseDB/mysql_fdw/issues/147 The upstream issue is still present which is why I forgot to actually close this bug on the Debian side when I silenced the error here. Christoph--- End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#795729: marked as done (libpqtypes: FTBFS under some timezones (eg. GMT+12))
Your message dated Sat, 17 Mar 2018 17:36:00 +
with message-id <e1exfko-000hha...@fasolo.debian.org>
and subject line Bug#795729: fixed in libpqtypes 1.5.1-3
has caused the Debian Bug report #795729,
regarding libpqtypes: FTBFS under some timezones (eg. GMT+12)
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.)
--
795729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpqtypes
Version: 1.5.1-2
Severity: serious
Justification: fails to build from source
Dear Maintainer,
libpqtypes fails to build from source on unstable/amd64 under
some timezones (eg. TZ="/usr/share/zoneinfo/Etc/GMT+12"):
[..]
debian/rules override_dh_auto_test
make[1]: Entering directory '/tmp/buildd/libpqtypes-1.5.1'
/usr/bin/make test LDFLAGS+=-L.libs
make[2]: Entering directory '/tmp/buildd/libpqtypes-1.5.1'
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-O3 -Wall -Wpointer-arith -D_GNU_SOURCE -D_REENTRANT -fsigned-char
-std=gnu99 -Wclobbered -Wempty-body -Wignored-qualifiers
-Wmissing-parameter-type -Wold-style-declaration -Woverride-init
-Wsign-compare -Wtype-limits -Wuninitialized -fomit-frame-pointer
-fno-strict-aliasing -funroll-all-loops -funit-at-a-time -Wdate-time
-D_FORTIFY_SOURCE=2 -I/usr/include/postgresql -Isrc -DHAVE_CONFIG_H \
-o test src/regression-test.c -Wl,-z,relro -L.libs -lm -lpq
-lpqtypes
src/regression-test.c: In function 'main':
src/regression-test.c:235:11: warning: variable 'ba' set but not used
[-Wunused-but-set-variable]
PGbytea ba;
^
make[2]: Leaving directory '/tmp/buildd/libpqtypes-1.5.1'
LD_LIBRARY_PATH=:.libs pg_virtualenv ./test ""
install: cannot change owner and permissions of
'/tmp/pg_virtualenv.2sBpjO/postgresql/9.4': Operation not permitted
Creating new cluster 9.4/regress ...
config /tmp/pg_virtualenv.2sBpjO/postgresql/9.4/regress
data /tmp/pg_virtualenv.2sBpjO/data/9.4/regress
locale C
Warning: The socket directory for owners other than 'postgres'
defaults to /tmp. You might want to change the unix_socket_directories
parameter
in postgresql.conf to a more secure directory.
port 5432
Warning: The parent /var/run/postgresql of the selected
stats_temp_directory is not writable for the cluster owner. Not adding
this
setting in postgresql.conf.
server type lookup failed: could not find 'mytype_t'
%epoch - passed
%epoch - passed
%timestamptz - FAILED
Composites & Arrays: (always binary)
Testing empty array handling - passed
composite[] with nested composite and arrays passed
PQputvf
SELECT $1 + ($2 % $3) AS answer
PQputvf - passed
PQspecPrepare
PQspecPrepare - passed
Native C types: (text)
%char - passed
%char - passed
%int2 - passed
%int2 - passed
%int4 - passed
%int4 - passed
%int8 - passed
%int8 - passed
%float4 - passed
%float4 - passed
%float8 - passed
%float8 - passed
%money - passed
%money - passed
%oid - passed
%oid - passed
%bool - passed
%bool - passed
Native C types: (binary)
%char - passed
%char - passed
%int2 - passed
%int2 - passed
%int4 - passed
%int4 - passed
%int8 - passed
%int8 - passed
%float4 - passed
%float4 - passed
%float8 - passed
%float8 - passed
%money - passed
%money - passed
%oid - passed
%oid - passed
%bool - passed
%bool - passed
Variable-length types: (text)
%bpchar - passed
%varchar - passed
%text - passed
%bytea* - passed
%uuid - passed
%numeric - passed
Variable-length types: (binary)
%bpchar - passed
%varchar - passed
%text - passed
%bytea* - passed
%uuid - passed
%numeric - passed
Geometric types: (text)
%point - passed
%lseg - passed
%box - passed
%circle - passed
%path - passed
%polygon - passed
Geometric types: (binary)
%point - passed
%lseg - passed
%box - passed
%circle - passed
%path - passed
%polygon - passed
Network types: (text)
%inet - IPv4 passed
%inet - IPv6 passed
%macaddr - passed
Network types: (binary)
%inet - IPv4 passed
%inet - IPv6 passed
%macaddr - passed
Sub-class: (text)
epoch_put('0')
epoch_put('946702800')
epoch_get(text)
epoch_get(text)
Sub-class: (binary)
epoch_put('0')
epoch_put('946702800')
epoch_ge
[Pkg-postgresql-public] Processed: limit source to postgresql-10, tagging 891898, tagging 892807
Processing commands for cont...@bugs.debian.org: > limit source postgresql-10 Limiting to bugs with field 'source' containing at least one of 'postgresql-10' Limit currently set to 'source':'postgresql-10' > tags 891898 + pending Bug #891898 [src:postgresql-10] postgresql-10: Please update NEWS entry for 10.3-1 Added tag(s) pending. > tags 892807 + pending Bug #892807 [src:postgresql-10] postgresl-10: please disable spinlocks on riscv64 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 891898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891898 892807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: reassign 892807 to src:postgresql-10, reassign 843068 to src:pywinrm
Processing commands for cont...@bugs.debian.org: > reassign 892807 src:postgresql-10 10.3-1 Bug #892807 [src:postgresql-10] postgresl-10: please disable spinlocks on riscv64 Ignoring request to reassign bug #892807 to the same package Bug #892807 [src:postgresql-10] postgresl-10: please disable spinlocks on riscv64 Ignoring request to alter found versions of bug #892807 to the same values previously set > reassign 843068 src:pywinrm 0.0.3-1 Bug #843068 [python-winrm] python-winrm: new upstream release Warning: Unknown package 'python-winrm' Bug reassigned from package 'python-winrm' to 'src:pywinrm'. No longer marked as found in versions pywinrm/0.0.3-1. Ignoring request to alter fixed versions of bug #843068 to the same values previously set Bug #843068 [src:pywinrm] python-winrm: new upstream release Marked as found in versions pywinrm/0.0.3-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 843068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843068 892807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: reassign 892807 to src:postgresql-10
Processing commands for cont...@bugs.debian.org: > reassign 892807 src:postgresql-10 10.3-1 Bug #892807 [src:postgresl-10] postgresl-10: please disable spinlocks on riscv64 Warning: Unknown package 'src:postgresl-10' Bug reassigned from package 'src:postgresl-10' to 'src:postgresql-10'. No longer marked as found in versions postgresl-10/10.3-1. Ignoring request to alter fixed versions of bug #892807 to the same values previously set Bug #892807 [src:postgresql-10] postgresl-10: please disable spinlocks on riscv64 Marked as found in versions postgresql-10/10.3-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 892807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: closing 892778
Processing commands for cont...@bugs.debian.org: > close 892778 Bug #892778 [phppgadmin] phppgadmin: php need to recompile PHP using the --with-pgsql configure option Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 892778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: Re: Bug#892778: phppgadmin: php need to recompile PHP using the --with-pgsql configure option
Processing control commands: > tags -1 moreinfo Bug #892778 [phppgadmin] phppgadmin: php need to recompile PHP using the --with-pgsql configure option Added tag(s) moreinfo. -- 892778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: limit source to prometheus-sql-exporter, tagging 892116
Processing commands for cont...@bugs.debian.org: > limit source prometheus-sql-exporter Limiting to bugs with field 'source' containing at least one of 'prometheus-sql-exporter' Limit currently set to 'source':'prometheus-sql-exporter' > tags 892116 + pending Bug #892116 [src:prometheus-sql-exporter] [PATCH] Please set Built-Using field Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 892116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: Re: Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors
Processing control commands: > reassign -1 postgresql Bug #891836 [systemd] systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors Bug reassigned from package 'systemd' to 'postgresql'. No longer marked as found in versions systemd/232-25+deb9u1. Ignoring request to alter fixed versions of bug #891836 to the same values previously set -- 891836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: retitle 891687 to postgresql-common: provide easy way to spin up a systemd user service cluster
Processing commands for cont...@bugs.debian.org: > retitle 891687 postgresql-common: provide easy way to spin up a systemd user > service cluster Bug #891687 [postgresql-common] postgresql-common: dsfwew Changed Bug title to 'postgresql-common: provide easy way to spin up a systemd user service cluster' from 'postgresql-common: dsfwew'. > thanks Stopping processing here. Please contact me if you need assistance. -- 891687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: forcibly merging 884457 891488
Processing commands for cont...@bugs.debian.org: > forcemerge 884457 891488 Bug #884457 [postgresql-client-common] post-install failure when /usr/share/man/man1/ does not exist Bug #891488 [postgresql-client-common] postgresql: Installing postgresql fails due to "error creating symbolic link '/usr/share/man/man1/psql.1.gz.dpkg-tmp': No such file or directory" Severity set to 'wishlist' from 'normal' Merged 884457 891488 > thanks Stopping processing here. Please contact me if you need assistance. -- 884457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884457 891488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed (with 1 error): reassign 891488 to postgresql-client-common, merging 891488 884457
Processing commands for cont...@bugs.debian.org: > reassign 891488 postgresql-client-common Bug #891488 [postgresql] postgresql: Installing postgresql fails due to "error creating symbolic link '/usr/share/man/man1/psql.1.gz.dpkg-tmp': No such file or directory" Bug reassigned from package 'postgresql' to 'postgresql-client-common'. No longer marked as found in versions postgresql-common/181+deb9u1. Ignoring request to alter fixed versions of bug #891488 to the same values previously set > merge 891488 884457 Bug #891488 [postgresql-client-common] postgresql: Installing postgresql fails due to "error creating symbolic link '/usr/share/man/man1/psql.1.gz.dpkg-tmp': No such file or directory" Unable to merge bugs because: severity of #884457 is 'wishlist' not 'normal' Failed to merge 891488: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 884457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884457 891488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#749809: marked as done (pgpool2: Undefined conversion from double to enum)
Your message dated Sun, 25 Feb 2018 16:23:08 +0100 with message-id <20180225152308.ga14...@msg.df7cb.de> and subject line Re: Bug#749809: pgpool2: Undefined conversion from double to enum has caused the Debian Bug report #749809, regarding pgpool2: Undefined conversion from double to enum 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.) -- 749809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pgpool2 Version: 3.3.3-2 Usertags: goto-cc During a rebuild of all packages in a clean sid chroot (and cowbuilder+pbuilder) the build failed with the following error. Please note that we use our research compiler tool-chain (using tools from the cbmc package), which permits extended reporting on type inconsistencies at link time. [...] libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -D_GNU_SOURCE -I .. -I /usr/include/postgresql -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wmissing-prototypes -Wmissing-declarations -MT pcp.lo -MD -MP -MF .deps/pcp.Tpo -c pcp.c -fPIC -DPIC -o .libs/pcp.o file pcp.c line 1649 function pcp_watchdog_info: in expression `atof(index)': conversion from `double' to `WD_STATUS': implicit conversion not permitted CONVERSION ERROR Makefile:638: recipe for target 'pcp.lo' failed make[3]: *** [pcp.lo] Error 1 make[3]: Leaving directory '/srv/jenkins-slave/workspace/sid-goto-cc-pgpool2/pgpool2-3.3.3/pcp' Makefile:861: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 This is here: http://sources.debian.net/src/pgpool2/3.3.3-2/pcp/pcp.c?hl=1649#L1649 It may have historic reasons that atof is used here, but this should really be a checked conversion towards one of the legitimated values of WD_STATUS: http://sources.debian.net/src/pgpool2/3.3.3-2/watchdog/watchdog.h?hl=109#L103 (and that checked conversion would use atoi). Best, Michael pgp_e_saqTkwP.pgp Description: PGP signature --- End Message --- --- Begin Message --- Re: To Michael Tautschnig 2018-02-18 <20180218153904.ga27...@msg.df7cb.de> > is this problem still present? Closing for now. Christoph--- End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: closing 890830
Processing commands for cont...@bugs.debian.org: > close 890830 0.9.1~beta-1 Bug #890830 [pgmodeler] pgmodeler: unable to connect to remote dbcluster with ssl Marked as fixed in versions pgmodeler/0.9.1~beta-1. Bug #890830 [pgmodeler] pgmodeler: unable to connect to remote dbcluster with ssl Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 890830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: Re: Bug#891049: pgmodeler: version in stretch incompatible with db version in stretch
Processing control commands: > severity -1 serious Bug #891049 [pgmodeler] pgmodeler: version in stretch incompatible with db version in stretch Severity set to 'serious' from 'normal' -- 891049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#891049: marked as done (pgmodeler: version in stretch incompatible with db version in stretch)
Your message dated Thu, 22 Feb 2018 10:19:23 +0100 with message-id <20180222091923.ga20...@msg.df7cb.de> and subject line Re: Bug#891049: pgmodeler: version in stretch incompatible with db version in stretch has caused the Debian Bug report #891049, regarding pgmodeler: version in stretch incompatible with db version in stretch 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.) -- 891049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pgmodeler Version: 0.8.2-1+b1 Severity: normal Hi! I would like to use pgmodeler in Stretch, but the program can't work with PostgreSQL 9.6, also in Stretch. I get an error message that only versions up to 9.5 are supported, and that's the end of the story. Cheers, Toni -- System Information: Debian Release: 9.3 APT prefers stable APT policy: (990, 'stable'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pgmodeler depends on: ii libc6 2.24-11+deb9u1 ii libgcc1 1:6.3.0-18 ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 ii libpq59.6.6-0+deb9u1 ii libqt5core5a 5.7.1+dfsg-3+b1 ii libqt5gui55.7.1+dfsg-3+b1 ii libqt5network55.7.1+dfsg-3+b1 ii libqt5printsupport5 5.7.1+dfsg-3+b1 ii libqt5svg55.7.1~20161021-2+b2 ii libqt5widgets55.7.1+dfsg-3+b1 ii libstdc++66.3.0-18 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 ii libxml2 2.9.4+dfsg1-2.2+deb9u2 ii pgmodeler-common 0.8.2-1 pgmodeler recommends no packages. pgmodeler suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Control: severity -1 serious Version: 0.9.1~beta-1 Re: Toni Mueller 2018-02-21 <151925212500.8837.9009431344134188619.report...@spruce.office.oeko.net> > I would like to use pgmodeler in Stretch, but the program can't work > with PostgreSQL 9.6, also in Stretch. I get an error message that only > versions up to 9.5 are supported, and that's the end of the story. Oops. We've only recently imported pgmodeler into the PostgreSQL team, so obviously this incompatibility fell through the cracks. Sorry. I don't see that we can realistically upgrade pgmodeler in stretch, so there's two workarounds available: using pgmodeler from buster, or use the stretch-pgdg distribution from apt.postgresql.org. Christoph--- End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: found 890830 in 0.8.2-1
Processing commands for cont...@bugs.debian.org: > found 890830 0.8.2-1 Bug #890830 [pgmodeler] pgmodeler: unable to connect to remote dbcluster with ssl Marked as found in versions pgmodeler/0.8.2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 890830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: Re: Bug#749809: pgpool2: Undefined conversion from double to enum
Processing control commands: > tags -1 moreinfo Bug #749809 [pgpool2] pgpool2: Undefined conversion from double to enum Added tag(s) moreinfo. -- 749809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#828769: marked as done (pgpool2: stale socket files after systemd kills pgpool processes duringstop)
Your message dated Sun, 18 Feb 2018 15:52:07 +
with message-id <e1enrg3-0008gp...@fasolo.debian.org>
and subject line Bug#828769: fixed in pgpool2 3.7.2-1
has caused the Debian Bug report #828769,
regarding pgpool2: stale socket files after systemd kills pgpool processes
duringstop
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.)
--
828769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pgpool2
Version: 3.4.3-1
Severity: minor
Dear Maintainer,
I'm having an issue with stale pgpool2 socket files if systemd had killed the
pgpool processes while in progress of stopping pgpool2.
First of all, there is a systemd.service file for pgpool2 in
/lib/systemd/system/pgpool2.service. As it does not specify an explicit
ExecStop, default systemd.kill is used - first all pgpool processes will receive
a SIGTERM signal and, after a timeout of 90s, all remaining processes get a
final SIGKILL.
In my setups, sometimes stopping pgpool2 takes longer than the above mentioned
timeout (maybe long running SQL queries or so) - here SIGKILL kicks in. In
(rare) cases where pgpool somehow has locked up it may also refuse to kindly
exit cleanly - also here SIGKILL will used when trying to use systemd to stop
pgpool2. When the processes get killed hard, they will leave residues in
$socket_dir.
srwxrwxrwx 1 postgres postgres 0 Jun 23 07:02 /var/run/postgresql/.s.PGSQL.5432
srwxrwxrwx 1 postgres postgres 0 Jun 23 07:02 /var/run/postgresql/.s.PGSQL.9898
(On the next start|during a restart), pgpool2 will finally fail to start
claiming that the socket file(s) already exist(s). Like:
pgpool[7643]: [5-1] 2016-06-27 16:58:00: pid 7643: FATAL: failed to bind a
socket: "/var/run/postgresql/.s.PGSQL.9898"
pgpool[7643]: [5-2] 2016-06-27 16:58:00: pid 7643: DETAIL: bind socket failed
with error: "Address already in use"
As a first-aid I have added two ExecStartPre's to pgpool2.service that will
cleanup the sockets - if there is no more running pgpool process - before trying
to start pgpool2.
ExecStartPre=/bin/bash -c "{ /usr/bin/test -s /var/run/postgresql/pgpool.pid &&
! /usr/bin/pgrep --pidfile /var/run/postgresql/pgpool.pid; } || { /usr/bin/test
! -s /var/run/postgresql/pgpool.pid && ! /usr/bin/pgrep pgpool; } && {
/usr/bin/test -S /var/run/postgresql/.s.PGSQL.9898 && /bin/rm
/var/run/postgresql/.s.PGSQL.9898; } || /usr/bin/test ! -S
/var/run/postgresql/.s.PGSQL.9898"
ExecStartPre=/bin/bash -c "{ /usr/bin/test -s /var/run/postgresql/pgpool.pid &&
! /usr/bin/pgrep --pidfile /var/run/postgresql/pgpool.pid; } || { /usr/bin/test
! -s /var/run/postgresql/pgpool.pid && ! /usr/bin/pgrep pgpool; } && {
/usr/bin/test -S /var/run/postgresql/.s.PGSQL.5432 && /bin/rm
/var/run/postgresql/.s.PGSQL.5432; } || /usr/bin/test ! -S
/var/run/postgresql/.s.PGSQL.5432"
Rather hacky with the hardcoded socket filenames. Otherwise IMHO 'port' and
'pcp_port' parameters from pgpool.conf needs to be looked up first to guess the
socket names.
My question - do you see a cleaner way to handle that situation?
-- System Information:
Debian Release: 8.5
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: pgpool2
Source-Version: 3.7.2-1
We believe that the bug you reported is fixed in the latest version of
pgpool2, 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 828...@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 pgpool2 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: Sun, 18 Feb 2018 12:52:30 +0100
Source: pgpool2
Binary: pgpool2 libpgpool0 libpgpool-dev postgresql-10-pgpool2
Architecture: source
Versi
[Pkg-postgresql-public] Bug#888446: marked as done (phppgadmin - Connection fail with postgreSQL 10)
Your message dated Wed, 14 Feb 2018 22:33:49 +0100
with message-id <2473187.ZvvxJOMcBf@deimos>
and subject line Bug#888446: fixed in phppgadmin 5.1+ds-3
has caused the Debian Bug report #888446,
regarding phppgadmin - Connection fail with postgreSQL 10
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.)
--
888446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phppgadmin
Version: 5.1+ds-2
Branch: buster (testing)
Hi,
There is a connection problem with postgreslq 10 on buster.
run application on http://localhost/phppgadmin/
Add my credentials, but the applicaction show the next error:
*Version of PostgreSQL not supported. Please upgrade to version or later.*
To fix, I follow the next link
https://stackoverflow.com/questions/46794672/installing-phppgadmin-5-1-on-ubuntu-16-04-with-postgresql-10-not-supported
I change the file:
*/usr/share/phppgadmin/classes/database/Connection.php*
// Detect version and choose appropriate database driver
switch (substr($version,0,3)) {
*case '10.': // add this line to fix partialy the problem*
case '9.2': return 'Postgres'; break;
case '9.1': return 'Postgres91'; break;
case '9.0': return 'Postgres90'; break;
case '8.4': return 'Postgres84'; break;
case '8.3': return 'Postgres83'; break;
case '8.2': return 'Postgres82'; break;
case '8.1': return 'Postgres81'; break;
case '8.0':
case '7.5': return 'Postgres80'; break;
case '7.4': return 'Postgres74'; break;
}
Pleace, can you fix the problem in the package?
Thanks a lot.
Ing. Yadickson Soto
+56 9 9668 8798
Usuario Linux #497718
--- End Message ---
--- Begin Message ---
Source: phppgadmin
Source-Version: 5.1+ds-3
We believe that the bug you reported is fixed in the latest version of
phppgadmin, 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 888...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jean-Michel Vourgère <nir...@debian.org> (supplier of updated phppgadmin
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)
signature.asc
Description: This is a digitally signed message part.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 14 Feb 2018 20:52:56 +
Source: phppgadmin
Binary: phppgadmin
Architecture: source all
Version: 5.1+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Jean-Michel Vourgère <nir...@debian.org>
Description:
phppgadmin - web-based administration tool for PostgreSQL
Closes: 886446 886454
Changes:
phppgadmin (5.1+ds-3) unstable; urgency=medium
.
[ Christoph Berg ]
* Move packaging repository to salsa.debian.org
.
[ Jean-Michel Vourgère ]
* Bumped policy to 4.1.3: Priority is now optional.
* Bumped compat to 11.
* Fix exports with new patch fix-obsolete-pgdump-flag to remove -i option
from pg_dump calls. Thanks to roger21. Closes: #886454
* Add support for postgres version with 2 digits with patch
2digit-pg-versions. Closes: #886446
Checksums-Sha1:
f0d093c6d0dec5990118c9eb80292b66dc13e2ee 2022 phppgadmin_5.1+ds-3.dsc
de5618c7d0c3d0bc0dd4b8ad1775687084b198c9 11908
phppgadmin_5.1+ds-3.debian.tar.xz
8c308501aa7620273c5e6f1e37db20a1c350ed9c 450228 phppgadmin_5.1+ds-3_all.deb
1a0b0e34cda431c778fd74669460f2567d212e3f 5967
phppgadmin_5.1+ds-3_amd64.buildinfo
Checksums-Sha256:
8a2b6d37d9ea350a5aa11cc55f29126ad20947f8c75a3bf8b27d21b6ec9be0a2 2022
phppgadmin_5.1+ds-3.dsc
42cc5bf1c4b54a71d0fe2e00aad43d31a8134ee00cec73815a18f8762806c191 11908
phppgadmin_5.1+ds-3.debian.tar.xz
6277d8ec43e6c88944c81f7af0662ee0570be4113970092c3b087c4e7830db97 450228
phppgadmin_5.1+ds-3_all.deb
3779c43a09f7663a493d9806546687d001140ec79974d7d94cfbbec961af24e2 5967
phppgadmin_5.1+ds-3_amd64.buildinfo
Files:
b44dde2e3ff3a1dc1425abcc39ee150f 2022 web optional phppgadmin_5.1+ds-3.dsc
dd72fa0a7f620b621ece8fa6bd37f6cc 11908 web optional
phppgadmin_5.1+ds-3.debian.tar.xz
98813284c80adea945cd85533a5526ab 450228 web optional
php
[Pkg-postgresql-public] Bug#886454: marked as done (pg_dump: invalid option -- 'i')
Your message dated Wed, 14 Feb 2018 21:19:45 + with message-id <e1em4sv-000eoy...@fasolo.debian.org> and subject line Bug#886454: fixed in phppgadmin 5.1+ds-3 has caused the Debian Bug report #886454, regarding pg_dump: invalid option -- 'i' 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.) -- 886454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886454 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: phppgadmin Version: 5.1-1.1 Date: Sat, 6 Jan 2018 06:20:56 +0100 From: roger21 <roge...@free.fr> To: pkg-postgresql-public@lists.alioth.debian.org Subject: [Pkg-postgresql-public] bug in the export feature of phpPgAdmin Hi, i can't do a descent bug report but still i'm trying to report that : the export feature of phpPgAdmin fails since it uses an obsolete parameter (-i) for pg_dump as reported by the apache/php error log : error.log:/usr/lib/postgresql/9.6/bin/pg_dump: invalid option -- 'i' error.log:Try "pg_dump --help" for more information. the bug is in the file /usr/share/phppgadmin/dbexport.php : at line 76 : $cmd = $exe . " -i";" must be replaced by : "$cmd = $exe;" the -i parameters does not need to be replaced by anything. the bug is well known, there are even youtube video about the fix ... the phpPgAdmin development seems discontinued but i hope this could be patched since it is so minor. cheers --- End Message --- --- Begin Message --- Source: phppgadmin Source-Version: 5.1+ds-3 We believe that the bug you reported is fixed in the latest version of phppgadmin, 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 886...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jean-Michel Vourgère <nir...@debian.org> (supplier of updated phppgadmin 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: Wed, 14 Feb 2018 20:52:56 + Source: phppgadmin Binary: phppgadmin Architecture: source all Version: 5.1+ds-3 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public@lists.alioth.debian.org> Changed-By: Jean-Michel Vourgère <nir...@debian.org> Description: phppgadmin - web-based administration tool for PostgreSQL Closes: 886446 886454 Changes: phppgadmin (5.1+ds-3) unstable; urgency=medium . [ Christoph Berg ] * Move packaging repository to salsa.debian.org . [ Jean-Michel Vourgère ] * Bumped policy to 4.1.3: Priority is now optional. * Bumped compat to 11. * Fix exports with new patch fix-obsolete-pgdump-flag to remove -i option from pg_dump calls. Thanks to roger21. Closes: #886454 * Add support for postgres version with 2 digits with patch 2digit-pg-versions. Closes: #886446 Checksums-Sha1: f0d093c6d0dec5990118c9eb80292b66dc13e2ee 2022 phppgadmin_5.1+ds-3.dsc de5618c7d0c3d0bc0dd4b8ad1775687084b198c9 11908 phppgadmin_5.1+ds-3.debian.tar.xz 8c308501aa7620273c5e6f1e37db20a1c350ed9c 450228 phppgadmin_5.1+ds-3_all.deb 1a0b0e34cda431c778fd74669460f2567d212e3f 5967 phppgadmin_5.1+ds-3_amd64.buildinfo Checksums-Sha256: 8a2b6d37d9ea350a5aa11cc55f29126ad20947f8c75a3bf8b27d21b6ec9be0a2 2022 phppgadmin_5.1+ds-3.dsc 42cc5bf1c4b54a71d0fe2e00aad43d31a8134ee00cec73815a18f8762806c191 11908 phppgadmin_5.1+ds-3.debian.tar.xz 6277d8ec43e6c88944c81f7af0662ee0570be4113970092c3b087c4e7830db97 450228 phppgadmin_5.1+ds-3_all.deb 3779c43a09f7663a493d9806546687d001140ec79974d7d94cfbbec961af24e2 5967 phppgadmin_5.1+ds-3_amd64.buildinfo Files: b44dde2e3ff3a1dc1425abcc39ee150f 2022 web optional phppgadmin_5.1+ds-3.dsc dd72fa0a7f620b621ece8fa6bd37f6cc 11908 web optional phppgadmin_5.1+ds-3.debian.tar.xz 98813284c80adea945cd85533a5526ab 450228 web optional phppgadmin_5.1+ds-3_all.deb a8fe137a17c953bb9659cf8dfdae0f5a 5967 web optional phppgadmin_5.1+ds-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEEQIMD57NJdABlZVMrO1wscaIY2DwFAlqEor8SHG5pcmdhbEBk ZWJpYW4ub3JnAAoJEDtcLHGiGNg8vk8P/R8rwJPonE2SfekQ3sNEaiQVOCyfvwpo dyFTJd1s36b4Wm5UyD0k0LjUyfJQv3MOzCqvALg3hmohDJNBt8T2d4Hj7Of63U1+ joZRsLcJVdyN18NQTfipMcq3BAA4FgLGLwjQ
[Pkg-postgresql-public] Processed: severity of 888446 is important
Processing commands for cont...@bugs.debian.org: > severity 888446 important Bug #888446 [phppgadmin] phppgadmin - Connection fail with postgreSQL 10 Severity set to 'important' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 888446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888446 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#803574: marked as done (When you close 'edit data' window, pgadmin3 freezes)
Your message dated Mon, 12 Feb 2018 20:15:43 +0100 with message-id <20180212191543.ga24...@msg.df7cb.de> and subject line Re: Bug#803574: When you close 'edit data' window, pgadmin3 freezes has caused the Debian Bug report #803574, regarding When you close 'edit data' window, pgadmin3 freezes 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.) -- 803574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pgadmin3 Version: 1.20.0~beta2-1 Severity: important Dear maintainer, Whene I close 'edit data' window after to have edit some datas, sometimes pgadmin3 freezes. Here are the pgadmin3 backtrace provided by himself and gdb backtrace. Thank you very much. Best regards Denis Briand -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pgadmin3 depends on: ii libc6 2.19-18+deb8u1 ii libgcc1 1:4.9.2-10 ii libkrb5-3 1.12.1+dfsg-19 ii libpq5 9.4.5-0+deb8u1 ii libssl1.0.0 1.0.1k-3+deb8u1 ii libstdc++6 4.9.2-10 ii libwxbase3.0-0 3.0.2-1+b1 ii libwxgtk3.0-0 3.0.2-1+b1 ii libxml2 2.9.1+dfsg1-5 ii libxslt1.1 1.1.28-2+b2 ii pgadmin3-data 1.20.0~beta2-1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages pgadmin3 recommends: ii pgagent3.4.0-3 ii postgresql-client-9.4 [postgresql-client] 9.4.5-0+deb8u1 Versions of packages pgadmin3 suggests: pn postgresql-contrib -- no debconf information ASSERT INFO: ../src/common/wincmn.cpp(478): assert "GetEventHandler() == this" failed in ~wxWindowBase(): any pushed event handlers must have been removed BACKTRACE: [1] wxWindowBase::~wxWindowBase() [2] wxWindow::~wxWindow() [3] wxControlBase::~wxControlBase() [4] wxStyledTextCtrl::~wxStyledTextCtrl() [5] wxStyledTextCtrl::~wxStyledTextCtrl() [6] wxWindowBase::Destroy() [7] wxWindowBase::DestroyChildren() [8] wxWindow::~wxWindow() [9] wxGridWindow::~wxGridWindow() [10] wxWindowBase::Destroy() [11] wxWindowBase::DestroyChildren() [12] wxWindow::~wxWindow() [13] wxListEvent::~wxListEvent() [14] wxWindowBase::Destroy() [15] wxWindowBase::DestroyChildren() [16] wxWindow::~wxWindow() [17] wxTopLevelWindowGTK::~wxTopLevelWindowGTK() [18] wxFrameBase::~wxFrameBase() [19] non-virtual thunk to wxBookCtrlBase::~wxBookCtrlBase() [20] wxListEvent::~wxListEvent() [21] wxListEvent::~wxListEvent() [22] wxAppConsoleBase::DeletePendingObjects() [23] wxAppConsoleBase::ProcessIdle() [24] wxAppBase::ProcessIdle() [25] wxApp::DoIdle() [26] g_main_context_dispatch [27] g_main_loop_run [28] gtk_main [29] wxGUIEventLoop::DoRun() [30] wxEventLoopBase::Run() [31] wxAppConsoleBase::MainLoop() [32] wxEntry(int&, wchar_t**) [33] __libc_start_main #0 0x73f1779b in raise (sig=5) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37 #1 0x76317b80 in wxGUIAppTraits::ShowAssertDialog(wxString const&) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0 #2 0x757a9a22 in ?? () from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #3 0x757a9de0 in wxAppConsoleBase::OnAssertFailure(wchar_t const*, int, wchar_t const*, wchar_t const*, wchar_t const*) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #4 0x762d67c0 in wxApp::OnAssertFailure(wchar_t const*, int, wchar_t const*, wchar_t const*, wchar_t const*) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0 #5 0x757aa1bb in ?? () from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #6 0x757a5be1 in wxOnAssert(char const*, int, char const*, char const*, wchar_t const*) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #7 0x76539df4 in wxWindowBase::~wxWindowBase() () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0 #8 0x7631d248 in wxWindow::~wxWindow() () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0 #9 0x764025ae in wxControlBase::~wxControlBase() () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0 #10 0x776f6692 in wxStyledTextCtrl::~wxStyledTextCtrl() () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_stc-3.0.so.0 #11 0x776f6809 in wxStyledTextCtrl::~wxStyledTextCtrl() () from /
[Pkg-postgresql-public] Bug#605817: marked as done (pgadmin3: When a connection is lost, pgadmin blanks)
Your message dated Mon, 12 Feb 2018 20:10:19 +0100 with message-id <20180212191019.ga23...@msg.df7cb.de> and subject line Re: Bug#605817: pgadmin3: When a connection is lost, pgadmin blanks has caused the Debian Bug report #605817, regarding pgadmin3: When a connection is lost, pgadmin blanks 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.) -- 605817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pgadmin3 Version: 1.10.0-1+b2 Severity: grave Justification: causes non-serious data loss pgadmin3 is unusable when the connection to one or more databases is lost. The window of pgadmin3 do not show anything, so it is impossible to save a query or do anything. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages pgadmin3 depends on: ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.4-1GCC support library ii libkrb5-3 1.8.1+dfsg-3 MIT Kerberos runtime libraries ii libpq5 8.4.1-1 PostgreSQL C client library ii libstdc++6 4.4.4-1 The GNU Standard C++ Library v3 ii libwxbase2.8-0 2.8.10.1-3 wxBase library (runtime) - non-GUI ii libwxgtk2.8-0 2.8.10.1-3 wxWidgets Cross-platform C++ GUI t ii libxml2 2.7.6.dfsg-1 GNOME XML library ii libxslt1.1 1.1.26-1 XSLT processing library - runtime ii pgadmin3-data 1.10.0-1 graphical administration tool for Versions of packages pgadmin3 recommends: ii pgagent 3.0.1-1job scheduler for PostgreSQL ii postgresql-client-8.3 [postgr 8.3.8-1front-end programs for PostgreSQL pgadmin3 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Re: Sergio Cuellar Valdes 2010-12-03 <20101203185109.11639.8.report...@einsamkeit.traurigkeit.org> > Package: pgadmin3 > Version: 1.10.0-1+b2 > Severity: grave > Justification: causes non-serious data loss > > pgadmin3 is unusable when the connection to one or more databases is > lost. > > The window of pgadmin3 do not show anything, so it is impossible to save > a query or do anything. I've given this another try - it reacts smoothly to connection aborts. I guess there's still a problem if the remote server doesn't answer at all and it's running into timeouts, but that's likely a problem with many networking application. Given that pgadmin3 won't be seeing any new upstream releases, I'm closing this Debian bug now. Christoph--- End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#364784: marked as done (pgadmin3: selecting datatype in when creating new columns is very uncomfortable)
Your message dated Mon, 12 Feb 2018 20:05:51 +0100 with message-id <20180212190551.ga23...@msg.df7cb.de> and subject line Re: Bug#364784: pgadmin3: selecting datatype in when creating new columns is very uncomfortable has caused the Debian Bug report #364784, regarding pgadmin3: selecting datatype in when creating new columns is very uncomfortable 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.) -- 364784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pgadmin3 Version: 1.4.2-1 Severity: normal When selecting data type for new column. We have "combo-box" here with all data types listed in some random order (at least it is not alphavetical). It will be fine If I could enter first letters to jump to desired datatype. Right now usualy I have to read all list of datatypes to find the one I need. It's even easier to do it in command line tools. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686 Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2) Versions of packages pgadmin3 depends on: ii libc6 2.3.6-7 GNU C Library: Shared libraries ii libgcc1 1:4.1.0-1+b1 GCC support library ii libpq4 8.1.3-4 PostgreSQL C client library ii libstdc++6 4.1.0-1+b1 The GNU Standard C++ Library v3 ii libwxgtk2.6-0 2.6.1.2-0.1 wxWidgets Cross-platform C++ GUI t ii pgadmin3-data 1.4.2-1 Graphical administration tool for pgadmin3 recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Re: Emil Nowak 2006-04-25 <20060425172026.29997.1160.reportbug@galeon> > Package: pgadmin3 > Version: 1.4.2-1 > Severity: normal > > When selecting data type for new column. We have "combo-box" here with all > data types listed in some random order (at least it is not alphavetical). > It will be fine If I could enter first letters to jump to desired datatype. > Right now usualy I have to read all list of datatypes to find the one I need. > > It's even easier to do it in command line tools. Hi, since there won't be any new pgadmin3 releases from upstream, I'm closing this Debian bug now. Christoph--- End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#797804: marked as done (pgadmin3 segfaults after rightclick)
Your message dated Mon, 12 Feb 2018 20:03:49 +0100 with message-id <20180212190349.ga23...@msg.df7cb.de> and subject line Re: Bug#797804: pgadmin3 segfault while connecting has caused the Debian Bug report #797804, regarding pgadmin3 segfaults after rightclick 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.) -- 797804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pgadmin3 Version: 1.20.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** I tried to manage a local postgres installation but when trying to add a new server pgadmin3 closes after segfaulting. Message: $> Debug: Adding duplicate image handler for 'PNG file' I found nearly the same bug description last year but it seems that the bug returned. I use a fully upgraded debian testing environment but when the bug appeared I even upgraded pgadmin3 to experimental. This didn't help either. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pgadmin3 depends on: ii libc6 2.19-19 ii libgcc1 1:5.1.1-14 ii libpq5 9.4.4-1 ii libssl1.0.0 1.0.2d-1 ii libstdc++6 5.1.1-14 ii libwxbase3.0-0 3.0.2+dfsg-1 ii libwxgtk3.0-0 3.0.2+dfsg-1 ii libxml2 2.9.1+dfsg1-5 ii libxslt1.1 1.1.28-2+b2 ii pgadmin3-data 1.20.0-1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages pgadmin3 recommends: ii pgagent3.4.0-3 ii postgresql-client-9.4 [postgresql-client] 9.4.4-1 Versions of packages pgadmin3 suggests: pn postgresql-contrib -- no debconf information --- End Message --- --- Begin Message --- Version: 1.22.1-1 Re: To Stefan Krueger 2016-04-16 <20160416212552.ga8...@msg.df7cb.de> > Re: Stefan Krueger 2016-04-15 > <trinity-7cfe982c-81ec-4598-af03-0125834759ed-1460702991510@3capp-gmx-bs30> > > Hi, > > > > the version 1.22.1-1.pgdg80+1 seems to work. > > Hi, > > thanks for the confirmation. > > I've uploaded that version to jessie-backports so it is available > there as well. Closing this bug, finally. Christoph--- End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#668924: marked as done (pgadmin3: Lost characters when typing query)
Your message dated Mon, 12 Feb 2018 19:57:19 +0100 with message-id <20180212185719.ga22...@msg.df7cb.de> and subject line Re: Bug#668924: pgadmin3: Lost characters when typing query has caused the Debian Bug report #668924, regarding pgadmin3: Lost characters when typing query 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.) -- 668924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pgadmin3 Version: 1.14.0-2 Hi, It seems that while I'm typing a query, alot of the characters I type get lost. I have reported this *years* ago, and then it seems the problem went away, now it's back. Kurt --- End Message --- --- Begin Message --- Re: Kurt Roeckx 2016-01-17 <20160117112145.ga8...@roeckx.be> > > Since 2012, can you reproduce it with the new version? > > I can't reproduce it with 1.20.0-3+b1. Since I'm having this > problems for a long time and that it goes away and comes back, I > don't beleve this is fixed. Hi, pgadmin3 development has ceased upstream, so if there's any bug in pgadmin3 here, it's unlikely to get fixed. (Though this sounds more like a toolkit issue.) Christoph--- End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#750558: marked as done (pgadmin3 does support ssh jumps, but does not support ssh-agent )
Your message dated Mon, 12 Feb 2018 19:54:33 +0100 with message-id <20180212185433.ga22...@msg.df7cb.de> and subject line Re: Bug#750558: pgadmin3 does support ssh jumps, but does not support ssh-agent has caused the Debian Bug report #750558, regarding pgadmin3 does support ssh jumps, but does not support ssh-agent 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.) -- 750558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pgadmin3 Version: 1.18.1-3 Severity: wishlist Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pgadmin3 depends on: ii libc6 2.18-7 ii libgcc1 1:4.9.0-5 ii libkrb5-3 1.12.1+dfsg-1 ii libpq5 9.3.4-1+b1 ii libssl1.0.0 1.0.1g-4 ii libstdc++6 4.9.0-5 ii libwxbase3.0-0 3.0.0-4 ii libwxgtk3.0-0 3.0.0-4 ii libxml2 2.9.1+dfsg1-3 ii libxslt1.1 1.1.28-2 ii pgadmin3-data 1.18.1-3 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages pgadmin3 recommends: pn pgagent ii postgresql-client-9.3 [postgresql-client] 9.3.4-1+b1 Versions of packages pgadmin3 suggests: ii postgresql-contrib 9.3+155 -- no debconf information --- End Message --- --- Begin Message --- Re: bmorel 2014-06-04 <20140604132753.9893.88746.reportbug@D2SI-P07-2.D2SI> > Package: pgadmin3 > Version: 1.18.1-3 > Severity: wishlist > Tags: upstream pgadmin3 isn't developed anymore upstream, so I'm closing this wishlist bug now. Christoph--- End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#888421: marked as done (pgadmin3: not supporting pgsql server 10, error reading postgres db)
Your message dated Sun, 11 Feb 2018 21:26:38 + with message-id <e1ekz8w-0007uu...@fasolo.debian.org> and subject line Bug#888421: fixed in pgadmin3 1.22.2-4 has caused the Debian Bug report #888421, regarding pgadmin3: not supporting pgsql server 10, error reading postgres db 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.) -- 888421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pgadmin3 Version: 1.22.2-3 Severity: important Tags: upstream pgadmin3: not supporting pgsql server 10. ~ WARNING: 12:10:35: Warning: The server you are connecting to is not a version that is supported by this release of pgAdmin III. pgAdmin III may not function as expected. Supported server versions are 8.4 to 9.6. QUERY : 12:10:38: Set query (localhost:5432): SELECT usecreatedb, usesuper, CASE WHEN usesuper THEN pg_postmaster_start_time() ELSE NULL END as upsince, CASE WHEN usesuper THEN pg_conf_load_time() ELSE NULL END as confloadedsince, CASE WHEN usesuper THEN pg_is_in_recovery() ELSE NULL END as inrecovery, CASE WHEN usesuper THEN pg_last_xlog_receive_location() ELSE NULL END as receiveloc, CASE WHEN usesuper THEN pg_last_xlog_replay_location() ELSE NULL END as replayloc, CASE WHEN usesuper THEN pg_last_xact_replay_timestamp() ELSE NULL END as replay_timestamp, CASE WHEN usesuper AND pg_is_in_recovery() THEN pg_is_xlog_replay_paused() ELSE NULL END as isreplaypaused FROM pg_user WHERE usename=current_user ERROR : 12:10:38: Error: ERROR: function pg_last_xlog_receive_location() does not exist LINE 1: ...E NULL END as inrecovery, CASE WHEN usesuper THEN pg_last_xl... ^ HINT: No function matches the given name and argument types. You might need to add explicit type casts. ERROR : 12:10:40: Error: Column not found in pgSet: usecreatedb ERROR : 12:12:08: Error: Column not found in pgSet: usesuper ERROR : 12:12:10: Error: Column not found in pgSet: upsince ERROR : 12:12:10: Error: Column not found in pgSet: confloadedsince ERROR : 12:12:11: Error: Column not found in pgSet: inrecovery ERROR : 12:12:11: Error: Column not found in pgSet: replayloc ERROR : 12:12:11: Error: Column not found in pgSet: receiveloc ERROR : 12:12:11: Error: Column not found in pgSet: replay_timestamp ERROR : 12:12:11: Error: Column not found in pgSet: isreplaypaused assertion fail: ~ ASSERT INFO: db/pgSet.cpp(284): assert "col < nCols && col >= 0" failed in GetBool(). BACKTRACE: [1] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) [2] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) [3] wxEvtHandler::TryHereOnly(wxEvent&) [4] wxEvtHandler::DoTryChain(wxEvent&) [5] wxEvtHandler::ProcessEvent(wxEvent&) [6] wxWindowBase::TryAfter(wxEvent&) [7] wxScrollHelperEvtHandler::ProcessEvent(wxEvent&) [8] wxGenericTreeCtrl::OnChar(wxKeyEvent&) [9] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) [10] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) [11] wxEvtHandler::TryHereOnly(wxEvent&) [12] wxEvtHandler::ProcessEventLocally(wxEvent&) [13] wxEvtHandler::ProcessEvent(wxEvent&) [14] wxScrollHelperEvtHandler::ProcessEvent(wxEvent&) [15] wxEvtHandler::SafelyProcessEvent(wxEvent&) [16] g_closure_invoke [17] g_signal_emit_valist [18] g_signal_emit [19] gtk_window_propagate_key_event [20] g_closure_invoke [21] g_signal_emit_valist [22] g_signal_emit [23] gtk_propagate_event [24] gtk_main_do_event [25] g_main_context_dispatch [26] g_main_loop_run [27] gtk_main [28] wxGUIEventLoop::DoRun() [29] wxEventLoopBase::Run() [30] wxAppConsoleBase::MainLoop() [31] wxEntry(int&, wchar_t**) [32] __libc_start_main log files added as attachment ... -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE=nl (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pgadmin3 depends on: ii libc6 2.26-4 ii libgcc1 1:7.2.0-19 ii libgcrypt20 1.8.1-4 ii libpq510.1-3 ii libstdc++67.2.0-19 ii libwxbase3
[Pkg-postgresql-public] Bug#878295: marked as done (pgadmin3 changes for PG10)
Your message dated Sun, 11 Feb 2018 21:26:38 +
with message-id <e1ekz8w-0007uo...@fasolo.debian.org>
and subject line Bug#878295: fixed in pgadmin3 1.22.2-4
has caused the Debian Bug report #878295,
regarding pgadmin3 changes for PG10
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.)
--
878295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pgadmin3
Version: 1.22.2-1
- Forwarded message from Bernhard Rieder <bernh...@ratte.cc> -
Date: Wed, 11 Oct 2017 16:10:53 +0200
From: Bernhard Rieder <bernh...@ratte.cc>
To: christoph.b...@credativ.de
Subject: pgadmin3 anpassungen für PG10
diff -ur pgadmin3-1.22.2/pgadmin/include/pgAdmin3.h pgadmin3-1.22.2-PG10/pgadmin/include/pgAdmin3.h
--- pgadmin3-1.22.2/pgadmin/include/pgAdmin3.h 2016-11-10 15:13:28.0 +0100
+++ pgadmin3-1.22.2-PG10/pgadmin/include/pgAdmin3.h 2017-10-11 14:40:38.835409091 +0200
@@ -58,8 +58,8 @@
// Supported server minimum and maximum values.
const short SERVER_MIN_VERSION_N = 0x0804;
const wxString SERVER_MIN_VERSION_T = wxT("8.4");
-const short SERVER_MAX_VERSION_N = 0x0906;
-const wxString SERVER_MAX_VERSION_T = wxT("9.6");
+const short SERVER_MAX_VERSION_N = 0x0A00;
+const wxString SERVER_MAX_VERSION_T = wxT("10.0");
// Supported Greenplum Database and Greenplum HAWQ minimum and maximum values.
const short GP_MIN_VERSION_N = 0x0802;
diff -ur pgadmin3-1.22.2/pgadmin/schema/pgServer.cpp pgadmin3-1.22.2-PG10/pgadmin/schema/pgServer.cpp
--- pgadmin3-1.22.2/pgadmin/schema/pgServer.cpp 2016-02-08 11:25:13.0 +0100
+++ pgadmin3-1.22.2-PG10/pgadmin/schema/pgServer.cpp 2017-10-11 14:55:57.274751845 +0200
@@ -905,13 +905,24 @@
if (conn->BackendMinimumVersion(8, 5))
{
sql += wxT(", CASE WHEN usesuper THEN pg_is_in_recovery() ELSE NULL END as inrecovery");
- sql += wxT(", CASE WHEN usesuper THEN pg_last_xlog_receive_location() ELSE NULL END as receiveloc");
- sql += wxT(", CASE WHEN usesuper THEN pg_last_xlog_replay_location() ELSE NULL END as replayloc");
+ if (conn->BackendMinimumVersion(10, 0))
+ {
+sql += wxT(", CASE WHEN usesuper THEN pg_last_wal_receive_lsn() ELSE NULL END as receiveloc");
+sql += wxT(", CASE WHEN usesuper THEN pg_last_wal_replay_lsn() ELSE NULL END as replayloc");
+ }
+ else
+ {
+ sql += wxT(", CASE WHEN usesuper THEN pg_last_xlog_receive_location() ELSE NULL END as receiveloc");
+ sql += wxT(", CASE WHEN usesuper THEN pg_last_xlog_replay_location() ELSE NULL END as replayloc");
+ }
}
if (conn->BackendMinimumVersion(9, 1))
{
sql += wxT(", CASE WHEN usesuper THEN pg_last_xact_replay_timestamp() ELSE NULL END as replay_timestamp");
- sql += wxT(", CASE WHEN usesuper AND pg_is_in_recovery() THEN pg_is_xlog_replay_paused() ELSE NULL END as isreplaypaused");
+ if (conn->BackendMinimumVersion(10, 0))
+sql += wxT(", CASE WHEN usesuper AND pg_is_in_recovery() THEN pg_is_wal_replay_paused() ELSE NULL END as isreplaypaused");
+ else
+ sql += wxT(", CASE WHEN usesuper AND pg_is_in_recovery() THEN pg_is_xlog_replay_paused() ELSE NULL END as isreplaypaused");
}
pgSet *set = ExecuteSet(sql + wxT("\n FROM pg_user WHERE usename=current_user"));
@@ -1434,7 +1445,11 @@
bool pgServer::PauseReplay()
{
SetReplayPaused(true);
- wxString sql = wxT("SELECT pg_xlog_replay_pause()");
+ wxString sql;
+ if (conn->BackendMinimumVersion(10, 0))
+ sql = wxT("SELECT pg_wal_replay_pause()");
+ else
+ sql = wxT("SELECT pg_xlog_replay_pause()");
return conn->ExecuteVoid(sql);
}
@@ -1442,7 +1457,11 @@
bool pgServer::ResumeReplay()
{
SetReplayPaused(false);
- wxString sql = wxT("SELECT pg_xlog_replay_resume()");
+ wxString sql;
+ if (conn->BackendMinimumVersion(10, 0))
+ sql = wxT("SELECT pg_wal_replay_resume()");
+ else
+ sql = wxT("SELECT pg_xlog_replay_resume()");
return conn->ExecuteVoid(sql);
}
--- End Message ---
--- Begin Message ---
Source: pgadmin3
Source-Version: 1.22.2-4
We believe that the bug you reported is fixed in the latest version of
pgadmin3, 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 furthe
[Pkg-postgresql-public] Bug#887251: marked as done (postgresql-common should depend on e2fsprogs explicitly)
Your message dated Thu, 08 Feb 2018 13:27:55 + with message-id <e1ejmf1-000bop...@fasolo.debian.org> and subject line Bug#887251: fixed in postgresql-common 190 has caused the Debian Bug report #887251, regarding postgresql-common should depend on e2fsprogs explicitly 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.) -- 887251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: postgresql-common Version: 189 User: helm...@debian.org Usertags: nonessentiale2fsprogs Dear maintainer, We want to make removing e2fsprogs from installations possible. For standard installations this is not useful, but embedded applications and chroots benefit from such an option. For getting there all packages that use e2fsprogs must be identified and gain a dependency on it as e2fsprogs currently is essential. postgresql-common was identified as potentially needing such a dependency, because it mentions tool names from e2fsprogs in the following files: /usr/bin/pg_createcluster contains chattr. According to file it is a Perl script text executable Please investigate whether these cases are actually uses of a tool from e2fsprogs. Care has been taken to shrink the number of candidates as much as possible, but a few false positives will remain. After doing so, do one of the following: * Add e2fsprogs to Depends. * Add e2fsprogs to Recommends. * Close this bug explaining why e2fsprogs is not used by this package. Once e2fsprogs drops the "Essential: yes" flag, this bug will be upgraded to RC severity. Please note that lintian will warn about such a dependency before lintian 2.5.56. Thanks for your help Helmut --- End Message --- --- Begin Message --- Source: postgresql-common Source-Version: 190 We believe that the bug you reported is fixed in the latest version of postgresql-common, 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 887...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg <christoph.b...@credativ.de> (supplier of updated postgresql-common 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: Thu, 08 Feb 2018 13:26:44 +0100 Source: postgresql-common Binary: postgresql-common postgresql-client-common postgresql-server-dev-all postgresql postgresql-client postgresql-doc postgresql-contrib postgresql-all Architecture: source Version: 190 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public@lists.alioth.debian.org> Changed-By: Christoph Berg <christoph.b...@credativ.de> Description: postgresql - object-relational SQL database (supported version) postgresql-all - metapackage depending on all PostgreSQL server packages postgresql-client - front-end programs for PostgreSQL (supported version) postgresql-client-common - manager for multiple PostgreSQL client versions postgresql-common - PostgreSQL database-cluster manager postgresql-contrib - additional facilities for PostgreSQL (supported version) postgresql-doc - documentation for the PostgreSQL database management system postgresql-server-dev-all - extension build tool for multiple PostgreSQL versions Closes: 887251 Changes: postgresql-common (190) unstable; urgency=medium . * Move packaging repository to salsa.debian.org * pg_lsclusters: Add --help. * pg_virtualenv: Error out if no server packages are installed. * postgresql-common recommends e2fsprogs, we are using chattr in pg_createcluster. (Closes: #887251) * PgCommon.pm: Fix include directives parser, spotted by ironhalik, thanks! * postgresql@.service: Set Timeoutstart=0, which is the same as infinity, but works on older systemd versions as well. * Rewrite architecture.html as README.md. * t/006_next_free_port.t: Drop -q argument from netcat, nmap-ncat.rpm doesn't have it. * t/032_ssl_key_permissions.t: Adjust for 9.4 in oldstable which still has the old permissions check. Checksums-Sha1: 8de735103c4fe7dd0c0b293a40a673b1bbb1c9f6 2320 postgresql-common_190.dsc 521a1729e77c0
[Pkg-postgresql-public] Processed (with 1 error): block 882409 with 710275
Processing commands for cont...@bugs.debian.org: > block 882409 with 710275 Bug #882409 [postgresql-9.4] postgresql-9.4: jessie->wheezy on amd64: psql: FATAL: Peer authentication failed for user "postgres" 882409 was not blocked by any bugs. 882409 was not blocking any bugs. Added blocking bug(s) of 882409: 710275 Failed to set blocking bugs of 882409: can't find location for 710275. > thanks Stopping processing here. Please contact me if you need assistance. -- Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: reassign 884457 to postgresql-client-common
Processing commands for cont...@bugs.debian.org: > reassign 884457 postgresql-client-common Bug #884457 [postgresql-client-9.6] post-install failure when /usr/share/man/man1/ does not exist Bug reassigned from package 'postgresql-client-9.6' to 'postgresql-client-common'. No longer marked as found in versions postgresql-9.6/9.6.6-0+deb9u1. Ignoring request to alter fixed versions of bug #884457 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 884457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#888755: marked as done (postgresql-common: pg_upgradecluster should call psql with -X)
Your message dated Tue, 30 Jan 2018 12:06:22 +0100 with message-id <20180130110622.ga31...@msg.df7cb.de> and subject line Re: Bug#888755: postgresql-common: pg_upgradecluster should call psql with -X has caused the Debian Bug report #888755, regarding postgresql-common: pg_upgradecluster should call psql with -X 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.) -- 888755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888755 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: postgresql-common Version: 181+deb9u1 Severity: normal Dear Maintainer, When I upgraded a box (that's heavily firewalled, so running reportbug on it doesn't work, so I'm writing this from another box, I'll try to make sure the automatically inserted information reflects the box I had the problem on) from Jessie to Stretch, I also got postgresql 9.6 instead of (or technically in addition to) the 9.4 that was in Jessie, and was told to run pg_upgradecluster to upgrade the databases. That failed with some messages about trying to run "CREATE DATABASE" inside a transaction. After a while and some timme searching the net, I realised that it might be due to me having "\set AUTOCOMMIT off" in /etc/postgresql-common/psqlrc, and adding a -X to every call of psql in pg_upgradecluster did indeed fix the problem and allowed me to upgrade my databases. Most things you'd ever find in a psqlrc is related to interactive use, so just not reading it should be a lot better than the current behaviour. -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages postgresql-common depends on: ii adduser 3.115 ii debconf [debconf-2.0] 1.5.61 ii init-system-helpers 1.48 ii lsb-base 9.20161125 ii postgresql-client-common 181+deb9u1 ii procps2:3.3.12-3 ii ssl-cert 1.0.39 ii ucf 3.0036 Versions of packages postgresql-common recommends: ii logrotate 3.11.0-0.1 postgresql-common suggests no packages. --- End Message --- --- Begin Message --- Version: 187 Re: Henrik Christian Grove 2018-01-29 <20180129145413.19889.61183.reportbug@solitaire.grove> > That failed with some messages about trying to run "CREATE DATABASE" > inside a transaction. After a while and some timme searching the net, I > realised that it might be due to me having "\set AUTOCOMMIT off" in > /etc/postgresql-common/psqlrc, and adding a -X to every call of psql in > pg_upgradecluster did indeed fix the problem and allowed me to upgrade > my databases. Hi Henrik, this has already been fixed in postgresql-common version 187. Thanks for the report! Christoph--- End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: Re: Bug#887251: postgresql-common should depend on e2fsprogs explicitly
Processing control commands: > tags -1 + pending Bug #887251 [postgresql-common] postgresql-common should depend on e2fsprogs explicitly Ignoring request to alter tags of bug #887251 to the same tags previously set -- 887251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: limit source to postgresql-common, tagging 887251
Processing commands for cont...@bugs.debian.org: > limit source postgresql-common Limiting to bugs with field 'source' containing at least one of 'postgresql-common' Limit currently set to 'source':'postgresql-common' > tags 887251 + pending Bug #887251 [postgresql-common] postgresql-common should depend on e2fsprogs explicitly Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 887251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: Re: Bug#887940: Bug#887940: libpq-dev: changed version format in pg_config causes other packages to FTBFS
Processing control commands: > reassign -1 src:libpreludedb Bug #887940 [libpq-dev] libpq-dev: changed version format in pg_config causes other packages to FTBFS Bug reassigned from package 'libpq-dev' to 'src:libpreludedb'. No longer marked as found in versions postgresql-10/10.1-3. Ignoring request to alter fixed versions of bug #887940 to the same values previously set -- 887940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: libpq-dev: changed version format in pg_config causes other packages to FTBFS
Processing control commands: > affects -1 src:libpreludedb Bug #887940 [libpq-dev] libpq-dev: changed version format in pg_config causes other packages to FTBFS Added indication that 887940 affects src:libpreludedb -- 887940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#723847: marked as done (postgresql-9.3: server - pg_upgradecluster - initdb: --data-checksums ?)
Your message dated Fri, 12 Jan 2018 14:02:09 +0100 with message-id <20180112130209.ga10...@msg.df7cb.de> and subject line Re: Bug#723847: [Pkg-postgresql-public] Bug#723847: Bug#723847: postgresql-9.3: server - pg_upgradecluster - initdb: --data-checksums ? has caused the Debian Bug report #723847, regarding postgresql-9.3: server - pg_upgradecluster - initdb: --data-checksums ? 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.) -- 723847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: postgresql-9.3 Version: 9.3~rc1-2 Severity: wishlist I wonder whether --data-checksums / -k can be made the default for creating new clusters starting with PG 9.3. If not it'd still be good to capture the rationale for that decision. I am aware of /etc/postgresql-common/createcluster.conf -> initdb_options and that has worked nicely for me. Karsten -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'stable'), (50, 'unstable'), (10, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.10-2-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages postgresql-9.3 depends on: ii libc6 2.17-92+b1 ii libcomerr2 1.42.8-1 ii libgssapi-krb5-2 1.11.3+dfsg-3 ii libkrb5-3 1.11.3+dfsg-3 ii libldap-2.4-2 2.4.31-1+nmu2+b1 ii libpam0g 1.1.3-9 ii libpq5 9.3~rc1-2 ii libssl1.0.01.0.1e-3 ii libxml22.9.1+dfsg1-3 ii locales2.17-92 ii locales-all [locales] 2.17-92+b1 ii postgresql-client-9.3 9.3~rc1-2 ii postgresql-common 149 ii ssl-cert 1.0.33 ii tzdata 2013d-1 postgresql-9.3 recommends no packages. Versions of packages postgresql-9.3 suggests: ii locales-all 2.17-92+b1 pn oidentd | ident-server -- no debconf information --- End Message --- --- Begin Message --- Re: Peter Eisentraut 2013-10-16 <1381893307.17199.4.ca...@vanquo.pezone.net> > On Sat, 2013-10-12 at 11:09 +0200, Karsten Hilbert wrote: > > So, to rephrase the question: I wonder whether --data-checksums > > can be pre-set in /etc/postgresql-common/createcluster.conf's > > "initdb_options" ? > > It doesn't matter where you attach the option, the answer is the same: > Upstream has decided that checksums should not be the default at this > time. If you want to override that for the entire world of Debian, you > need to come up with a good reason. Hi, 4 years later the answer here is still what Peter said, we won't change the default in Debian from upstream's default. I'll close the wishlist bug now. Christoph--- End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: Re: pg_upgradecluster should use fast shutdown
Processing control commands: > found -1 181+deb9u1 Bug #756008 [postgresql-common] pg_upgradecluster should use fast shutdown Marked as found in versions postgresql-common/181+deb9u1. -- 756008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#881501: marked as done (postgresql-common: Please recognize Ubuntu 18.04 as a supported version)
Your message dated Thu, 14 Dec 2017 20:55:43 + with message-id <e1epaxf-0007gx...@fasolo.debian.org> and subject line Bug#881501: fixed in postgresql-common 189 has caused the Debian Bug report #881501, regarding postgresql-common: Please recognize Ubuntu 18.04 as a supported version 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.) -- 881501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: postgresql-common Version: 188 Severity: important slony1-2's autopkgtests are failing on Ubuntu 18.04 "bionic" because 18.04 is not listed as in debian/supported-versions. Ubuntu developers currently plan to target postgresql-10 for 18.04 LTS. http://autopkgtest.ubuntu.com/packages/s/slony1-2/bionic/amd64 Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- Source: postgresql-common Source-Version: 189 We believe that the bug you reported is fixed in the latest version of postgresql-common, 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 881...@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-common 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: Thu, 14 Dec 2017 21:13:24 +0100 Source: postgresql-common Binary: postgresql-common postgresql-client-common postgresql-server-dev-all postgresql postgresql-client postgresql-doc postgresql-contrib postgresql-all Architecture: source Version: 189 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public@lists.alioth.debian.org> Changed-By: Christoph Berg <m...@debian.org> Description: postgresql - object-relational SQL database (supported version) postgresql-all - metapackage depending on all PostgreSQL server packages postgresql-client - front-end programs for PostgreSQL (supported version) postgresql-client-common - manager for multiple PostgreSQL client versions postgresql-common - PostgreSQL database-cluster manager postgresql-contrib - additional facilities for PostgreSQL (supported version) postgresql-doc - documentation for the PostgreSQL database management system postgresql-server-dev-all - extension build tool for multiple PostgreSQL versions Closes: 876438 881501 Changes: postgresql-common (189) unstable; urgency=medium . [ Chris Lamb ] * Update README.Debian for postgresql-10. (Closes: #876438) . [ Christoph Berg ] * dh_make_pgxs: Use PostgreSQL license as default, fix extension name. * Modernize README.Debian's version numbers and SSL instructions. * postgresql@.service: Ignore startup failure, recovery might take arbitrarily long to finish. The actual service status still correctly reflects if the postmaster process is running. https://www.postgresql.org/message-id/2017205316.u56lkmkakdmcx6zm%40msg.df7cb.de * supported-versions: Version 10 on Ubuntu 18.04 (bionic). (Closes: #881501) * debian/maintscripts-functions: bump update-alternatives priority of version 1x to 1x0. * Unsupport 9.2 on apt.postgresql.org. * t/140_pg_config.t: Also test /usr/bin/pg_config.libpq-dev, and check MKDIR_P and abs_top_build/srcdir in Makefile.global. Checksums-Sha1: f2ae71ef1570bc1312967fd3244d9d3da6c0df61 2339 postgresql-common_189.dsc 424339366b610c06ef4f4cc96f07cce24c0678e7 206908 postgresql-common_189.tar.xz fa3a5efe9c0407a2c0cb0e12ab460c5f8206da1d 5773 postgresql-common_189_source.buildinfo Checksums-Sha256: d5036f8efded708bf65cb5bdd191ebaff0afd9698023bc2572e6e2317e6558cb 2339 postgresql-common_189.dsc a0203ed9c8901f893abc38dff50c5b9aa50c8337b35fb3de001afcc335bdef9a 206908 postgresql-common_189.tar.xz f0a892b4c84b74ffcd3acd2d4b0a0f22acdd5c36c57d371f20e957b0d687d148 5773 postgresql-common_189_source.buildinfo Files: 005c212e0f4589da25d71c475426125d 2339 database optional postgresql-common_189.dsc 0a2cc39265849b19f0f1d2e91dff1911 206908 database optional postgresql-common_189.tar.xz f6b57ac73bd24f429e2de6e49ac93a2c 5773 database optional postgresql-common_18
[Pkg-postgresql-public] Bug#876438: marked as done (postgresql-common: Please update README.Debian for postgresql-10)
Your message dated Thu, 14 Dec 2017 20:55:43 + with message-id <e1epaxf-0007gr...@fasolo.debian.org> and subject line Bug#876438: fixed in postgresql-common 189 has caused the Debian Bug report #876438, regarding postgresql-common: Please update README.Debian for postgresql-10 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.) -- 876438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: postgresql-common Version: 185 Severity: wishlist Tags: patch Hi, I'm lazy and like copy-paste stuff; can you update README.Debian for postgresql-10? :) Patch attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/debian/README.Debian b/debian/README.Debian index c9c3f9b..c4e9976 100644 --- a/debian/README.Debian +++ b/debian/README.Debian @@ -113,15 +113,15 @@ remove the newer default cluster first. E. g., if you have postgresql-9.1 installed and want to upgrade to 9.4, you first install postgresql-9.4: - apt-get install postgresql-9.4 + apt-get install postgresql-10 -Then drop the default 9.4 cluster that was just created: +Then drop the default 10 cluster that was just created: - pg_dropcluster 9.4 main --stop + pg_dropcluster 10 main --stop -And then upgrade the 9.1 cluster to the latest installed version (e. g. 9.4): +And then upgrade the 9.6 cluster to the latest installed version (e. g. 9.6): - pg_upgradecluster 9.1 main + pg_upgradecluster 9.6 main SSL --- --- End Message --- --- Begin Message --- Source: postgresql-common Source-Version: 189 We believe that the bug you reported is fixed in the latest version of postgresql-common, 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 876...@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-common 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: Thu, 14 Dec 2017 21:13:24 +0100 Source: postgresql-common Binary: postgresql-common postgresql-client-common postgresql-server-dev-all postgresql postgresql-client postgresql-doc postgresql-contrib postgresql-all Architecture: source Version: 189 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public@lists.alioth.debian.org> Changed-By: Christoph Berg <m...@debian.org> Description: postgresql - object-relational SQL database (supported version) postgresql-all - metapackage depending on all PostgreSQL server packages postgresql-client - front-end programs for PostgreSQL (supported version) postgresql-client-common - manager for multiple PostgreSQL client versions postgresql-common - PostgreSQL database-cluster manager postgresql-contrib - additional facilities for PostgreSQL (supported version) postgresql-doc - documentation for the PostgreSQL database management system postgresql-server-dev-all - extension build tool for multiple PostgreSQL versions Closes: 876438 881501 Changes: postgresql-common (189) unstable; urgency=medium . [ Chris Lamb ] * Update README.Debian for postgresql-10. (Closes: #876438) . [ Christoph Berg ] * dh_make_pgxs: Use PostgreSQL license as default, fix extension name. * Modernize README.Debian's version numbers and SSL instructions. * postgresql@.service: Ignore startup failure, recovery might take arbitrarily long to finish. The actual service status still correctly reflects if the postmaster process is running. https://www.postgresql.org/message-id/2017205316.u56lkmkakdmcx6zm%40msg.df7cb.de * supported-versions: Version 10 on Ubuntu 18.04 (bionic). (Closes: #881501) * debian/maintscripts-functions: bump update-alternatives priority of version 1x to 1x0. * Unsupport 9.2 on apt.postgresql.org. * t/140_pg_config.t: Also test /usr/bin/pg_config.libpq-dev, and check MKDIR_P and abs_top_build/srcdir in Makefile.global. Checksums-Sha1: f2ae71ef1570bc1312967fd3244d9d3da6c0df61 2339 p
[Pkg-postgresql-public] Processed: Re: Bug#882409: postgresql-9.4: jessie->wheezy on amd64: psql: FATAL: Peer authentication failed for user "postgres"
Processing control commands: > severity -1 important Bug #882409 [postgresql-9.4] postgresql-9.4: jessie->wheezy on amd64: psql: FATAL: Peer authentication failed for user "postgres" Severity set to 'important' from 'serious' > forwarded -1 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710275 Bug #882409 [postgresql-9.4] postgresql-9.4: jessie->wheezy on amd64: psql: FATAL: Peer authentication failed for user "postgres" Set Bug forwarded-to-address to 'https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710275'. -- 882409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#827384: marked as done (skytools3: please make the build reproducible)
Your message dated Sun, 10 Dec 2017 08:54:16 +
with message-id <e1enxni-000gwl...@fasolo.debian.org>
and subject line Bug#882611: Removed package(s) from unstable
has caused the Debian Bug report #827384,
regarding skytools3: please make the build reproducible
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.)
--
827384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: skytools3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps fileordering
Hi!
While working on the “reproducible builds” effort [1], we have noticed
that skytools3 could not be built reproducibly.
The attached patch removes extra timestamps from the documentation generated
by Asciidoc and Epydoc and also ensure a stable file order when linking object
files into executables.
Once applied, all binary packages can be built reproducibly in our
current experimental framework.
Thanks for considering the patch.
Best regards
Sascha
[1]: https://wiki.debian.org/ReproducibleBuilds
diff -Nru skytools3-3.2.6/debian/changelog skytools3-3.2.6/debian/changelog
--- skytools3-3.2.6/debian/changelog 2016-01-14 20:49:10.0 +
+++ skytools3-3.2.6/debian/changelog 2016-06-14 21:37:01.0 +
@@ -1,3 +1,10 @@
+skytools3 (3.2.6-4.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Make build reproducible.
+
+ -- Sascha Steinbiss <sas...@steinbiss.name> Tue, 14 Jun 2016 21:36:51 +
+
skytools3 (3.2.6-4) unstable; urgency=medium
* Build for PostgreSQL 9.5.
diff -Nru skytools3-3.2.6/debian/patches/reproducible.patch skytools3-3.2.6/debian/patches/reproducible.patch
--- skytools3-3.2.6/debian/patches/reproducible.patch 1970-01-01 00:00:00.0 +
+++ skytools3-3.2.6/debian/patches/reproducible.patch 2016-06-15 12:50:15.0 +
@@ -0,0 +1,39 @@
+Description: make build reproducible
+ This patch makes the build reproducible by adjusting the build system to
+ use stable sorting order for file traversal as well as remove timestamps from
+ Asciidoc footers and HTML documentation created by Epydoc.
+Author: Sascha Steinbiss <sas...@steinbiss.name>
+--- a/doc/Makefile
b/doc/Makefile
+@@ -5,7 +5,7 @@
+
+ EPYDOC = epydoc
+ EPYARGS = --no-private --url="http://pgfoundry.org/projects/skytools/; \
+- --name="Skytools" --html --no-private -v
++ --name="Skytools" --html --no-private --no-include-build-time -v
+
+ TOPHTML = README.html INSTALL.html index.html
+ DOCHTML = \
+@@ -40,6 +40,7 @@
+
+ #AFLAGS = -a linkcss
+ #AFLAGS = -a stylesheet=extra.css
++AFLAGS += -s
+
+ all: $(FQMAN)
+
+--- a/lib/mk/amext-libusual.mk
b/lib/mk/amext-libusual.mk
+@@ -17,10 +17,10 @@
+ _USUAL_DIR = $(call JoinPath,$(srcdir),$(USUAL_DIR))
+
+ # module names from sources (plus headers)
+-UsualMods = $(trace1)$(shell $(_USUAL_DIR)/find_modules.sh $(_USUAL_DIR) $(wildcard $(addprefix $(srcdir)/,$(1
++UsualMods = $(trace1)$(shell $(_USUAL_DIR)/find_modules.sh $(_USUAL_DIR) $(sort $(wildcard $(addprefix $(srcdir)/,$(1)
+
+ # full-path sources based on module list
+-UsualSrcsFull = $(trace1)$(wildcard $(addprefix $(_USUAL_DIR)/usual/,$(addsuffix *.[ch],$(1
++UsualSrcsFull = $(trace1)$(sort $(wildcard $(addprefix $(_USUAL_DIR)/usual/,$(addsuffix *.[ch],$(1)
+
+ # remove USUAL_DIR
+ UsualStrip = $(trace1)$(subst $(_USUAL_DIR)/,,$(1))
diff -Nru skytools3-3.2.6/debian/patches/series skytools3-3.2.6/debian/patches/series
--- skytools3-3.2.6/debian/patches/series 2016-01-14 20:49:10.0 +
+++ skytools3-3.2.6/debian/patches/series 2016-06-14 21:36:13.0 +
@@ -1,2 +1,3 @@
tests-invalid-echo.patch
tests-ticker-missing-installcheck.patch
+reproducible.patch
diff -Nru skytools3-3.2.6/debian/rules skytools3-3.2.6/debian/rules
--- skytools3-3.2.6/debian/rules 2016-01-14 20:49:10.0 +
+++ skytools3-3.2.6/debian/rules 2016-06-15 12:17:21.0 +
@@ -3,6 +3,8 @@
SRCDIR = $(CURDIR)
PKGVERS = $(shell dpkg-parsechangelog | awk -F '[:-]' '/^Version:/ { print substr($$2, 2) }')
ORIG_EXCLUDE=--exclude-vcs --exclude=debian
+export LC_ALL=C
+export LANG=C
include /usr/share/postgresql-common/pgxs_debian_control.mk
--- End Message ---
--- Begin Message ---
Version: 3.2.6-5+rm
Dear submitter,
as the package skytools3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal
[Pkg-postgresql-public] Bug#883055: marked as done (postgresql-contrib-9.6 (re-)installs alternative manpages of postgresql-9.6)
Your message dated Sun, 10 Dec 2017 08:54:27 + with message-id <e1enxnt-000gx7...@fasolo.debian.org> and subject line Bug#883010: Removed package(s) from unstable has caused the Debian Bug report #883055, regarding postgresql-contrib-9.6 (re-)installs alternative manpages of postgresql-9.6 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.) -- 883055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: postgresql-contrib-9.6 Version: 9.6.5-1 Severity: normal The postinst script of both postgresql-9.6 and postgresql-contrib-9.6 call update-alternatives for (e.g.) postgres.1.gz. While this doesn’t pose a problem for the alternatives database itself, this causes manpages.debian.org to display two separate versions of postgres.1 (and others), one of which cannot be displayed. manpages.d.o integrates with piuparts.d.o and logs update-alternatives calls, then associates them with a Debian binary package, and treats them as if the binary package contained a symbolic link. The intended state is that only the package which ships the manpage (postgresql-9.6 in this case) makes the update-alternatives call. Could you please change the postinst script to not make duplicate update-alternatives calls? Thank you! -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel, mipsel, arm64 Kernel: Linux 4.13.0-1-amd64 (SMP w/12 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages postgresql-contrib-9.6 depends on: ii libc6 2.24-17 ii libpq5 10.0-1+b1 ii libselinux1 2.7-2 ii libssl1.1 1.1.0g-2 ii libuuid12.30.2-0.1 ii libxml2 2.9.4+dfsg1-5+b1 ii libxslt1.1 1.1.29-2.2 ii postgresql-9.6 9.6.5-1 ii zlib1g 1:1.2.8.dfsg-5 postgresql-contrib-9.6 recommends no packages. Versions of packages postgresql-contrib-9.6 suggests: pn libdbd-pg-perl -- no debconf information --- End Message --- --- Begin Message --- Version: 9.6.6-0+deb9u1+rm Dear submitter, as the package postgresql-9.6 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/883010 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Chris Lamb (the ftpmaster behind the curtain)--- End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#878561: marked as done (skytools3 FTBFS with PostgreSQL 10)
Your message dated Sun, 10 Dec 2017 08:54:16 +
with message-id <e1enxni-000gwl...@fasolo.debian.org>
and subject line Bug#882611: Removed package(s) from unstable
has caused the Debian Bug report #878561,
regarding skytools3 FTBFS with PostgreSQL 10
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.)
--
878561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: skytools3
Version: 3.2.6-5
Severity: serious
Tags: buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/skytools3.html
...
fakeroot debian/rules clean
pg_buildext checkcontrol
--- debian/control 2016-09-27 20:56:20.0 -1200
+++ debian/control.MBRpFc 2017-10-06 19:57:18.792581339 -1200
@@ -57,12 +57,12 @@
is based on snapshot based event handling ideas from Slony-I, written for
general usage.
-Package: postgresql-9.6-pgq3
+Package: postgresql-10-pgq3
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-9.6
+Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-10
Provides: skytools-modules
-Conflicts: skytools-modules-9.6
-Replaces: skytools-modules-9.6
+Conflicts: skytools-modules-10
+Replaces: skytools-modules-10
Description: Skype tools for PostgreSQL replication, londiste and PGQ
This is the PGQ extension used by Skype replication, londiste. It consists
of PL/pgsql, and C code in database.
Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
updatecontrol'.
If you are seeing this message in a buildd log, a sourceful upload is required.
/usr/share/postgresql-common/pgxs_debian_control.mk:9: recipe for target
'debian/control' failed
make: *** [debian/control] Error 1
Christoph Berg said:
totally weird build system
(Adrian Vondendriesch is checking if updating is feasible without
pulling too much hair)
--- End Message ---
--- Begin Message ---
Version: 3.2.6-5+rm
Dear submitter,
as the package skytools3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/882611
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#872198: marked as done (postgresql-9.6: unowned directory after purge: /etc/postgresql/9.6/main/conf.d/)
Your message dated Sun, 10 Dec 2017 08:54:27 + with message-id <e1enxnt-000gx7...@fasolo.debian.org> and subject line Bug#883010: Removed package(s) from unstable has caused the Debian Bug report #872198, regarding postgresql-9.6: unowned directory after purge: /etc/postgresql/9.6/main/conf.d/ 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.) -- 872198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: postgresql-9.6 Version: 9.6.4-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned directories on the system after purge, which is a violation of policy 6.8: https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. The maintainer scripts create (and later remove) a file in that directory. Manual directory removal may be not appropriate as this directory is shared between several packages. If the package would ship this as an empty directory, dpkg would take care of the creation and removal (if it's empty). >From the attached log (scroll to the bottom...): 0m53.8s ERROR: FAIL: Package purging left files on system: /etc/postgresql/9.6/ not owned /etc/postgresql/9.6/main/ not owned /etc/postgresql/9.6/main/conf.d/ not owned cheers, Andreas postgresql-9.6_9.6.4-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Version: 9.6.6-0+deb9u1+rm Dear submitter, as the package postgresql-9.6 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/883010 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Chris Lamb (the ftpmaster behind the curtain)--- End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#859550: marked as done (pgadmin3: Please migrate to openssl1.1 in buster)
Your message dated Fri, 01 Dec 2017 17:49:04 + with message-id <e1ekpqu-0006ih...@fasolo.debian.org> and subject line Bug#859550: fixed in pgadmin3 1.22.2-2 has caused the Debian Bug report #859550, regarding pgadmin3: Please migrate to openssl1.1 in buster 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.) -- 859550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pgadmin3 Version: 1.22.1-1 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/pgadmin3_1.22.1-1_amd64-20160530-2114 On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. There is a libssl-dev package available in experimental that contains a recent snapshot, I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt --- End Message --- --- Begin Message --- Source: pgadmin3 Source-Version: 1.22.2-2 We believe that the bug you reported is fixed in the latest version of pgadmin3, 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 859...@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 pgadmin3 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: Thu, 30 Nov 2017 20:25:53 +0100 Source: pgadmin3 Binary: pgadmin3 pgadmin3-data Architecture: source Version: 1.22.2-2 Distribution: unstable Urgency: low Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public@lists.alioth.debian.org> Changed-By: Christoph Berg <m...@debian.org> Description: pgadmin3 - graphical administration tool for PostgreSQL pgadmin3-data - graphical administration tool for PostgreSQL - documentation Closes: 859550 Changes: pgadmin3 (1.22.2-2) unstable; urgency=low . [ Denis Briand ] * Update upstream repository path in debian/watch. * Bump standards version to 4.1.1 * Use libgcrypt to fix FTBFS with openssl 1.1.0, many thanks to Cyril Brulebois for the analysis (Closes: #859550). . [ Christoph Berg ] * Remove explicit pgadmin3-dbg package (but leave code in place for backports). * Use python3-sphinx for documentation. Checksums-Sha1: f008fa83bb5f7991df907200550dc45b2ce38b07 2270 pgadmin3_1.22.2-2.dsc a2fc15207b817b8ea580d24862a7f7d0e933c467 19208 pgadmin3_1.22.2-2.debian.tar.xz a6ea9843bfcdc85f58feff0cd475339a99f92701 12192 pgadmin3_1.22.2-2_source.buildinfo Checksums-Sha256: 5915a1cdceb25a605b2c4d4bff41dd774b2e40af37b14fd7d3ee7d7cd3c57dc4 2270 pgadmin3_1.22.2-2.dsc ba83810a7bb5ba1926e51bd329b2fcf6d9690b920c49ee047331c3419b643ccf 19208 pgadmin3_1.22.2-2.debian.tar.xz 9743733d250829a697cbdde716783e69dafe4d515eba979c4b07718b2ef815fa 12192 pgadmin3_1.22.2-2_source.buildinfo Files: c58e4ac685a3530f73823d6dcfb6a93c 2270 database optional pgadmin3_1.22.2-2.dsc d73e855cb5e717b15443417c5f97eeb7 19208 database optional pgadmin3_1.22.2-2.debian.tar.xz dc76e7c678a62c671605841b00232521 12192 database optional pgadmin3_1.22.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlohkg0ACgkQTFprqxLS p661/BAAmaaLGw8nUnGkQMvL1dL8oFs8SBokH0HdCru/Lxg3nO8shOVbWnUwRugh HHN0VZfNpXyn77WQW5SwieaOaR+CmWBGBujV7dUSQRMxdK0UQ+fXIDXxAYjO66OR eC8kDRjQdnAu+eAuG8qRU1ngVkSU/jlMfJGyEyZ5MBWlBmKNQLrES1BlS+ueswFU SGLXVRG9WwcfI5gN7koFsC8KrT6dvApaqjYNn7Lhd7lboSjDxuYs1ldGA2ap3aHM q/kwiUoyYPV0IwKZVV/VBQQS3Y1iA0U+LgI2QJ1uqHzmPZ9K+qk99iHn5AymIt0q JNdF00kYZuZ5TxPXXq/MAUuxehdH+wwqIGzQ/8QDJ+WYzlpWPlZy39gYKxyj9QUQ PTZUE2p+C1cTINu/d/MCoANVfMuZpL3it7IntwmPBOQ+W9FrQUH3xD0VcQV/zO6u 2e6plL0s2FD0Ve2sYT6Cr+1G37k1GQWOXps5nwexcpLn5YuN/yRsk3cuvIzaver4 UXsf8xiCRQu5D1LduKi9SISKeW1X1VZsE5K9TFq/OkpQZVQKY+BLvckmSCDzTfNc 4gNMgsNrJ
[Pkg-postgresql-public] Bug#882240: marked as done (pspg: FTBFS on hurd-i386: MAXPATHLEN undeclared)
Your message dated Fri, 24 Nov 2017 17:18:58 + with message-id <e1eihcw-0005gt...@fasolo.debian.org> and subject line Bug#882240: fixed in pspg 0.6-1 has caused the Debian Bug report #882240, regarding pspg: FTBFS on hurd-i386: MAXPATHLEN undeclared 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.) -- 882240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882240 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pspg Version: 0.5-1 Severity: important Tags: upstream Justification: fails to build from source User: debian-h...@lists.debian.org Usertags: hurd-i386 The build of pspg for hurd-i386 (admittedly not a release architecture) failed: src/pspg.c:1092:16: error: 'MAXPATHLEN' undeclared (first use in this function); did you mean 'MAX_STYLE'? The Hurd famously has no static MAXPATHLEN. Best practice is to allocate path buffers dynamically based on what you actually encounter, but if that's not convenient, you can look up _PC_PATH_MAX via pathconf or define a fallback constant (traditionally 4096). Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu --- End Message --- --- Begin Message --- Source: pspg Source-Version: 0.6-1 We believe that the bug you reported is fixed in the latest version of pspg, 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 882...@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 pspg 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: Fri, 24 Nov 2017 17:34:45 +0100 Source: pspg Binary: pspg Architecture: source Version: 0.6-1 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public@lists.alioth.debian.org> Changed-By: Christoph Berg <m...@debian.org> Description: pspg - PostgreSQL pager Closes: 882240 Changes: pspg (0.6-1) unstable; urgency=medium . * New upstream version. * Define MAXPATHLEN on Hurd. (Closes: #882240) Checksums-Sha1: 03eb9df04ad1f5a1e19561e82ce5822f95d8a8ae 1994 pspg_0.6-1.dsc f89b875ce7ef7cb4816f685bd5968155fa20a6d5 845851 pspg_0.6.orig.tar.gz 1f6bc0dd6399ffa3e2f165e70228d54484d54bc9 2392 pspg_0.6-1.debian.tar.xz a732ce9d1caf499ecebd4cd2137e88813ef9e598 5144 pspg_0.6-1_source.buildinfo Checksums-Sha256: 12f9172b4ce45d31781877e5823c4fc217aa492053cfbf39dc7346252a381481 1994 pspg_0.6-1.dsc 3b6a26ce43759eef6524230905a2b444bcbdbb133dda337d44efa05bddcce59a 845851 pspg_0.6.orig.tar.gz 889577cb65d88cf91293f54761d46a2d3422ce7f22e83a8a1c8fa5c3e7d8bb37 2392 pspg_0.6-1.debian.tar.xz 3ca6b05246436c30877ee882a1260c1ec8604c8ee1974a6928813ecbcc5018b0 5144 pspg_0.6-1_source.buildinfo Files: 687ea36b64959f6b2e8ad52e892c6c0d 1994 database optional pspg_0.6-1.dsc 65e3206fa94e8ff0247f4f9764de8597 845851 database optional pspg_0.6.orig.tar.gz 5fba5844f4f32baf09cf390b20392031 2392 database optional pspg_0.6-1.debian.tar.xz 44c553b300847a7460e9e8cb6a88f29a 5144 database optional pspg_0.6-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAloYT/sACgkQTFprqxLS p64hNhAAko/S2NvdyBboig5QBdZ45YW+zSmeS5v60xnwRniwMUQ/YPW3X1GoZOqe yA6LNvs6nKCP7ssAEJQDoQgrQfRxlFE/XQwv1T7qSx01BHTeYWOo86y4sHo/iuAJ E2MAWodU78UO1Cht0ta48sTRtSS1bEETfekCUyXAU9rUgdFYo51RYhSNFuNGlXCe KvxeqzdiVjETybMAknCyhgOHE0wkKjtsLTspJrApgsl3+CV44dmKbdl0RynQkp2i KgTmmUYKsChENgN+koA2adqjae6oP08DWQLhCSaeIB6ArkgFXq7ns+IBeM56GXCT ZJrv2uJREkkOfvZHvFNHJXzt5SYPd5vDQWpypQi7G7kK7qietffJg2yzXUiMk43X EyZW+TQptEaMN48inReNkQjRLTu+bRi/ihKAIfK+SIN49sM6dUwYhufGnvbu+p2U nho4WuwYKGwi7B3L2Vq/dLXWuEOdZoaX9VYEkKLX5T+Y0yyHN0oRR2VfU/neaCLS yVJHdvuykKwCo7x+//Kk+MABp0nOD0sZxBPmBKe2ILtWb3m8Q8bVIKxrxHnMs8ct s2PkCPbqkFLiG38kjJpE3E6rgXXJptep0VICWPRI9QxVebLYPvuCeC2+CyGjlHI1 M+NaJRjBlmLffB6fAmnxdufkF4Xot0tWLtPF598M7lkMCDeYs9A= =2y7G -END PGP SIGNATURE End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@list
[Pkg-postgresql-public] Processed: Re: Bug#859550: pgadmin3: Please migrate to openssl1.1 in buster
Processing control commands: > tag -1 patch Bug #859550 [src:pgadmin3] pgadmin3: Please migrate to openssl1.1 in buster Added tag(s) patch. -- 859550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#877851: marked as done (pgpool_setup + pg_md5 path)
Your message dated Thu, 16 Nov 2017 21:17:09 + with message-id <e1efrx3-000aay...@fasolo.debian.org> and subject line Bug#877851: fixed in pgpool2 3.6.7-1 has caused the Debian Bug report #877851, regarding pgpool_setup + pg_md5 path 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.) -- 877851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pgpool2 Version: 3.6.1-1 --- Begin Message --- Hi everyone, Though this has a high probability of being addresses, I did see an issue in a the regular Debian Stretch pgpool2 package, so I figure I'd bring it to your attention just in case. I was playing with running the pgpool_setup script as I'm just figuring things out, and I noticed that pgpool_setup (a bash script) tries some non-Debian paths when trying to find binaries, but you can set a bunch of environment variables to fix all of these issues, except one: pgpool_setup looks to $PGPOOL_INSTALL_DIR/bin (PGPOOL_INSTALL_DIR being the install path, eg /usr, /usr/local, etc) for a "pg_md5" binary that gets installed in /usr/sbin. Both pgpool_setup and pg_md5 exist in the same package, so I'm thinking that either the path for pg_md5 should be changed to /usr/bin or the script should be edited to /usr/sbin as a quick fix. Anyway, this obviously easy to deal with on my end, but since this issue seems to exist in the stable Debian package, I thought I'd mention it. -- Dan Thomson d...@astuteinternet.com Astute Internet Incorporated T: 1.888.685.1661 (604.637.7939) F: 604.738.0518 www.astuteinternet.com 100% Uptime Dedicated Hosting in Vancouver, Seattle, Los Angeles, Toronto, New York and Miami Follow us on Twitter: @astutehosting ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public --- End Message --- --- Begin Message --- Looks like the same is true for pcp_recovery_node as well as pg_md5. On 05/10/17 12:23 PM, Dan Thomson wrote: Hi everyone, Though this has a high probability of being addresses, I did see an issue in a the regular Debian Stretch pgpool2 package, so I figure I'd bring it to your attention just in case. I was playing with running the pgpool_setup script as I'm just figuring things out, and I noticed that pgpool_setup (a bash script) tries some non-Debian paths when trying to find binaries, but you can set a bunch of environment variables to fix all of these issues, except one: pgpool_setup looks to $PGPOOL_INSTALL_DIR/bin (PGPOOL_INSTALL_DIR being the install path, eg /usr, /usr/local, etc) for a "pg_md5" binary that gets installed in /usr/sbin. Both pgpool_setup and pg_md5 exist in the same package, so I'm thinking that either the path for pg_md5 should be changed to /usr/bin or the script should be edited to /usr/sbin as a quick fix. Anyway, this obviously easy to deal with on my end, but since this issue seems to exist in the stable Debian package, I thought I'd mention it. -- Dan Thomson d...@astuteinternet.com Astute Internet Incorporated T: 1.888.685.1661 (604.637.7939) F: 604.738.0518 www.astuteinternet.com 100% Uptime Dedicated Hosting in Vancouver, Seattle, Los Angeles, Toronto, New York and Miami Follow us on Twitter: @astutehosting ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public --- End Message --- --- End Message --- --- Begin Message --- Source: pgpool2 Source-Version: 3.6.7-1 We believe that the bug you reported is fixed in the latest version of pgpool2, 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 877...@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 pgpool2 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: Thu, 16 Nov 2017 20:59:45 +0100 Source: pg
[Pkg-postgresql-public] Bug#859552: marked as done (pgpool2: Please migrate to openssl1.1 in buster)
Your message dated Thu, 16 Nov 2017 21:17:09 + with message-id <e1efrx3-000aas...@fasolo.debian.org> and subject line Bug#859552: fixed in pgpool2 3.6.7-1 has caused the Debian Bug report #859552, regarding pgpool2: Please migrate to openssl1.1 in buster 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.) -- 859552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pgpool2 Version: 3.4.3-1 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/pgpool2_3.4.3-1_amd64-20160529-1506 On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. There is a libssl-dev package available in experimental that contains a recent snapshot, I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt --- End Message --- --- Begin Message --- Source: pgpool2 Source-Version: 3.6.7-1 We believe that the bug you reported is fixed in the latest version of pgpool2, 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 859...@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 pgpool2 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: Thu, 16 Nov 2017 20:59:45 +0100 Source: pgpool2 Binary: pgpool2 libpgpool0 libpgpool-dev postgresql-10-pgpool2 Architecture: source Version: 3.6.7-1 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public@lists.alioth.debian.org> Changed-By: Christoph Berg <m...@debian.org> Description: libpgpool-dev - pgpool control protocol library - headers libpgpool0 - pgpool control protocol library pgpool2- connection pool server and replication proxy for PostgreSQL postgresql-10-pgpool2 - connection pool server and replication proxy for PostgreSQL - mod Closes: 859552 877851 Changes: pgpool2 (3.6.7-1) unstable; urgency=medium . * New upstream version. + Supports OpenSSL 1.1. (Closes: #859552) * Remove pgpool2-dbg package. * Fix path of pg_md5 and pcp_recovery_node in scripts. (Closes: #877851) Checksums-Sha1: 26d78b7ca0304eeccddcf6929002d3d1fbf1a01d 2661 pgpool2_3.6.7-1.dsc c46b65475988e7a6c226e068274c542118682b51 3188186 pgpool2_3.6.7.orig.tar.gz a5084adb8dcd3cf356777e6d612504c3174f9a0d 12744 pgpool2_3.6.7-1.debian.tar.xz 62860503c8c37458d39ced111b24c9831daf0064 7783 pgpool2_3.6.7-1_source.buildinfo Checksums-Sha256: 1eda938867bd3553d2714af971b879b3cb4d6a6daefee7345398006c4caae648 2661 pgpool2_3.6.7-1.dsc 09cfe2cb36b9171d4a987a8b100e298e46d6a369c1b61d9e1a47d442ce16e249 3188186 pgpool2_3.6.7.orig.tar.gz 6020ba1c32b61c2e1ee60ed02325f6a35fa5cac7bacbdc4e5d66a664b2e121a7 12744 pgpool2_3.6.7-1.debian.tar.xz 0911fb3e3914007846d1cdc799365b7bdb9106138f87fbd671ea32f50e9c303a 7783 pgpool2_3.6.7-1_source.buildinfo Files: 9eeeff819326e700075978e15a81790a 2661 database optional pgpool2_3.6.7-1.dsc cb893b8deb8bf46b020139799b1810a9 3188186 database optional pgpool2_3.6.7.orig.tar.gz 1858586091617c339611e98005ba0a6e 12744 database optional pgpool2_3.6.7-1.debian.tar.xz 64d6f2b25317a4b1f7800a26edf0b999 7783 database optional pgpool2_3.6.7-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAloN9vUACgkQTFprqxLS p67rnBAAs/p94z8DBkDuPfQCrLPSH8lv4gopbW+LvVPcCchpuS5UhMnv2Sct6JcE WV9zS+orEMVoOju6ANCwI0cJEd8apI5GsnEICNglVA+L+K0bYd+uDDGeMufkFZeg YYB9f3a8UzabM/SttSxOp+zu7KaNp07V6s8P0gvdZ/Kc112ATRdo8aBZMZ3v/TaR Bs7mf9MSChpiHoZaZBKMNqvpRQcBB2u7qglEUdq80NDhlezpbjyklFr0ObU9WPMB 9RIFq38S9bBIBMUS+QtHaNwCi51m7W7XbSrSUxwp/zYRotMzDfyEkfaPr3IlDhuW RwVeQ12UF1+1bxuLeWg1LW3HREiDTRQqB7h4Sc2J
[Pkg-postgresql-public] Processed: raise severity of openssl-1.1-trans blockers
gi?bug=859230 859297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859297 859367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859367 859540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859540 859542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859542 859543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859543 859544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859544 859545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859545 859546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859546 859548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859548 859550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859550 859551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859551 859552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859552 859553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859553 859554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859554 859555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859555 859556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859556 859557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859557 859558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859558 859669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859669 859671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859671 859673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859673 859675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859675 859715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859715 859716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859716 859717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859717 859718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859718 859719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859719 859720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859720 859721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859721 859750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859750 859783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859783 859784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859784 859786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859786 859789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859789 859790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859790 859791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859791 859826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859826 859829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859829 859831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859831 859838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859838 859840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859840 859841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859841 859852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859852 859853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859853 863568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863568 867140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867140 870775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870775 870779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870779 871939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871939 872885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872885 873574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873574 873647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873647 874699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874699 875349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: Re: Bug#881498: postgresql-mysql-fdw: autopkgtests fail with postgresql-10
Processing commands for cont...@bugs.debian.org: > forwarded 881498 https://github.com/EnterpriseDB/mysql_fdw/issues/147 Bug #881498 [src:postgresql-mysql-fdw] postgresql-mysql-fdw: autopkgtests fail with postgresql-10 Ignoring request to change the forwarded-to-address of bug#881498 to the same value > End of message, stopping processing here. Please contact me if you need assistance. -- 881498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: limit source to postgresql-common, tagging 881501
Processing commands for cont...@bugs.debian.org: > limit source postgresql-common Limiting to bugs with field 'source' containing at least one of 'postgresql-common' Limit currently set to 'source':'postgresql-common' > tags 881501 + pending Bug #881501 [src:postgresql-common] postgresql-common: Please recognize Ubuntu 18.04 as a supported version Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 881501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: bug 881498 is forwarded to https://github.com/EnterpriseDB/mysql_fdw/issues/147
Processing commands for cont...@bugs.debian.org: > forwarded 881498 https://github.com/EnterpriseDB/mysql_fdw/issues/147 Bug #881498 [src:postgresql-mysql-fdw] postgresql-mysql-fdw: autopkgtests fail with postgresql-10 Set Bug forwarded-to-address to 'https://github.com/EnterpriseDB/mysql_fdw/issues/147'. > thanks Stopping processing here. Please contact me if you need assistance. -- 881498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: limit source to postgresql-common, tagging 876438
Processing commands for cont...@bugs.debian.org: > limit source postgresql-common Limiting to bugs with field 'source' containing at least one of 'postgresql-common' Limit currently set to 'source':'postgresql-common' > tags 876438 + pending Bug #876438 [src:postgresql-common] postgresql-common: Please update README.Debian for postgresql-10 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 876438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: bug 859551 is forwarded to https://github.com/pgbouncer/pgbouncer/issues/236
Processing commands for cont...@bugs.debian.org: > forwarded 859551 https://github.com/pgbouncer/pgbouncer/issues/236 Bug #859551 [src:pgbouncer] pgbouncer: Please migrate to openssl1.1 in buster Set Bug forwarded-to-address to 'https://github.com/pgbouncer/pgbouncer/issues/236'. > thanks Stopping processing here. Please contact me if you need assistance. -- 859551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#877264: marked as done (postgresql-10: unowned directory after purge: /etc/postgresql/10/main/conf.d/)
Your message dated Thu, 09 Nov 2017 15:37:48 + with message-id <e1ecoto-0004tk...@fasolo.debian.org> and subject line Bug#877264: fixed in postgresql-10 10.1-1 has caused the Debian Bug report #877264, regarding postgresql-10: unowned directory after purge: /etc/postgresql/10/main/conf.d/ 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.) -- 877264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: postgresql-10 Version: 10~rc1-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned directories on the system after purge, which is a violation of policy 6.8: https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. The maintainer scripts create (and later remove) a file in that directory. Manual directory removal may be not appropriate as this directory is shared between several packages. If the package would ship this as an empty directory, dpkg would take care of the creation and removal (if it's empty). >From the attached log (scroll to the bottom...): 0m53.1s ERROR: FAIL: Package purging left files on system: /etc/postgresql/10/not owned /etc/postgresql/10/main/ not owned /etc/postgresql/10/main/conf.d/not owned cheers, Andreas postgresql-10_10~rc1-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: postgresql-10 Source-Version: 10.1-1 We believe that the bug you reported is fixed in the latest version of postgresql-10, 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 877...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg <christoph.b...@credativ.de> (supplier of updated postgresql-10 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: Wed, 08 Nov 2017 10:40:59 +0100 Source: postgresql-10 Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3 postgresql-10 postgresql-10-dbg postgresql-client-10 postgresql-server-dev-10 postgresql-doc-10 postgresql-plperl-10 postgresql-plpython-10 postgresql-plpython3-10 postgresql-pltcl-10 Architecture: source Version: 10.1-1 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public@lists.alioth.debian.org> Changed-By: Christoph Berg <christoph.b...@credativ.de> Description: libecpg-compat3 - older version of run-time library for ECPG programs libecpg-dev - development files for ECPG (Embedded PostgreSQL for C) libecpg6 - run-time library for ECPG programs libpgtypes3 - shared library libpgtypes for PostgreSQL 10 libpq-dev - header files for libpq5 (PostgreSQL library) libpq5 - PostgreSQL C client library postgresql-10 - object-relational SQL database, version 10 server postgresql-10-dbg - debug symbols for postgresql-10 postgresql-client-10 - front-end programs for PostgreSQL 10 postgresql-doc-10 - documentation for the PostgreSQL database management system postgresql-plperl-10 - PL/Perl procedural language for PostgreSQL 10 postgresql-plpython-10 - PL/Python procedural language for PostgreSQL 10 postgresql-plpython3-10 - PL/Python 3 procedural language for PostgreSQL 10 postgresql-pltcl-10 - PL/Tcl procedural language for PostgreSQL 10 postgresql-server-dev-10 - development files for PostgreSQL 10 server-side programming Closes: 877264 Changes: postgresql-10 (10.1-1) unstable; urgency=medium . * New upstream version. . + Ensure that INSERT ... ON CONFLICT DO UPDATE checks table permissions and RLS policies in all cases (Dean Rasheed) . The update path of INSERT ... ON CONFLICT DO UPDATE requires SELECT permission on the columns of the arbiter index, but it failed to check for that in the case of an arbiter specified by constraint name. In addition, for a table with row level security enabled, it failed to check updated rows against
[Pkg-postgresql-public] Bug#879897: marked as done (postgresql-multicorn: python{, 3}-all-dev as test deps)
Your message dated Mon, 06 Nov 2017 19:04:53 +
with message-id <e1ebmhz-0005sb...@fasolo.debian.org>
and subject line Bug#879897: fixed in postgresql-multicorn 1.3.3-6
has caused the Debian Bug report #879897,
regarding postgresql-multicorn: python{,3}-all-dev as test deps
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.)
--
879897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-multicorn
Version: 1.3.3-5
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch
Dear maintainers,
I noticed during the python3.6 migration in Ubuntu that postgresql-multicorn
failed its autopkgtests, because while there were multiple supported
versions of python3 (3.5, 3.6), 3.6 was not available at test time.
The attached patch addresses this by making the tests depend on the
corresponding python*-all-dev package.
Apologies for not submitting this patch in time to matter for the python3.6
transition in Debian, but it's still a correct change that will be
applicable for the next python3 transition.
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru postgresql-multicorn-1.3.3/debian/tests/control
postgresql-multicorn-1.3.3/debian/tests/control
--- postgresql-multicorn-1.3.3/debian/tests/control 2017-10-22
06:22:35.0 -0700
+++ postgresql-multicorn-1.3.3/debian/tests/control 2017-10-26
20:46:48.0 -0700
@@ -1,7 +1,7 @@
-Depends: newpid, postgresql-10-python-multicorn, python-psycopg2,
python-sqlalchemy, postgresql-server-dev-all (>= 156~), postgresql-common (>=
159~), postgresql-contrib-10, postgresql-plpython-10
+Depends: newpid, postgresql-9.6-python-multicorn, python-psycopg2,
python-sqlalchemy, postgresql-server-dev-all (>= 156~), postgresql-common (>=
159~), postgresql-contrib-9.6, postgresql-plpython-9.6, python-all-dev
Test-Command: debian/tests/installcheck python2
Restrictions: needs-root allow-stderr
-Depends: newpid, postgresql-10-python3-multicorn, python3-psycopg2,
python3-sqlalchemy, postgresql-server-dev-all (>= 156~), postgresql-common (>=
159~), postgresql-contrib-10, postgresql-plpython3-10
+Depends: newpid, postgresql-9.6-python3-multicorn, python3-psycopg2,
python3-sqlalchemy, postgresql-server-dev-all (>= 156~), postgresql-common (>=
159~), postgresql-contrib-9.6, postgresql-plpython3-9.6, python3-all-dev
Test-Command: debian/tests/installcheck python3
Restrictions: needs-root allow-stderr
diff -Nru postgresql-multicorn-1.3.3/debian/tests/control.in
postgresql-multicorn-1.3.3/debian/tests/control.in
--- postgresql-multicorn-1.3.3/debian/tests/control.in 2017-10-21
02:57:09.0 -0700
+++ postgresql-multicorn-1.3.3/debian/tests/control.in 2017-10-26
20:46:48.0 -0700
@@ -1,7 +1,7 @@
-Depends: newpid, postgresql-PGVERSION-python-multicorn, python-psycopg2,
python-sqlalchemy, postgresql-server-dev-all (>= 156~), postgresql-common (>=
159~), postgresql-contrib-PGVERSION, postgresql-plpython-PGVERSION
+Depends: newpid, postgresql-PGVERSION-python-multicorn, python-psycopg2,
python-sqlalchemy, postgresql-server-dev-all (>= 156~), postgresql-common (>=
159~), postgresql-contrib-PGVERSION, postgresql-plpython-PGVERSION,
python-all-dev
Test-Command: debian/tests/installcheck python2
Restrictions: needs-root allow-stderr
-Depends: newpid, postgresql-PGVERSION-python3-multicorn, python3-psycopg2,
python3-sqlalchemy, postgresql-server-dev-all (>= 156~), postgresql-common (>=
159~), postgresql-contrib-PGVERSION, postgresql-plpython3-PGVERSION
+Depends: newpid, postgresql-PGVERSION-python3-multicorn, python3-psycopg2,
python3-sqlalchemy, postgresql-server-dev-all (>= 156~), postgresql-common (>=
159~), postgresql-contrib-PGVERSION, postgresql-plpython3-PGVERSION,
python3-all-dev
Test-Command: debian/tests/installcheck python3
Restrictions: needs-root allow-stderr
--- End Message ---
--- Begin Message ---
Source: postgresql-multicorn
Source-Version: 1.3.3-6
We believe that the bug you reported is fixed in the latest version of
postgresql-multicorn, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
atta
[Pkg-postgresql-public] Processed: Re: Bug#710275: postgresql needs restart on libc upgrade
Processing control commands: > severity -1 normal Bug #710275 [postgresql-10] postgresql-9.1: Needs restart on libc upgrade Severity set to 'normal' from 'important' > retitle -1 postgresql needs restart on libc/nss upgrade Bug #710275 [postgresql-10] postgresql-9.1: Needs restart on libc upgrade Changed Bug title to 'postgresql needs restart on libc/nss upgrade' from 'postgresql-9.1: Needs restart on libc upgrade'. > reassign -1 libc6 Bug #710275 [postgresql-10] postgresql needs restart on libc/nss upgrade Bug reassigned from package 'postgresql-10' to 'libc6'. Ignoring request to alter found versions of bug #710275 to the same values previously set Ignoring request to alter fixed versions of bug #710275 to the same values previously set > affects -1 postgresql-common Bug #710275 [libc6] postgresql needs restart on libc/nss upgrade Added indication that 710275 affects postgresql-common -- 710275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: tagging 626732
Processing commands for cont...@bugs.debian.org: > tags 626732 + wontfix Bug #626732 [postgresql-10] src:postgresql-9.1: missing source for src/backend/snowball/libstemmer/ Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 626732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#551078: marked as done (libpq5: Possibility to specify the Kerberos keytab file)
Your message dated Sun, 29 Oct 2017 22:09:42 +0100 with message-id <20171029210942.ca4g4ykfi22sf...@msg.df7cb.de> and subject line Re: Bug#551078: libpq5: Possibility to specify the Kerberos keytab file has caused the Debian Bug report #551078, regarding libpq5: Possibility to specify the Kerberos keytab file 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.) -- 551078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551078 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Subject: libpq5: Possibility to specify the Kerberos keytab file Package: libpq5 Version: 8.4.1-1 Severity: wishlist Libpq often used for connect to the database without human assist. In this case there is no opportunity to enter a password and get a ticket for authentication in Kerberos. Please add the ability to specify in a function PQconnectdb(conninfo) path to the Kerberos 5 keytab file. Keytab file is a common method of authentication without human and its support has already been implemented in the postgres server. -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (990, 'stable'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (SMP w/1 CPU core) Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libpq5 depends on: ii libc6 2.9-25 GNU C Library: Shared libraries ii libcomerr2 1.41.9-1 common error description library ii libgssapi-krb5-21.7dfsg~beta3-1 MIT Kerberos runtime libraries - k ii libkrb5-3 1.7dfsg~beta3-1 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.11-1 OpenLDAP libraries ii libssl0.9.8 0.9.8g-15+lenny5 SSL shared libraries libpq5 recommends no packages. libpq5 suggests no packages. -- debconf-show failed signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Re: Denis Feklushkin 2009-10-15 <20091015205247.4ac85598@db> > Subject: libpq5: Possibility to specify the Kerberos keytab file > Package: libpq5 > Version: 8.4.1-1 > Severity: wishlist > > Libpq often used for connect to the database without human assist. In > this case there is no opportunity to enter a password and get a ticket > for authentication in Kerberos. > > Please add the ability to specify in a function PQconnectdb(conninfo) > path to the Kerberos 5 keytab file. > > Keytab file is a common method of authentication without human and > its support has already been implemented in the postgres server. Hi Denis, while I agree that this would be a useful feature, there's little use in keeping this wishlist bug open in the Debian bug tracker. If you are still interested in getting this forward, cross-check it with the PostgreSQL TODO list [1], and bring it up on the PostgreSQL mailing lists. [1] https://wiki.postgresql.org/wiki/Todo I'm closing the wishlist bug now, sorry. Christoph--- End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: limit source to postgresql-10, tagging 877264
Processing commands for cont...@bugs.debian.org: > limit source postgresql-10 Limiting to bugs with field 'source' containing at least one of 'postgresql-10' Limit currently set to 'source':'postgresql-10' > tags 877264 + pending Bug #877264 [postgresql-10] postgresql-10: unowned directory after purge: /etc/postgresql/10/main/conf.d/ Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 877264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#856437: marked as done (postgresql-plproxy: autopkgtest depends on newpid which fails to install LXD runners)
Your message dated Mon, 23 Oct 2017 13:03:35 +0200 with message-id <20171023110335.sj3tdeagliplj...@msg.df7cb.de> and subject line Re: [Pkg-postgresql-public] Bug#856437: postgresql-plproxy: autopkgtest depends on newpid which fails to install LXD runners has caused the Debian Bug report #856437, regarding postgresql-plproxy: autopkgtest depends on newpid which fails to install LXD runners 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.) -- 856437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: postgresql-plproxy Version: 2.7-1 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu zesty ubuntu-patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * d/t/control: the newpid package fails to install in LXD environments (relies on fs capabilities which are disallowed by the kernel in user namespaces), so use unshare instead. Thanks for considering the patch. *** /tmp/tmp9Ftaz0/postgresql-plproxy_2.7-1ubuntu2.debdiff diff -Nru postgresql-plproxy-2.7/debian/tests/control postgresql-plproxy-2.7/debian/tests/control --- postgresql-plproxy-2.7/debian/tests/control 2017-02-28 10:19:53.0 -0800 +++ postgresql-plproxy-2.7/debian/tests/control 2017-02-28 16:28:57.0 -0800 @@ -1,3 +1,3 @@ Tests: installcheck -Depends: @, postgresql-server-dev-all, newpid +Depends: @, postgresql-server-dev-all, util-linux Restrictions: allow-stderr needs-root diff -Nru postgresql-plproxy-2.7/debian/tests/installcheck postgresql-plproxy-2.7/debian/tests/installcheck --- postgresql-plproxy-2.7/debian/tests/installcheck2017-02-28 10:19:53.0 -0800 +++ postgresql-plproxy-2.7/debian/tests/installcheck2017-02-28 16:28:57.0 -0800 @@ -32,7 +32,7 @@ if ! chmod o+w $AUTOPKGTEST_TMP && \ PG_CLUSTER_CONF_ROOT=$AUTOPKGTEST_TMP \ PG_CONFIG=/usr/lib/postgresql/$v/bin/pg_config \ - newnet pg_virtualenv -c "-p 5432 --locale C -s $AUTOPKGTEST_TMP" -i '--auth trust' -v $v \ + unshare -inu pg_virtualenv -c "-p 5432 --locale C -s $AUTOPKGTEST_TMP" -i '--auth trust' -v $v \ make -f $PWD/Makefile installcheck; then \ head -n 500 regression.diffs exit 1 -- System Information: Debian Release: stretch/sid APT prefers zesty APT policy: (500, 'zesty') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.10.0-8-generic (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Nishanth Aravamudan Ubuntu Server Canonical Ltd --- End Message --- --- Begin Message --- Re: Christian Ehrhardt 2017-10-23 <caatjj0jjabxuenphs2io99gswfo8cfhmnhqhvugi6-4hy9i...@mail.gmail.com> > I think you fixed this "on the other end" by accepting the fix for newpid > [1]. > I assume Nish and I will soon look into our pg-10 transition and will let > you know if we hit something like this again/still. > > But this bug can be closed - at least for now and very likely forever. > > [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860031 Ah right, I had already forgotten about that one. Thanks :) Christoph--- End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#872430: marked as done (postgresql-common: [INTL:pt] Updated Portuguese translation for debconf messages)
Your message dated Sun, 22 Oct 2017 21:09:17 +
with message-id <e1e6nuj-0008q5...@fasolo.debian.org>
and subject line Bug#872430: fixed in postgresql-common 187
has caused the Debian Bug report #872430,
regarding postgresql-common: [INTL:pt] Updated Portuguese translation for
debconf messages
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.)
--
872430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-common
Version: 184
Tags: l10n, patch
Severity: wishlist
Updated Portuguese translation for postgresql-common's debconf messages.
Feel free to use it.
For translation updates please contact 'Last Translator' or the
Portuguese Translation Team .
--
Best regards,
"Traduz" - Portuguese Translation Team
http://www.DebianPT.org
# Portuguese translation of postgresql-common debconf messages.
# This file is distributed under the same license as the postgresql-common package.
# Ricardo Silva <ardo...@gmail.com>, 2006,2017.
#
#
msgid ""
msgstr ""
"Project-Id-Version: postgresql-common 184\n"
"Report-Msgid-Bugs-To: postgresql-com...@packages.debian.org\n"
"POT-Creation-Date: 2016-03-05 11:47+0100\n"
"PO-Revision-Date: 2017-08-17 11:35-\n"
"Last-Translator: Ricardo Silva <ardo...@gmail.com>\n"
"Language-Team: Portuguese <tra...@debianpt.org>\n"
"Language: pt\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 1.6.10\n"
#. Type: error
#. Description
#: ../postgresql-common.templates:1001
msgid "Obsolete major version ${old}"
msgstr "Versão maior ${old} obsoleta"
#. Type: error
#. Description
#: ../postgresql-common.templates:1001
msgid ""
"The PostgreSQL version ${old} is obsolete, but the server or client packages "
"are still installed. Please install the latest packages (postgresql-"
"${latest} and postgresql-client-${latest}) and upgrade the existing "
"${oldversion} clusters with pg_upgradecluster (see manpage)."
msgstr ""
"A versão ${old} do PostgreSQL está obsoleta, mas ainda tem os pacotes de "
"cliente e/ou do servidor instalados. Por favor instale os últimos pacotes "
"(postgresql-${latest} e postgresql-client-${latest}) e actualize os seus "
"clusters ${oldversion} existentes com o pg_upgradecluster (ver página do "
"manual)."
#. Type: error
#. Description
#: ../postgresql-common.templates:1001
msgid ""
"Please be aware that the installation of postgresql-${latest} will "
"automatically create a default cluster ${latest}/main. If you want to "
"upgrade the ${old}/main cluster, you need to remove the already existing "
"${latest} cluster (pg_dropcluster --stop ${latest} main, see manpage for "
"details)."
msgstr ""
"Por favor tenha consciência que a instalação de postgresql-${latest} irá "
"criar automaticamente o cluster por omissão ${latest}/main. Se deseja "
"actualizar o cluster ${old}/main, precisa de remover o cluster ${latest} "
"existente (pg_dropcluster --stop ${latest} main, ver página do manual para "
"detalhes)."
#. Type: error
#. Description
#: ../postgresql-common.templates:1001
msgid ""
"The old server and client packages are no longer supported. After the "
"existing clusters are upgraded, the postgresql-${old} and postgresql-client-"
"${old} packages should be removed."
msgstr ""
"Os pacotes de cliente e servidor antigos já não são suportados. Após "
"actualizar os clusters existentes, deve remover os pacotes postgresql-${old} "
"e postgresql-client-${old}."
#. Type: error
#. Description
#: ../postgresql-common.templates:1001
msgid ""
"Please see /usr/share/doc/postgresql-common/README.Debian.gz for details."
msgstr ""
"Por favor consulte o ficheiro /usr/share/doc/postgresql-common/README.Debian."
"gz para mais detalhes."
#. Type: boolean
#. Description
#: ../postgresql-common.templates:2001
msgid "Enable SSL by default in new PostgreSQL clusters?"
msgstr "Activar SSL por omissão em novos clusters PostgreSQL?"
#. Type:
[Pkg-postgresql-public] Bug#868232: marked as done (lost (unintentionally) unconditional pg_updatedicts on postinst)
Your message dated Sun, 22 Oct 2017 21:09:17 +
with message-id <e1e6nuj-0008pz...@fasolo.debian.org>
and subject line Bug#868232: fixed in postgresql-common 187
has caused the Debian Bug report #868232,
regarding lost (unintentionally) unconditional pg_updatedicts on postinst
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.)
--
868232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868232
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-common
Version: 184
Severity: normal
This is suggesting a fix for the recent autopkgtest errors like [1], more
of them at [2].
TL;DR:
- we should add an unconditional pg_updatedicts on "configure" in the
postinst.
- This bug is explaining the details and polling for opinions on adding
that line
Details:
Formerly e.g. version 181 when installing on a clean system created
/var/cache/postgresql:
$ ls -dlaF /var/cache/postgresql
ls: cannot access '/var/cache/postgresql': No such file or directory
$ sudo apt install postgresql-common
[...]
$ ls -dlaF /var/cache/postgresql
drwxr-xr-x 3 root root 4096 Jul 13 07:43 /var/cache/postgresql/
But now e.g. with version 184 it doesn't do that anymore:
$ ls -dlaF /var/cache/postgresql
ls: cannot access '/var/cache/postgresql': No such file or directory
$ sudo apt install postgresql-common
[...]
$ ls -dlaF /var/cache/postgresql
ls: cannot access '/var/cache/postgresql': No such file or directory
The reason is the dropping of the following statement that was considered
to be no more needed:
if dpkg --compare-versions "$2" lt 94; then
pg_updatedicts || true
fi
I agree version 94 is long ago.
But since then, due to a mistake, this always was an unconditional
pg_updatedicts call on first install.
Quote from dpkg:
"These treat an empty version as earlier than any version: lt le eq ne ge
gt."
Now on a new install of postgresql-common $2 is empty and so this triggered
on first install since version 95.
That in turn might seem unimportant, but affects cases where the first
pg_updatedicts that is executed is under special conditions.
Exactly that happens on the autopkgtests of postgresql-9.6 (or later).
There the test dependencies install postgresql-common, as outlined above
now without calling pg_updatedicts.
Due to that the directory does not exist when the tests themselves call
pg_updatedicts to update the dicts.
But because they do so with a umask o 077
postgresql-common-184/testsuite:
22 : ${PG_UMASKS="077"} # default umask(s) to try
[...]
169 umask $U
[...]
Finally t/150_tsearch_stemming.t will all pg_updatedicts in that env
But due to the umask it is created as
drwx-- 3 root root 4096 Jul 13 07:43 /var/cache/postgresql/
And that finally lets the test fail with an issue like in [1]
=== Running test 150_tsearch_stemming.t ... ===
[...[
not ok 9 - creating en_US full text search configuration ERROR: could not
open dictionary file "/usr/share/postgresql/9.6/tsearch_data/en_us.dict":
Permission denied
Ok, long story short - we should make sure the base directory is created
correctly on postinst.
Therefor I suggest really adding an unconditional pg_updatedicts in there.
The postrm already has the matching rm to clean the dir up btw.
[1]:
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/postgresql-9.6/20170713_010956/log.gz
[2]: https://ci.debian.net/packages/p/postgresql-9.6/unstable/amd64/
--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
--- End Message ---
--- Begin Message ---
Source: postgresql-common
Source-Version: 187
We believe that the bug you reported is fixed in the latest version of
postgresql-common, 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 868...@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-common 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: Sun, 22 Oct 2017 20:44:38 +0200
Source: postgresql-common
Binary: postgresql-common postgresql-client-common postgresql-server-dev-all
postgresql post
[Pkg-postgresql-public] Bug#878564: marked as done (postgresql-filedump FTBFS with PostgreSQL 10)
Your message dated Sun, 22 Oct 2017 18:49:14 +
with message-id <e1e6ljc-000ft1...@fasolo.debian.org>
and subject line Bug#878564: fixed in postgresql-filedump 10.0-1
has caused the Debian Bug report #878564,
regarding postgresql-filedump FTBFS with PostgreSQL 10
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.)
--
878564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresql-filedump
Version: 9.6.0-2
Severity: serious
Tags: buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/postgresql-filedump.html
...
dh_auto_build
make -j1
make[1]: Entering directory '/build/1st/postgresql-filedump-9.6.0'
cc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-I/usr/include/postgresql/10/server pg_filedump.c -c
pg_filedump.c: In function 'FormatItem':
pg_filedump.c:994:18: error: 'SizeOfIptrData' undeclared (first use in this
function)
if (numBytes < SizeOfIptrData)
^~
pg_filedump.c:994:18: note: each undeclared identifier is reported only once
for each function it appears in
pg_filedump.c: In function 'FormatControl':
pg_filedump.c:1613:19: error: 'ControlFileData {aka struct ControlFileData}'
has no member named 'enableIntTimes'
(controlData->enableIntTimes ?
^~
Makefile:26: recipe for target 'pg_filedump.o' failed
make[1]: *** [pg_filedump.o] Error 1
--- End Message ---
--- Begin Message ---
Source: postgresql-filedump
Source-Version: 10.0-1
We believe that the bug you reported is fixed in the latest version of
postgresql-filedump, 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 878...@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-filedump
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: Sun, 22 Oct 2017 20:12:17 +0200
Source: postgresql-filedump
Binary: postgresql-filedump
Architecture: source
Version: 10.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Christoph Berg <m...@debian.org>
Description:
postgresql-filedump - Utility to format PostgreSQL files
Closes: 878564
Changes:
postgresql-filedump (10.0-1) unstable; urgency=medium
.
* New upstream release supporting PG10. (Closes: #878564)
* Update Standards-Version and package URLs.
* Re-enable PIE on 32bit archs.
Checksums-Sha1:
e5d9fed0f4283320cd45549e070efe4eafac4ec1 2158 postgresql-filedump_10.0-1.dsc
0858429de2c42f0bb095f4af185a91cec1f99e95 31544
postgresql-filedump_10.0.orig.tar.gz
2f112df94cec4184b0f7ea36d4abab648ac163c5 3016
postgresql-filedump_10.0-1.debian.tar.xz
c7f17808528451438aa415468401f1af3eb97e1c 6778
postgresql-filedump_10.0-1_source.buildinfo
Checksums-Sha256:
bb9458f095a6cb9f6dc03797abdcfa34521be675d7dc979a799bdbb1fc21461c 2158
postgresql-filedump_10.0-1.dsc
5adddeeed5ca97408b94333c5baf5deb6732c7b3fbbd192d7d2c639f5c1be409 31544
postgresql-filedump_10.0.orig.tar.gz
fa4a814128799458ed3d9cadde0e21eac3c274e86189da0c62e8c4417e095810 3016
postgresql-filedump_10.0-1.debian.tar.xz
961f78fa4d105c2940a811574cedaaa611f95be350d69acdad96ffa2a1d3bc2f 6778
postgresql-filedump_10.0-1_source.buildinfo
Files:
34ed4128a00fa15388208c257662f6a8 2158 database optional
postgresql-filedump_10.0-1.dsc
1299b533be564819c03d92567e31e497 31544 database optional
postgresql-filedump_10.0.orig.tar.gz
3833fb9fa7dd6f292f1e1a8ee0e2f16c 3016 database optional
postgresql-filedump_10.0-1.debian.tar.xz
2d168e5ff738c54bad68049439d0 6778 database optional
postgresql-filedump_10.0-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlns5KkACgkQTFprqxLS
p67ISw/6Albu5KXK6xLHIAbKH13f9ngOfKiV6Q5ji0w7mWmln/1vA960GWYiDL+O
R+YZE2Hh2CkYg2hyHvsRdgP7+jZj7ITklC8hcj0YSsVDcAN9hyb0GnVmL/PeXDGl
4/SLeoJpzxkZzjNfW1PuLacwbMAIrkyVhtYb8noPs0JC96kypoBceNiqSgsB1Nc7
4rUd6ej5aWwolPysWr9G5WPY4LDzvy/gDH7ldv2SLwMMlM+jXiW76yD
[Pkg-postgresql-public] Processed: limit source to postgresql-common, tagging 868232
Processing commands for cont...@bugs.debian.org: > limit source postgresql-common Limiting to bugs with field 'source' containing at least one of 'postgresql-common' Limit currently set to 'source':'postgresql-common' > tags 868232 + pending Bug #868232 [postgresql-common] lost (unintentionally) unconditional pg_updatedicts on postinst Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 868232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#878581: marked as done (pglogical FTBFS: fatal error: pglogical_compat.h: No such file or directory)
Your message dated Thu, 19 Oct 2017 09:38:12 +0200 with message-id <20171019073812.ogbdzlsxci62s...@msg.df7cb.de> and subject line Re: Bug#878581: pglogical FTBFS: fatal error: pglogical_compat.h: No such file or directory has caused the Debian Bug report #878581, regarding pglogical FTBFS: fatal error: pglogical_compat.h: No such file or directory 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.) -- 878581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878581 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pglogical Version: 2.0.1-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pglogical.html ... debian/rules override_dh_auto_build make[1]: Entering directory '/build/1st/pglogical-2.0.1' pg_buildext build build-%v ### build 10 ### make[2]: Entering directory '/build/1st/pglogical-2.0.1/build-10' pglogical_apply.o pglogical_conflict.o pglogical_manager.o pglogical.o pglogical_node.o pglogical_relcache.o pglogical_repset.o pglogical_rpc.o pglogical_functions.o pglogical_queue.o pglogical_fe.o pglogical_worker.o pglogical_sync.o pglogical_sequences.o pglogical_executor.o pglogical_dependency.o pglogical_apply_heap.o pglogical_apply_spi.o pglogical_output_config.o pglogical_output_plugin.o pglogical_output_proto.o pglogical_proto_json.o pglogical_proto_native.o pglogical_monitoring.o /build/1st/pglogical-2.0.1/compat100/pglogical_compat.o sed 's/__PGLOGICAL_VERSION__/2.0.1/;s/__REQUIRES__//' /build/1st/pglogical-2.0.1/pglogical.control.in > /build/1st/pglogical-2.0.1/pglogical.control gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -g -g -O2 -fdebug-prefix-map=/build/postgresql-10-Wvqwf1/postgresql-10-10.0=. -fstack-protector-strong -Wformat -Werror=format-security -fno-omit-frame-pointer -fPIC -fPIC -I/usr/include/postgresql -I -I. -I/build/1st/pglogical-2.0.1 -I/usr/include/postgresql/10/server -I/usr/include/postgresql/internal -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I/usr/include/libxml2 -I/usr/include/mit-krb5 -c -o pglogical_apply.o /build/1st/pglogical-2.0.1/pglogical_apply.c In file included from /build/1st/pglogical-2.0.1/pglogical_proto_native.h:20:0, from /build/1st/pglogical-2.0.1/pglogical_conflict.h:22, from /build/1st/pglogical-2.0.1/pglogical_apply.c:62: /build/1st/pglogical-2.0.1/pglogical_output_plugin.h:20:10: fatal error: pglogical_compat.h: No such file or directory #include "pglogical_compat.h" ^~~~ compilation terminated. : recipe for target 'pglogical_apply.o' failed make[2]: *** [pglogical_apply.o] Error 1 --- End Message --- --- Begin Message --- Version: 2.1.0-1 Re: Adrian Bunk 2017-10-14 <150800749854.6287.16219608579091251260.reportbug@localhost> > Source: pglogical > Version: 2.0.1-1 > Severity: serious > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pglogical.html 2.1.0-1 looks good now. Christoph--- End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#876851: marked as done (pgextwlist FTBFS with PostgreSQL 10)
Your message dated Tue, 17 Oct 2017 12:00:16 +
with message-id <e1e4qxg-000fm6...@fasolo.debian.org>
and subject line Bug#876851: fixed in pgextwlist 1.6-1
has caused the Debian Bug report #876851,
regarding pgextwlist FTBFS with PostgreSQL 10
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.)
--
876851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pgextwlist
Version: 1.5-1
Severity: serious
Tags: buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pgextwlist.html
...
fakeroot debian/rules clean
pg_buildext checkcontrol
--- debian/control 2016-09-27 04:39:03.0 -1200
+++ debian/control.ovz8MK 2018-10-26 16:43:22.556097914 -1200
@@ -10,10 +10,10 @@
Vcs-Browser: https://github.com/dimitri/pgextwlist
XS-Testsuite: autopkgtest
-Package: postgresql-9.6-pgextwlist
+Package: postgresql-10-pgextwlist
Section: libs
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-9.6
+Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-10
Description: PostgreSQL Extension Whitelisting
This extension implements extension whitelisting, and will actively prevent
users from installing extensions not in the provided list. Also, this
Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
updatecontrol'.
If you are seeing this message in a buildd log, a sourceful upload is required.
/usr/share/postgresql-common/pgxs_debian_control.mk:9: recipe for target
'debian/control' failed
make: *** [debian/control] Error 1
--- End Message ---
--- Begin Message ---
Source: pgextwlist
Source-Version: 1.6-1
We believe that the bug you reported is fixed in the latest version of
pgextwlist, 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 876...@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 pgextwlist 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: Sun, 15 Oct 2017 13:21:54 +0200
Source: pgextwlist
Binary: postgresql-10-pgextwlist
Architecture: source amd64
Version: 1.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Christoph Berg <m...@debian.org>
Description:
postgresql-10-pgextwlist - PostgreSQL Extension Whitelisting
Closes: 876851
Changes:
pgextwlist (1.6-1) unstable; urgency=medium
.
* New upstream version with PostgreSQL 10 support, patch by
Oskari Saarenmaa. (Closes: #876851)
* Update Dimitri's email address.
Checksums-Sha1:
27f2af12d0b89501b282ed3a30f9226417425a88 2064 pgextwlist_1.6-1.dsc
9068905210457c9e61f96bb91efeeed70d142490 16697 pgextwlist_1.6.orig.tar.gz
4fd5687a43e90b41c74474d6290a1abd0a6e72f1 802 pgextwlist_1.6-1.diff.gz
feb2c5f4f6a73a76ca8e1e9639259d5989771f65 7543 pgextwlist_1.6-1_amd64.buildinfo
618aadf4c686941a95817554aba248a0dbe3a4f9 60128
postgresql-10-pgextwlist-dbgsym_1.6-1_amd64.deb
202c8c1e9d24b671a33b752c175ba0096848e9aa 12358
postgresql-10-pgextwlist_1.6-1_amd64.deb
Checksums-Sha256:
5202d0cbb738c3a50820c41724f9862ad7d8e04a65c5368ba5f6198004dbae01 2064
pgextwlist_1.6-1.dsc
29b1ac8d2d2948fb94cfa21f144ec2e5f195d6fd6d18136c6bd28b910ba1b00c 16697
pgextwlist_1.6.orig.tar.gz
941653648dbe04e369d85edab523e324be91d9fbfb270440ad86649c5dc79f6d 802
pgextwlist_1.6-1.diff.gz
0a652535f115129046866dd7853fde389d54eaaebc06001031fe8e895d483aaf 7543
pgextwlist_1.6-1_amd64.buildinfo
93ef5cbcecadff9b5c9a7a9dccbdffe0bb685d637f3554963b146e6361dff11e 60128
postgresql-10-pgextwlist-dbgsym_1.6-1_amd64.deb
de3590137c901428dd3f7c674ecbe20641f4f9a39057d41cd4d5b86241926fc5 12358
postgresql-10-pgextwlist_1.6-1_amd64.deb
Files:
d1d3adee467d21d60e8b242940196257 2064 database optional pgextwlist_1.6-1.dsc
b8f086d191da230e8b9e1fa848dec250 16697 database optional
pgextwlist_1.6.orig.tar.gz
be0b3f420fe4fa44330797c294a28770 802 database optional pgextwlist_1.6-1.diff.gz
116fc832e9608c97f66bde7d17a6473d 7543 database optional
pgextwli
[Pkg-postgresql-public] Bug#878563: marked as done (postgresql-pllua FTBFS with PostgreSQL 10)
Your message dated Mon, 16 Oct 2017 20:57:08 +0300
with message-id <20171016175708.ag6ta7l4ctzxamf7@localhost>
and subject line Fixed in 1:1.1.0-2
has caused the Debian Bug report #878563,
regarding postgresql-pllua FTBFS with PostgreSQL 10
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.)
--
878563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresql-pllua
Version: 1:1.1.0-1
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/postgresql-pllua.html
...
fakeroot debian/rules clean
pg_buildext checkcontrol
--- debian/control 2017-08-06 03:44:43.0 -1200
+++ debian/control.TlZMC6 2018-11-14 14:04:08.776817432 -1200
@@ -10,10 +10,10 @@
Vcs-Git: https://anonscm.debian.org/git/pkg-postgresql/postgresql-pllua.git
Vcs-Browser:
https://anonscm.debian.org/cgit/pkg-postgresql/postgresql-pllua.git/
-Package: postgresql-9.6-pllua
+Package: postgresql-10-pllua
Architecture: any
-Depends: postgresql-9.6, ${misc:Depends}, ${shlibs:Depends}
-Description: Lua procedural language for PostgreSQL 9.6
+Depends: postgresql-10, ${misc:Depends}, ${shlibs:Depends}
+Description: Lua procedural language for PostgreSQL 10
PL/Lua is an implementation of Lua as a loadable procedural language for
PostgreSQL: with PL/Lua you can use PostgreSQL functions and triggers
written in the Lua programming language.
Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
updatecontrol'.
If you are seeing this message in a buildd log, a sourceful upload is required.
/usr/share/postgresql-common/pgxs_debian_control.mk:9: recipe for target
'debian/control' failed
make: *** [debian/control] Error 1
Christoph Berg said:
needs to be fixed upstream
--- End Message ---
--- Begin Message ---
Version: 1:1.1.0-2
postgresql-pllua (1:1.1.0-2) unstable; urgency=medium
* Pull patch to support PostgreSQL 10.
-- Christoph Berg <m...@debian.org> Sat, 14 Oct 2017 11:10:04 +0200
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed--- End Message ---
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: limit source to pgextwlist, tagging 876851
Processing commands for cont...@bugs.debian.org: > limit source pgextwlist Limiting to bugs with field 'source' containing at least one of 'pgextwlist' Limit currently set to 'source':'pgextwlist' > tags 876851 + pending Bug #876851 [src:pgextwlist] pgextwlist FTBFS with PostgreSQL 10 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 876851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#856423: marked as done (postgresql-plproxy: autopkgtest failures since move to newnet (2.6-2))
Your message dated Sat, 14 Oct 2017 15:20:36 + with message-id <e1e3oeu-0003oe...@fasolo.debian.org> and subject line Bug#856423: fixed in postgresql-plproxy 2.8-1 has caused the Debian Bug report #856423, regarding postgresql-plproxy: autopkgtest failures since move to newnet (2.6-2) 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.) -- 856423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: postgresql-plproxy Version: 2.7-1 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu zesty ubuntu-patch Dear Maintainer, The autopkgtests for postgresql-plproxy have been failing ever since 2.6-2 because postgres is not network namespace aware. In Ubuntu, the attached patch was applied to achieve the following: * d/t/installcheck fixes: - Passing a port to pg_virtualenv even with newnet does not avoid port collisions, as pg_virtualenv (via pg_createcluster) is only looking at the configured clusters on the filesystem, not what is running in the current network namespace. Set an alternative PG_CLUSTER_CONF_ROOT instead, and set it before we call pg_virtualenv. - Set the socket directory for pg_createcluster, as we are using the standard port and that can lead to conflicts. This also requires making the AUTOPKGTEST_TMP directory world-writeable so the postgres user can write socket information there. Thanks for considering the patch. *** /tmp/tmpnVHESZ/postgresql-plproxy_2.7-1ubuntu1.debdiff diff -Nru postgresql-plproxy-2.7/debian/tests/installcheck postgresql-plproxy-2.7/debian/tests/installcheck --- postgresql-plproxy-2.7/debian/tests/installcheck2016-09-25 14:04:41.0 -0700 +++ postgresql-plproxy-2.7/debian/tests/installcheck2017-02-28 10:19:53.0 -0800 @@ -21,9 +21,19 @@ ;; esac - if ! newnet pg_virtualenv -c '-p 5432 --locale C' -i '--auth trust' -v $v \ - make -f $PWD/Makefile \ - installcheck PG_CONFIG=/usr/lib/postgresql/$v/bin/pg_config; then + # AUTOPKGTEST_TMP is not writeable by any user except root, but + # we want to use it for storing the Postgres socket + # Set PG_CLUSTER_CONF_ROOT, because although we are running in a + # network namespace (so we can reuse the default port), + # pg_virtualenv/pg_createcluster looks at the configured + # databases on the filesystem + # Set the socket directory because we are to re-use the port and + # there can be conflicts in the normal socket directory + if ! chmod o+w $AUTOPKGTEST_TMP && \ + PG_CLUSTER_CONF_ROOT=$AUTOPKGTEST_TMP \ + PG_CONFIG=/usr/lib/postgresql/$v/bin/pg_config \ + newnet pg_virtualenv -c "-p 5432 --locale C -s $AUTOPKGTEST_TMP" -i '--auth trust' -v $v \ + make -f $PWD/Makefile installcheck; then \ head -n 500 regression.diffs exit 1 fi -- System Information: Debian Release: stretch/sid APT prefers zesty APT policy: (500, 'zesty') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.10.0-8-generic (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Nishanth Aravamudan Ubuntu Server Canonical Ltd --- End Message --- --- Begin Message --- Source: postgresql-plproxy Source-Version: 2.8-1 We believe that the bug you reported is fixed in the latest version of postgresql-plproxy, 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 856...@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-plproxy 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: Sat, 14 Oct 2017 16:21:59 +0200 Source: postgresql-plproxy Binary: postgresql-10-plproxy Architecture: source Version: 2.8-1 Distribution: unstable Urge
[Pkg-postgresql-public] Bug#876842: marked as done (orafce FTBFS with PostgreSQL 10)
Your message dated Sat, 14 Oct 2017 09:03:08 +0200
with message-id <20171014070308.tp3dmrvzoaelh...@msg.df7cb.de>
and subject line Re: Bug#876842: orafce FTBFS with PostgreSQL 10
has caused the Debian Bug report #876842,
regarding orafce FTBFS with PostgreSQL 10
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.)
--
876842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: orafce
Version: 3.3.1-3
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/orafce.html
...
fakeroot debian/rules clean
pg_buildext checkcontrol
--- debian/control 2016-11-18 23:27:08.0 -1200
+++ debian/control.S0k7Eu 2018-10-26 16:40:45.520097914 -1200
@@ -18,10 +18,10 @@
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-postgresql/orafce.git
XS-Testsuite: autopkgtest
-Package: postgresql-9.6-orafce
+Package: postgresql-10-orafce
Architecture: any
-Depends: postgresql-9.6, ${misc:Depends}, ${shlibs:Depends}
-Description: Oracle support functions for PostgreSQL 9.6
+Depends: postgresql-10, ${misc:Depends}, ${shlibs:Depends}
+Description: Oracle support functions for PostgreSQL 10
This project implements some functions for compatibility with Oracle.
The functionality was verified on Oracle 10g, and the module is
useful for production work.
Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
updatecontrol'.
If you are seeing this message in a buildd log, a sourceful upload is required.
/usr/share/postgresql-common/pgxs_debian_control.mk:9: recipe for target
'debian/control' failed
make: *** [debian/control] Error 1
--- End Message ---
--- Begin Message ---
Version: 3.6.0-1
Re: Adrian Bunk 2017-09-26
<150641877968.19686.8226364293576862807.reportbug@localhost>
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
(postgresql-10-)orafce just passed NEW, which is among the last
packages to transition to PG10.
The remaining packages for the transition are:
pgextwlist: postgresql-9.6-pgextwlist - RM: https://bugs.debian.org/878440
postgresql-pllua: postgresql-9.6-pllua - needs to be fixed upstream
repmgr: postgresql-9.6-repmgr - has new rc version in experimental
skytools3: postgresql-9.6-pgq3 - totally weird build system
(Adrian Vondendriesch is checking if updating is feasible without
pulling too much hair)
Thanks for filing the FTBFS bugs on the non-transition packages!
Christoph
signature.asc
Description: PGP signature
--- End Message ---
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: reassign 710275 to postgresql-10
Processing commands for cont...@bugs.debian.org: > reassign 710275 postgresql-10 Bug #710275 [postgresql-9.6] postgresql-9.1: Needs restart on libc upgrade Bug reassigned from package 'postgresql-9.6' to 'postgresql-10'. Ignoring request to alter found versions of bug #710275 to the same values previously set Ignoring request to alter fixed versions of bug #710275 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 710275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: reassign 626732 to postgresql-10
Processing commands for cont...@bugs.debian.org: > reassign 626732 postgresql-10 Bug #626732 [postgresql-9.6] src:postgresql-9.1: missing source for src/backend/snowball/libstemmer/ Bug reassigned from package 'postgresql-9.6' to 'postgresql-10'. Ignoring request to alter found versions of bug #626732 to the same values previously set Ignoring request to alter fixed versions of bug #626732 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 626732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: reassign 704802 to postgresql-plperl-10
Processing commands for cont...@bugs.debian.org: > reassign 704802 postgresql-plperl-10 Bug #704802 [postgresql-9.6] plperl crashes immediately on kfreebsd Bug reassigned from package 'postgresql-9.6' to 'postgresql-plperl-10'. Ignoring request to alter found versions of bug #704802 to the same values previously set Ignoring request to alter fixed versions of bug #704802 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 704802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: reassign 640451 to postgresql-10
Processing commands for cont...@bugs.debian.org: > reassign 640451 postgresql-10 Bug #640451 [postgresql-9.6] adminpack extension cannot handle config files in /etc Bug reassigned from package 'postgresql-9.6' to 'postgresql-10'. Ignoring request to alter found versions of bug #640451 to the same values previously set Ignoring request to alter fixed versions of bug #640451 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 640451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#877381: marked as done (plr: please make the build reproducible)
Your message dated Sat, 07 Oct 2017 16:04:12 + with message-id <e1e0rag-000adf...@fasolo.debian.org> and subject line Bug#877381: fixed in plr 1:8.3.0.17-3 has caused the Debian Bug report #877381, regarding plr: please make the build reproducible 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.) -- 877381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: plr Version: 1:8.3.0.17-2 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Hi, Whilst working on the Reproducible Builds effort [0], we noticed that plr could not be built reproducibly as it encodes the date in generated HTML. Patch attached. [0] https://reproducible-builds.org/ Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- a/debian/rules 2017-10-01 09:43:31.433455583 +0100 --- b/debian/rules 2017-10-01 09:52:20.327204302 +0100 @@ -10,6 +10,8 @@ override_dh_installdocs: dh_installdocs --all doc/plr-US.pdf doc/html/*.html + find debian/*/usr/share/doc/ -type f -name '*.html' -print0 | \ + xargs -0r sed -i -e 's@CONTENT="[^"]*"@CONTENT=""@g' override_dh_auto_install: +pg_buildext loop postgresql-%v-plr --- End Message --- --- Begin Message --- Source: plr Source-Version: 1:8.3.0.17-3 We believe that the bug you reported is fixed in the latest version of plr, 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 877...@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 plr 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: Sat, 07 Oct 2017 17:21:25 +0200 Source: plr Binary: postgresql-10-plr Architecture: source Version: 1:8.3.0.17-3 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public@lists.alioth.debian.org> Changed-By: Christoph Berg <m...@debian.org> Description: postgresql-10-plr - Procedural language interface between PostgreSQL and R Closes: 877381 Changes: plr (1:8.3.0.17-3) unstable; urgency=medium . * Use SOURCE_DATE_EPOCH for documentation timestamp via openjade. Closes: #877381 Checksums-Sha1: a8221f6438a96d960c4860ac2f33b0e27450b703 2123 plr_8.3.0.17-3.dsc 32903612552c9d1aceed859e50dd320906edd9ec 13532 plr_8.3.0.17-3.debian.tar.xz a8f19b614503a69a2085ef8592652d1e4197fd3f 10246 plr_8.3.0.17-3_source.buildinfo Checksums-Sha256: 213eb8a1729dba37b3ca84e14f0cec1baa7d4dde17c0bf32ee9e203242b9af5a 2123 plr_8.3.0.17-3.dsc 3704b8972031f69e8ffa80bc555f084fa841295f6e9638ff46fab19071681ff6 13532 plr_8.3.0.17-3.debian.tar.xz 3bac56c13c6e73207ba280ed27d622ddfa2b12364e60099d56d2d89583e8c94b 10246 plr_8.3.0.17-3_source.buildinfo Files: b09a376fafd336dc1e47fafe807399e4 2123 database optional plr_8.3.0.17-3.dsc 0f688eaa2ba0ef52e533347c9ecefbd4 13532 database optional plr_8.3.0.17-3.debian.tar.xz 653d57c545b5190bffb3011dfae5a064 10246 database optional plr_8.3.0.17-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlnY9EQACgkQTFprqxLS p67agBAArJTTlHQJDrPZmUphATTBUDnT7Aut70ZoRYGSYjnZ2I36r4ePL/tSOlbg Pb1+enO6qMBDysRycn5ZyAN56APuXW0QC02U3Vpg25rpHqDoZJFaP72vHYNlH25f S3keqv7uOepXCQe4ONNofzANHEAYi1V5castR4Pe2YZqBuLuvemjr/HHxiQhWbSG 5YngyXG6XVDNAvnJKo8UhpSvGixw+d/bI0sApihLVn0b74g/sY5GGqAgdM7Zh1Oo Sv1CTfJRVehyB5mVNy3i/wgJc5IeqzvlCrAI4ThrxDnR/CK4zh3F1X4D96KPPj7S 2n++hHZT4MKKD9yjuIj1EAIZL4RUBcuahgODprjcexLduix/Ddl3pN59Lla90m+P mo32TxyDQvyqqnpjJ3pDH4UCdN7FheIA0XR0KLRb5JclyVV9v+q6HrnWoST5D+Lt cMP7hjIGcp2n8LifGQIsZj3RuXumaC9zwIzozbiwDex8MdHK68z9I3pF+Jb4fR7g hCApyWQuEnprFw0tawm0usb/+kNljdg/pw8/DMjqSmkiEBrTRUqXzD32uwmHQNK2 5nKPZQeJeAxC6hcz/Ah+6ATYW8su8ZjQ8O5ShV8ESA1AyyDp18xZRNNh/OArY99I VWNfVq5ZH0Y9nw4T02h76ZJA+eezsB8lVbVXS9OQvMX8bGrFwMg= =J9KC -END PGP SIGNATURE End Message --- ___ Pkg-pos
[Pkg-postgresql-public] Processed: Re: Bug#877920: postgresql-common: pg_upgradecluster 9.6 -> 10 fails (locale problem)
Processing control commands: > tags -1 moreinfo Bug #877920 [postgresql-common] postgresql-common: pg_upgradecluster 9.6 -> 10 fails (locale problem) Added tag(s) moreinfo. -- 877920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#790231: marked as done (check-postgres: FTBFS under pbuilder: Test failure in 02_disk_space.t)
Your message dated Thu, 5 Oct 2017 19:48:13 +0200 with message-id <20171005174813.h3x5jkqurzsbt...@msg.df7cb.de> and subject line Re: Bug#790231: check-postgres: FTBFS under pbuilder: Test failure in 02_disk_space.t has caused the Debian Bug report #790231, regarding check-postgres: FTBFS under pbuilder: Test failure in 02_disk_space.t 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.) -- 790231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: check-postgres Version: 2.21.0-3 Severity: normal >From my pbuilder build log: ... debian/rules override_dh_auto_test make[1]: Entering directory '/tmp/buildd/check-postgres-2.21.0' debian/run-test + export LC_ALL=C + export SKIP_NETWORK_TESTS=1 + trap cleanup 0 2 3 15 + /usr/share/postgresql-common/supported-versions + echo running make test for 9.4 running make test for 9.4 + cleanup + rm -rf test_database_check_postgres* /tmp/cptesting_socket* + export PGBINDIR=/usr/lib/postgresql/9.4/bin + make test make[2]: Entering directory '/tmp/buildd/check-postgres-2.21.0' PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/00_basic.t ... ok t/00_signature.t ... skipped: Test skipped unless environment variable RELEASE_TESTING is set t/00_test_tester.t . skipped: Test skipped unless environment variable RELEASE_TESTING is set t/01_validate_range.t .. ok t/02_autovac_freeze.t .. # Creating database in directory "test_database_check_postgres" Creating new symlink socket at /tmp/cptesting_socket t/02_autovac_freeze.t .. ok t/02_backends.t ok t/02_bloat.t ... ok t/02_checkpoint.t .. ok t/02_cluster_id.t .. ok t/02_commitratio.t . ok t/02_connection.t .. ok t/02_custom_query.t ok t/02_database_size.t ... ok t/02_dbstats.t . ok t/02_disabled_triggers.t ... ok t/02_disk_space.t .. 1/8 # Failed test 'Action 'disk_space' reports file system' # at t/02_disk_space.t line 42. # 'POSTGRES_DISK_SPACE OK: DB "postgres" (host:/tmp/cptesting_socket) FS - mounted on / is using 44.11 GB of 91.54 GB (51%) | time=0.02s size=47365783552B # ' # doesn't match '(?^:FS /.*? mounted on /.*? is using )' t/02_disk_space.t .. 6/8 # Failed test 'Action 'disk_space' reports MRTG output' # at t/02_disk_space.t line 57. # '45908787200 # 0 # # - # ' # doesn't match '(?^:\A\d+\n0\n\n/.*\n)' # Looks like you failed 2 tests of 8. t/02_disk_space.t .. Dubious, test returned 2 (wstat 512, 0x200) Failed 2/8 subtests t/02_fsm_pages.t ... ok t/02_fsm_relations.t ... ok t/02_hitratio.t ok t/02_last_analyze.t ok t/02_last_vacuum.t . ok t/02_listener.t ok t/02_locks.t ... ok t/02_logfile.t . ok t/02_new_version_bc.t .. skipped: Skipped because environment variable SKIP_NETWORK_TESTS is set t/02_new_version_box.t . skipped: Skipped because environment variable SKIP_NETWORK_TESTS is set t/02_new_version_cp.t .. skipped: Skipped because environment variable SKIP_NETWORK_TESTS is set t/02_new_version_pg.t .. skipped: Skipped because environment variable SKIP_NETWORK_TESTS is set t/02_new_version_tnm.t . skipped: Skipped because environment variable SKIP_NETWORK_TESTS is set t/02_pgagent_jobs.t 1/48 NOTICE: schema "pgagent" does not exist, skipping t/02_pgagent_jobs.t 42/48 NOTICE: drop cascades to 4 other objects DETAIL: drop cascades to table pgagent.pga_job drop cascades to table pgagent.pga_jobstep drop cascades to table pgagent.pga_joblog drop cascades to table pgagent.pga_jobsteplog t/02_pgagent_jobs.t ok t/02_pgbouncer_checksum.t .. ok t/02_prepared_txns.t ... ok t/02_query_runtime.t ... ok t/02_query_time.t .. ok t/02_relation_size.t ... ok t/02_replicate_row.t ... ok t/02_same_schema.t . # Creating database in directory "test_database_check_postgres2" Creating new symlink socket at /tmp/cptesting_socket2 # Creating database in directory "test_database_check_postgres3" Creating new symlink socke
[Pkg-postgresql-public] Bug#876472: marked as done (Updated debconf PO Catalan translation for the package postgresql-common)
Your message dated Thu, 05 Oct 2017 15:24:26 +
with message-id <e1e080g-000aye...@fasolo.debian.org>
and subject line Bug#876472: fixed in postgresql-common 186
has caused the Debian Bug report #876472,
regarding Updated debconf PO Catalan translation for the package
postgresql-common
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.)
--
876472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-common
Version: 184
Severity: wishlist
Tag: i10n
This is an updated version of the Catalan debconf PO file.
Thanks!
I. De Marchi# postgresql-common po-debconf translation to Catalan
# Copyright (C) 2006 Software in the Public Interest, SPI Inc.
# This file is distributed under the same license as the postgresql-common
# package.
# Innocent De Marchi <tangram.pe...@gmail.com>, 2011, 2017.
#
msgid ""
msgstr ""
"Project-Id-Version: postgresql-common 184\n"
"Report-Msgid-Bugs-To: postgresql-com...@packages.debian.org\n"
"POT-Creation-Date: 2016-03-05 11:47+0100\n"
"PO-Revision-Date: 2017-09-07 18:59+0200\n"
"Last-Translator: Innocent De Marchi <tangram.pe...@gmail.com>\n"
"Language-Team: Catalan <debian-l10n-cata...@lists.debian.org>\n"
"Language: ca\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.0.3\n"
#. Type: error
#. Description
#: ../postgresql-common.templates:1001
msgid "Obsolete major version ${old}"
msgstr "Versió principal ${old} obsoleta"
#. Type: error
#. Description
#: ../postgresql-common.templates:1001
msgid ""
"The PostgreSQL version ${old} is obsolete, but the server or client packages "
"are still installed. Please install the latest packages (postgresql-"
"${latest} and postgresql-client-${latest}) and upgrade the existing "
"${oldversion} clusters with pg_upgradecluster (see manpage)."
msgstr ""
"La versió de «PostgreSQL» ${old} és obsoleta, però el paquet del client o "
"del servidor encara estan instal·lats. Heu d'instal·lar les darreres "
"versions dels paquets (postgresql-${latest} i postgresql-client-${latest}) i "
"actualitzar els clústers de la versió ${oldversion} amb l'ordre "
"«pg_upgradecluster» (consulteu la pà gina del manual)."
#. Type: error
#. Description
#: ../postgresql-common.templates:1001
msgid ""
"Please be aware that the installation of postgresql-${latest} will "
"automatically create a default cluster ${latest}/main. If you want to "
"upgrade the ${old}/main cluster, you need to remove the already existing "
"${latest} cluster (pg_dropcluster --stop ${latest} main, see manpage for "
"details)."
msgstr ""
"Tingueu en present que la instal lació de postgresql-${latest} generarà "
"automà ticament un clúster pre-determinat ${latest}/main. Heu d'eliminar el "
"clúster ${latest} existent («pg_dropcluster --stop ${latest}) si desitjau "
"actualitzar el clúster ${old}/main, consulteu la pà gina de manual per "
"conèixer els detalls."
#. Type: error
#. Description
#: ../postgresql-common.templates:1001
msgid ""
"The old server and client packages are no longer supported. After the "
"existing clusters are upgraded, the postgresql-${old} and postgresql-client-"
"${old} packages should be removed."
msgstr ""
"Ja no se dona suport als paquets antics de client i servidor. Haureu "
"d'eliminar els paquets postgresql-${old} i postgresql-client-${old} després "
"d'actualitzar els clústers que tingui."
#. Type: error
#. Description
#: ../postgresql-common.templates:1001
msgid ""
"Please see /usr/share/doc/postgresql-common/README.Debian.gz for details."
msgstr ""
"Consulteu « /usr/share/doc/postgresql-common/README.Debian.gz» pels detalls."
#. Type: boolean
#. Description
#: ../postgresql-common.templates:2001
msgid "Enable SSL by default in new PostgreSQL clusters?"
msgstr "Permet SSL de forma predeterminada en clústers PostgreSQL nous?"
#. Type: boolean
#. Description
#: ../postgresql-common.templates:2001
msgid ""
"PostgreSQL support
[Pkg-postgresql-public] Processed: limit source to postgresql-common, tagging 876472
Processing commands for cont...@bugs.debian.org: > limit source postgresql-common Limiting to bugs with field 'source' containing at least one of 'postgresql-common' Limit currently set to 'source':'postgresql-common' > tags 876472 + pending Bug #876472 [postgresql-common] Updated debconf PO Catalan translation for the package postgresql-common Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 876472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#876865: marked as done (pgsphere FTBFS with PostgreSQL 10)
Your message dated Wed, 27 Sep 2017 22:00:13 +
with message-id <e1dxknj-0004k8...@fasolo.debian.org>
and subject line Bug#876865: fixed in pgsphere 1.1.1+2017.08.30-1
has caused the Debian Bug report #876865,
regarding pgsphere FTBFS with PostgreSQL 10
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.)
--
876865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pgsphere
Version: 1.1.1+2017.08.29-1
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pgsphere.html
...
fakeroot debian/rules clean
pg_buildext checkcontrol
--- debian/control 2017-08-29 02:10:32.0 -1200
+++ debian/control.heKi5w 2017-09-23 12:13:25.840962887 -1200
@@ -12,12 +12,12 @@
Vcs-Browser: https://anonscm.debian.org/cgit/pkg-postgresql/pgsphere.git
Vcs-Git: https://anonscm.debian.org/cgit/pkg-postgresql/pgsphere.git
-Package: postgresql-9.6-pgsphere
+Package: postgresql-10-pgsphere
Architecture: any
-Depends: postgresql-9.6,
+Depends: postgresql-10,
${misc:Depends},
${shlibs:Depends}
-Description: Spherical data types for PostgreSQL 9.6
+Description: Spherical data types for PostgreSQL 10
PgSphere, an extension for PostgreSQL, aims at providing uniform
access to spherical data. It allows for a fast search and analysis for
objects with spherical attributes in geographical, astronomical, or
@@ -27,5 +27,5 @@
data of geographical objects around the world and astronomical data
collections like star and other catalogues.
.
- This package provides a module for PostgreSQL 9.6.
+ This package provides a module for PostgreSQL 10.
Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
updatecontrol'.
If you are seeing this message in a buildd log, a sourceful upload is required.
/usr/share/postgresql-common/pgxs_debian_control.mk:9: recipe for target
'debian/control' failed
make: *** [debian/control] Error 1
--- End Message ---
--- Begin Message ---
Source: pgsphere
Source-Version: 1.1.1+2017.08.30-1
We believe that the bug you reported is fixed in the latest version of
pgsphere, 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 876...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher <oleb...@debian.org> (supplier of updated pgsphere 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: SHA512
Format: 1.8
Date: Wed, 27 Sep 2017 09:15:15 +0200
Source: pgsphere
Binary: postgresql-pgsphere
Architecture: source amd64
Version: 1.1.1+2017.08.30-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Ole Streicher <oleb...@debian.org>
Description:
postgresql-pgsphere - Spherical data types for PostgreSQL
Closes: 876865
Changes:
pgsphere (1.1.1+2017.08.30-1) unstable; urgency=medium
.
[ Markus Nullmeier ]
* New upstream version 1.1.1+2017.08.30
* updated upstream references
.
[ Ole Streicher ]
* Create a single package for all PostgreSQL versions
* Rebuild against postgresql-10. Closes: #876865
Checksums-Sha1:
a92fbfa4d776f4c4ac72b4c42e77e9b93624800c 2200 pgsphere_1.1.1+2017.08.30-1.dsc
7521508a531ab9f8f06d4d17d8b843f7b40b4409 445684
pgsphere_1.1.1+2017.08.30.orig.tar.gz
b50057346539341138a367b689e09248923fd18e 2788
pgsphere_1.1.1+2017.08.30-1.debian.tar.xz
ed96c92b1825948c9ac80e2797da38e461f8ef34 7596
pgsphere_1.1.1+2017.08.30-1_amd64.buildinfo
b2f44586cdf5ca484c6aa879d037d126c56e91cb 156038
postgresql-pgsphere-dbgsym_1.1.1+2017.08.30-1_amd64.deb
944e9d53b68f36de356ceffa18d2ab4efcea0714 73582
postgresql-pgsphere_1.1.1+2017.08.30-1_amd64.deb
Checksums-Sha256:
dab30d159726f9b97e8004ba710ffa3fedf2feafe791f096110cf27e7568428f 2200
pgsphere_1.1.1+2017.08.30-1.dsc
3eba2b16f726078d6ae57297ff18c4fef5f97fceefd3bbe131068944db753d17 445684
pgsphere_1.1.1+2017.08.30.orig.tar.gz
fd40327ad943ba413d45f4d84533a35db62806dd7e2e56b2501fdd60ddb233b0 2788
pgsphere_1.1.1+2017.08.30-1.debian.tar.xz
58c66bdf19835471c857c1a270d41a91e5f83819ba10f
[Pkg-postgresql-public] Bug#876788: marked as done (postgresql-q3c FTBFS with PostgreSQL 10)
Your message dated Wed, 27 Sep 2017 15:00:17 +
with message-id <e1dxdov-0001aj...@fasolo.debian.org>
and subject line Bug#876788: fixed in postgresql-q3c 1.5.0-3
has caused the Debian Bug report #876788,
regarding postgresql-q3c FTBFS with PostgreSQL 10
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.)
--
876788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresql-q3c
Version: 1.5.0-2
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/postgresql-q3c.html
...
fakeroot debian/rules clean
pg_buildext checkcontrol
--- debian/control 2017-09-05 19:02:30.0 -1200
+++ debian/control.chBILN 2017-09-23 12:16:00.910794389 -1200
@@ -11,17 +11,17 @@
Vcs-Browser: https://anonscm.debian.org/cgit/pkg-postgresql/postgresql-q3c.git
Vcs-Git: https://anonscm.debian.org/cgit/pkg-postgresql/postgresql-q3c.git
-Package: postgresql-9.6-q3c
+Package: postgresql-10-q3c
Architecture: any
-Depends: postgresql-9.6,
+Depends: postgresql-10,
${misc:Depends},
${shlibs:Depends}
-Description: PostgreSQL 9.6 extension used for indexing the sky
+Description: PostgreSQL 10 extension used for indexing the sky
Q3C, an extension for PostgreSQL, is designed for the work with large
astronomical catalogues or any catalogs of objects on the sphere.
.
This extension allows a user to perform fast circular, elliptical or
polygonal searches on the sky as well as fast cross-matches.
.
- This package provides a module for PostgreSQL 9.6.
+ This package provides a module for PostgreSQL 10.
Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
updatecontrol'.
If you are seeing this message in a buildd log, a sourceful upload is required.
/usr/share/postgresql-common/pgxs_debian_control.mk:9: recipe for target
'debian/control' failed
make: *** [debian/control] Error 1
--- End Message ---
--- Begin Message ---
Source: postgresql-q3c
Source-Version: 1.5.0-3
We believe that the bug you reported is fixed in the latest version of
postgresql-q3c, 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 876...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher <oleb...@debian.org> (supplier of updated postgresql-q3c 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: SHA512
Format: 1.8
Date: Mon, 25 Sep 2017 21:37:30 +0200
Source: postgresql-q3c
Binary: postgresql-q3c
Architecture: source amd64
Version: 1.5.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Ole Streicher <oleb...@debian.org>
Description:
postgresql-q3c - PostgreSQL extension used for indexing the sky
Closes: 876788
Changes:
postgresql-q3c (1.5.0-3) unstable; urgency=medium
.
* Create a single package for all PostgreSQL versions
* Rebuild against postgresql-10. Closes: #876788
Checksums-Sha1:
1ca46140b622609f41ac55e7f7d1af0ee6efb26b 2199 postgresql-q3c_1.5.0-3.dsc
4a3b1371408b7b25a6436026c631992bd66da918 3812
postgresql-q3c_1.5.0-3.debian.tar.xz
26841e8fffcf1524737d38f42f040728b8d53340 64118
postgresql-q3c-dbgsym_1.5.0-3_amd64.deb
ebc61f3dccfc5963c75f8d5b154da0df8afcf1aa 7446
postgresql-q3c_1.5.0-3_amd64.buildinfo
5fde141502444cd5b9baf080c3a56cf056f2c88b 61252 postgresql-q3c_1.5.0-3_amd64.deb
Checksums-Sha256:
0b89031eafb12bf765fb6501faec1cdc3ef14fa568f5f72578c7ff680d18682c 2199
postgresql-q3c_1.5.0-3.dsc
a101f26928d1cc96fce52ad8c463a22edfa2ed5ad87295f75b9883b7804378ea 3812
postgresql-q3c_1.5.0-3.debian.tar.xz
89eca0ed3c7d835d1e9c18a4ddecf51be89e6fc08d72f8be59b3eca58faefc5e 64118
postgresql-q3c-dbgsym_1.5.0-3_amd64.deb
85b1ee73a2f05de0d77e21b424f72d4719fcc88e3f04d398040c4de073a5dda7 7446
postgresql-q3c_1.5.0-3_amd64.buildinfo
7169413048d7282afbe8249e65d3494fc0f657693aa568c829f2755dff982fce 61252
postgresql-q3c_1.5.0-3_amd64.deb
Files:
512327c90b340774887aefff2ddd8840 2199 database optional
postgresql-q3c_1.5.0-3.dsc
ff2cc92fd2e1aa59ea8da222d1d2f740 3812 database optional
[Pkg-postgresql-public] Bug#876863: marked as done (powa-archivist FTBFS with PostgreSQL 10)
Your message dated Tue, 26 Sep 2017 15:03:20 +0300
with message-id <20170926120320.xtiq7bj6q26w5rg5@localhost>
and subject line Fixed package is in NEW
has caused the Debian Bug report #876863,
regarding powa-archivist FTBFS with PostgreSQL 10
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.)
--
876863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: powa-archivist
Version: 3.1.0-1
Severity: serious
Tags: buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/powa-archivist.html
...
fakeroot debian/rules clean
pg_buildext checkcontrol
--- debian/control 2016-09-26 08:50:34.0 -1200
+++ debian/control.jfmlot 2018-10-26 17:48:06.059800363 -1200
@@ -10,10 +10,10 @@
Vcs-Browser: https://github.com/credativ/powa-archivist.git
Vcs-Git: https://github.com/credativ/powa-archivist.git -b debian
-Package: postgresql-9.6-powa
+Package: postgresql-10-powa
Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-9.6
-Description: PostgreSQL Workload Analyzer -- PostgreSQL 9.6 extension
+Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-10
+Description: PostgreSQL Workload Analyzer -- PostgreSQL 10 extension
This package contains the core extension of the PoWA project, a PostgreSQL
Workload Analyzer that gathers performance stats and provides real-time charts
and graphs to help monitor and tune your PostgreSQL servers.
Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
updatecontrol'.
If you are seeing this message in a buildd log, a sourceful upload is required.
/usr/share/postgresql-common/pgxs_debian_control.mk:9: recipe for target
'debian/control' failed
make: *** [debian/control] Error 1
--- End Message ---
--- Begin Message ---
Version: 3.1.1
https://ftp-master.debian.org/new/powa-archivist_3.1.1.html
Changed-By: Christoph Berg <christoph.b...@credativ.de>
Description:postgresql-10-powa - PostgreSQL Workload Analyzer -- PostgreSQL
10 extension
Changes:powa-archivist (3.1.1) unstable; urgency=medium
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed--- End Message ---
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#876843: marked as done (ip4r FTBFS with PostgreSQL 10)
Your message dated Tue, 26 Sep 2017 12:51:26 +0300
with message-id <20170926095126.sww7lqb7ilhannuo@localhost>
and subject line Fix is in NEW
has caused the Debian Bug report #876843,
regarding ip4r FTBFS with PostgreSQL 10
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.)
--
876843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ip4r
Version: 2.1.1-1
Severity: serious
Tags: buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ip4r.html
...
fakeroot debian/rules clean
pg_buildext checkcontrol
--- debian/control 2016-09-21 05:20:18.0 -1200
+++ debian/control.SqwXQ9 2018-10-26 16:41:04.140097914 -1200
@@ -10,10 +10,10 @@
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-postgresql/ip4r.git
XS-Testsuite: autopkgtest
-Package: postgresql-9.6-ip4r
+Package: postgresql-10-ip4r
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-9.6
-Description: IPv4 and IPv6 types for PostgreSQL 9.6
+Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-10
+Description: IPv4 and IPv6 types for PostgreSQL 10
This PostgreSQL module provides several data types which can contain
single IPv4 or IPv6 addresses or a range of such addresses.
.
Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
updatecontrol'.
If you are seeing this message in a buildd log, a sourceful upload is required.
/usr/share/postgresql-common/pgxs_debian_control.mk:9: recipe for target
'debian/control' failed
make: *** [debian/control] Error 1
--- End Message ---
--- Begin Message ---
Version: 2.2-2
https://ftp-master.debian.org/new/ip4r_2.2-2.html
Changed-By: Christoph Berg <m...@debian.org>
Description:postgresql-10-ip4r - IPv4 and IPv6 types for PostgreSQL 10
Changes:
ip4r (2.2-2) unstable; urgency=medium
* Upload for PostgreSQL 10.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed--- End Message ---
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: Not a problem in stretch
Processing commands for cont...@bugs.debian.org: > tags 876842 buster sid Bug #876842 [src:orafce] orafce FTBFS with PostgreSQL 10 Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 876842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#868367: marked as done (postgresql-common: standby cannot start with "recovery.conf file found in config directory")
Your message dated Thu, 21 Sep 2017 10:37:16 + with message-id <e1duyr6-000alw...@fasolo.debian.org> and subject line Bug#868367: fixed in postgresql-common 185 has caused the Debian Bug report #868367, regarding postgresql-common: standby cannot start with "recovery.conf file found in config directory" 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.) -- 868367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: postgresql-common Version: 183.pgdg80+1 Severity: important Dear Maintainer, I update postgresql-common and restart standby. Now my standby cannot start with message: "recovery.conf file found in config directory". Yes, I have recovery.conf in /etc, this is intentional. I symlink it from data dir. -- System Information: Debian Release: 8.8 Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/56 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages postgresql-common depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.56 ii init-system-helpers 1.22 ii lsb-base 4.1+Debian13+nmu1 ii postgresql-client-common 183.pgdg80+1 ii procps2:3.3.9-9 ii ssl-cert 1.0.35 ii ucf 3.0030 Versions of packages postgresql-common recommends: ii logrotate 3.8.7-1+b1 Versions of packages postgresql-common suggests: ii libjson-perl 2.61-1 -- debconf information excluded -- Sergey Burladyan --- End Message --- --- Begin Message --- Source: postgresql-common Source-Version: 185 We believe that the bug you reported is fixed in the latest version of postgresql-common, 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 868...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg <christoph.b...@credativ.de> (supplier of updated postgresql-common 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: Thu, 21 Sep 2017 12:07:30 +0200 Source: postgresql-common Binary: postgresql-common postgresql-client-common postgresql-server-dev-all postgresql postgresql-client postgresql-doc postgresql-contrib postgresql-all Architecture: source all Version: 185 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public@lists.alioth.debian.org> Changed-By: Christoph Berg <christoph.b...@credativ.de> Description: postgresql - object-relational SQL database (supported version) postgresql-all - metapackage depending on all PostgreSQL server packages postgresql-client - front-end programs for PostgreSQL (supported version) postgresql-client-common - manager for multiple PostgreSQL client versions postgresql-common - PostgreSQL database-cluster manager postgresql-contrib - additional facilities for PostgreSQL (supported version) postgresql-doc - documentation for the PostgreSQL database management system postgresql-server-dev-all - extension build tool for multiple PostgreSQL versions Closes: 868367 Changes: postgresql-common (185) unstable; urgency=medium . * Team upload. . [ Christoph Berg ] * Revert "Error out if a recovery.conf file is found in /etc/postgresql". It caused too many false positives for setups where a recovery.conf template is located in the etc directory. (Closes: #868367) * Bump default PostgreSQL version to 10. . [ Marco Nenciarini ] * supported-versions: correctly detect version 10 when using 'installed'. Checksums-Sha1: de69816b91971087e81dfdef5aa72bb04b16b824 2339 postgresql-common_185.dsc fc9909fab382e79c95883e6808ebffea1ea74d9c 204188 postgresql-common_185.tar.xz a02caf267a753d504b2e70c14d8e491afe8576af 57146 postgresql-all_10+185_all.deb 9106a0a9dcccf08f6fb536d0fb91cc00e350bff3 80778 postgresql-client-common_185_all.deb 590bc5af89e8b8b4064d7e2be83ddcfc28c41264 57066 postgresql-client_10+185_all.deb 705891e85a971d80c41c193
[Pkg-postgresql-public] Processed: found 876293 in 184
Processing commands for cont...@bugs.debian.org: > found 876293 184 Bug #876293 [postgresql-common] postgresql-common: pg_upgradecluster needs to copy wal_level earlier Marked as found in versions postgresql-common/184. > thanks Stopping processing here. Please contact me if you need assistance. -- 876293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processed: limit source to slony1-2, tagging 852650
Processing commands for cont...@bugs.debian.org: > limit source slony1-2 Limiting to bugs with field 'source' containing at least one of 'slony1-2' Limit currently set to 'source':'slony1-2' > tags 852650 + pending Bug #852650 [slony1-2] slony1-2: Recommend time-daemon as an alternative to ntp Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 852650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#874427: marked as done (/usr/bin/pg_config in multiple packages)
Your message dated Wed, 6 Sep 2017 19:53:40 +0200 with message-id <20170906175340.x53apufhpvif5...@msg.df7cb.de> and subject line Re: Bug#874427: /usr/bin/pg_config in multiple packages has caused the Debian Bug report #874427, regarding /usr/bin/pg_config in multiple packages 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.) -- 874427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: postgresql-common Version: 165+deb8u2 Both postgresql-common and libpq-dev install the file /usr/bin/pg_config . That's a bug, isn't it? dpkg --install seems to think so. This was not a problem for me before an attempted update a few days ago; Now I have broken dependencies that I cannot fix because I cannot install the current libpq-dev because of the file conflict. I don't know what changed. -- Bryan Henderson San Jose, California --- End Message --- --- Begin Message --- Re: Bryan Henderson 2017-09-06 <49166.bry...@giraffe-data.com> > The only thing I can think of that I did out of the ordinary to cause this is > that I don't normally update my system by installing all the new packages at > once; I install them a few at a time to limit the damage if something breaks. > So I may have updated Postgres packages in a different order than is usual. The packages should actually cope with that. I don't think we can really figure out now what had happened when you got into that situation, given everything works again, so I'll close the bug now. > Anyway, I'm glad to know how this diversion works so if this happens again, I > can repair it. The logic there hasn't changed for years, and your report was the first time I've heard of problems with it, so it's quite unlikely you'll hit it again. Hopefully :) Thanks for reporting! Christoph--- End Message --- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
