Source: filtlong Version: 0.2.0-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 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>>' > g++ -std=c++11 -O3 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o src/main.o > src/main.cpp > g++ -std=c++11 -O3 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o src/kmers.o > src/kmers.cpp > g++ -std=c++11 -O3 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o src/misc.o > src/misc.cpp > g++ -std=c++11 -O3 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o > src/arguments.o src/arguments.cpp > g++ -std=c++11 -O3 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o src/read.o > src/read.cpp > g++ -std=c++11 -O3 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -o bin/filtlong > src/main.o src/kmers.o src/misc.o src/arguments.o src/read.o -lz -Wl,-z,relro > -Wl,-z,now > make[2]: Leaving directory '/<<PKGBUILDDIR>>' > markdown_py -f README.html README.md > Traceback (most recent call last): > File "/usr/bin/markdown_py", line 6, in <module> > from pkg_resources import load_entry_point > ModuleNotFoundError: No module named 'pkg_resources' > make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/06/20/filtlong_0.2.0-2_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.
