Source: unicode-screensaver Version: 0.5.2-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ./libtool --tag=CC --mode=link gcc -pedantic -Wall > -Wstrict-prototypes -Wnested-externs -Wmissing-prototypes > -Wno-overlength-strings -Wdeclaration-after-statement -g -O2 -o unicode > unicode.o screenhack.o visual.o yarandom.o resources.o usleep.o fps.o -lXft > -lX11 -lfontconfig -lfreetype -lXmu -lXt -lX11 -lXt -lX11 > libtool: link: gcc -pedantic -Wall -Wstrict-prototypes -Wnested-externs > -Wmissing-prototypes -Wno-overlength-strings -Wdeclaration-after-statement -g > -O2 -o unicode unicode.o screenhack.o visual.o yarandom.o resources.o > usleep.o fps.o -lXft -lfontconfig -lfreetype -lXmu -lXt -lX11 > /usr/bin/ld: screenhack.o:/<<PKGBUILDDIR>>/hacks/screenhack.c:133: multiple > definition of `progclass'; unicode.o:/<<PKGBUILDDIR>>/unicode.c:166: first > defined here > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/08/02/unicode-screensaver_0.5.2-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.
