Your message dated Wed, 25 Apr 2018 18:55:46 +0200 with message-id <dadd270c-30d8-8a60-8d6c-d077d2b9d...@pocock.pro> and subject line fixed upstream has caused the Debian Bug report #724305, regarding postbooks: Does not work on postgres 9.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.) -- 724305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724305 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: postbooks Version: 4.0.2-3 Severity: important Tags: upstream Postbooks relies on functionality removed in 9.2. After setting up the quickstart schema, trying to login yields: A System Error occurred at login2.cpp::344: ERROR: column "procpid" does not exist LINE 1: SELECT pg_try_advisory_lock(datid::integer, procpid) ^ QUERY: SELECT pg_try_advisory_lock(datid::integer, procpid) FROM pg_stat_activity WHERE(procpid = pg_backend_pid()) CONTEXT: PL/pgSQL function login(boolean) line 10 at PERFORM (42703) procpid was renamed to pid in 9.2 and is not coming back[1]. Filing as important because 9.1 is still installable (thus possibly not RC), but as the default postgres version is 9.3 this should really be fixed soon. [1] http://www.postgresql.org/message-id/e1t6wsq-0005kn...@wrigleys.postgresql.org -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages postbooks depends on: ii libc6 2.17-92+b1 ii libdmtx0a 0.7.4-1 ii libgcc1 1:4.8.1-10 ii libopenrpt1 3.3.4-4 ii libqt4-designer 4:4.8.5+git121-g2a9ea11+dfsg-1 ii libqt4-help 4:4.8.5+git121-g2a9ea11+dfsg-1 ii libqt4-network 4:4.8.5+git121-g2a9ea11+dfsg-1 ii libqt4-script 4:4.8.5+git121-g2a9ea11+dfsg-1 ii libqt4-scripttools 4:4.8.5+git121-g2a9ea11+dfsg-1 ii libqt4-sql 4:4.8.5+git121-g2a9ea11+dfsg-1 ii libqt4-sql-psql 4:4.8.5+git121-g2a9ea11+dfsg-1 ii libqt4-xml 4:4.8.5+git121-g2a9ea11+dfsg-1 ii libqt4-xmlpatterns 4:4.8.5+git121-g2a9ea11+dfsg-1 ii libqtcore4 4:4.8.5+git121-g2a9ea11+dfsg-1 ii libqtgui4 4:4.8.5+git121-g2a9ea11+dfsg-1 ii libqtwebkit4 2.2.1-6 ii libstdc++6 4.8.1-10 ii qt-assistant-compat 4.6.3-6 ii zlib1g 1:1.2.8.dfsg-1 postbooks recommends no packages. Versions of packages postbooks suggests: pn postbooks-schema-demo <none> pn postbooks-schema-empty <none> ii postbooks-schema-quickstart 4.0.2-1 -- no debconf information
--- End Message ---
--- Begin Message ---Version: 4.5.0 The bug was opened against version 4.0.2-3 The problem is fixed upstream from 4.5.0 onwards according to the compatibility matrix: https://xtupleuniversity.xtuple.com/library/articles/compatibility-matrix
--- End Message ---
