Source: charliecloud Version: 0.31-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230216 ftbfs-bookworm
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat > -Werror=format-security -std=c99 -Wall -Werror -c -o ch-ssh.o ch-ssh.c > rm -f ch-run-oci > sed -E 's|%PYTHON_SHEBANG%|/usr/bin/env python3|' < ch-run-oci.py.in > > ch-run-oci > chmod +rx,-w ch-run-oci # respects umask > rm -f ch-image > sed -E 's|%PYTHON_SHEBANG%|/usr/bin/env python3|' < ch-image.py.in > ch-image > chmod +rx,-w ch-image # respects umask > In file included from ch_fuse.c:33: > config.h:38: error: "PACKAGE_VERSION" redefined [-Werror] > 38 | #define PACKAGE_VERSION "0.31" > | > In file included from /usr/include/fuse3/fuse_common.h:17, > from /usr/include/fuse3/fuse_lowlevel.h:25, > from /usr/include/squashfuse/ll.h:31, > from ch_fuse.c:31: > /usr/include/fuse3/fuse_config.h:42: note: this is the location of the > previous definition > 42 | #define PACKAGE_VERSION "3.13.1" > | > cc1: all warnings being treated as errors > make[3]: *** [Makefile:638: ch_run-ch_fuse.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/02/16/charliecloud_0.31-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230216&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results 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! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
