Source: libtexttools Version: 2.1.0-16 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200402 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<<PKGBUILDDIR>>' > sed ' s%ADAFLAGS%-g", "-O2", "-fdebug-prefix-map=/<<PKGBUILDDIR>>=.", > "-fstack-protector-strong", "-gnatn%; s%CFLAGS%-g", "-O2", > "-fdebug-prefix-map=/<<PKGBUILDDIR>>=.", "-fstack-protector-strong", > "-Wformat", "-Werror=format-security%; s%LDFLAGS%-Wl,-z,relro", > "-Wl,-z,now", "-Wl,--no-undefined", "-Wl,--no-copy-dt-needed-entries", > "-Wl,--no-allow-shlib-undefined%; s%LDLIBS%-lncurses", "-ltinfo%; > s%SOVERSION%10%;' \ > texttools.gpr.sed > texttools.gpr > gprbuild texttools.gpr -j4 -R -v -eS -XKIND=dynamic > gprbuild: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnatprj.so.7: > undefined symbol: system__os_lib__get_os_time_from_string > make[2]: *** [Makefile:79: build-dynamic] Error 127 The full build log is available from: http://qa-logs.debian.net/2020/04/02/libtexttools_2.1.0-16_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.
