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.
<builtin>: 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 ---
