Source: sipwitch Version: 1.2.4-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. > -D_FORTIFY_SOURCE=2 -I../inc -DOSIP_MT -DHAVE_PTHREAD -Wno-long-long > -DNEW_STDCPP -pthread -fno-check-new -finline -fvisibility=hidden > -DUCOMMON_VISIBILITY=1 -g -O2 -fstack-protector --param=ssp-buffer-size=4 > -Wformat -Werror=format-security -Wall -c -o service.lo service.cpp > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -I../inc > -DOSIP_MT -DHAVE_PTHREAD -Wno-long-long -DNEW_STDCPP -pthread -fno-check-new > -finline -fvisibility=hidden -DUCOMMON_VISIBILITY=1 -g -O2 -fstack-protector > --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c > service.cpp -fPIC -DPIC -o .libs/service.o > In file included from service.cpp:20:0: > ../inc/sipwitch/service.h: In member function 'void > sipwitch::service::keyclone::reset(const char*)': > ../inc/sipwitch/service.h:111:14: error: 'id' was not declared in this scope > ../inc/sipwitch/service.h: In static member function 'static bool > sipwitch::service::isLinked(sipwitch::service::keynode*)': > ../inc/sipwitch/service.h:263:23: error: 'sipwitch::service::keynode' has no > member named 'isLeaf' > service.cpp: In member function 'void > sipwitch::service::keyclone::splice(sipwitch::service::keyclone*)': > service.cpp:214:5: error: 'parent' was not declared in this scope > service.cpp:216:28: error: 'class sipwitch::service::keyclone' has no member > named 'child' > make[3]: *** [service.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/sipwitch_1.2.4-1_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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
