Your message dated Sat, 29 Mar 2014 18:01:19 +0200
with message-id <[email protected]>
and subject line Patch applied and uploaded, close the bug
has caused the Debian Bug report #738382,
regarding memcachedb: FTBFS: bdb.c:208:23: error: 'DB_ENV' has no member named
'repmgr_set_local_site'
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 [email protected]
immediately.)
--
738382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738382
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: memcachedb
Version: 1.2.0-10
Severity: serious
Tags: jessie sid
User: [email protected]
Usertags: qa-ftbfs-20140208 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I/usr/local/BerkeleyDB.4.7/include
> -D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4
> -Wformat -Werror=format-security -c -o bdb.o bdb.c
> bdb.c: In function 'bdb_env_init':
> bdb.c:208:23: error: 'DB_ENV' has no member named 'repmgr_set_local_site'
> if ((ret = env->repmgr_set_local_site(env,
> bdb_settings.rep_localhost, bdb_settings.rep_localport, 0)) != 0) {
> ^
> bdb.c:215:27: error: 'DB_ENV' has no member named 'repmgr_add_remote_site'
> if ((ret = env->repmgr_add_remote_site(env,
> bdb_settings.rep_remotehost, bdb_settings.rep_remoteport, NULL, 0)) != 0) {
> ^
> make[3]: *** [bdb.o] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/02/08/memcachedb_1.2.0-10_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 1.2.0-11
Forgot to close the bug in the changelog. This has been fixed with the
patch provided by Peter Michael Green.
--
Arto Jantunen
--- End Message ---
