Source: openafs
Version: 1.8.6-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):
> gcc  -Wl,-z,relro -L/usr/lib/x86_64-linux-gnu/heimdal 
> -L/usr/lib/x86_64-linux-gnu/heimdal -g -O   -Damd64_linux26  
> -DFSSYNC_BUILD_SERVER -DFSSYNC_BUILD_CLIENT -g -O2 
> -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -g -O   -I/<<PKGBUILDDIR>>/src/config 
> -I/<<PKGBUILDDIR>>/include -I. -I.   -I/usr/include/heimdal   -o volscan 
> volscan-main.o vol-info.o physio.o ihandle.o \
>       /<<PKGBUILDDIR>>/lib/libcmd.a vlib.a /<<PKGBUILDDIR>>/lib/util.a 
> /<<PKGBUILDDIR>>/lib/libdir.a /<<PKGBUILDDIR>>/lib/librx.a 
> /<<PKGBUILDDIR>>/lib/libafshcrypto_lwp.a /<<PKGBUILDDIR>>/lib/liblwp.a 
> /<<PKGBUILDDIR>>/lib/libsys.a /<<PKGBUILDDIR>>/lib/libacl.a 
> /<<PKGBUILDDIR>>/lib/libopr.a -lroken -lresolv  
> /usr/bin/ld: vlib.a(volume.o):./src/vol/volume.c:128: multiple definition of 
> `vol_io_params'; ihandle.o:./src/vol/ihandle.c:81: first defined here
> /usr/bin/ld: vlib.a(daemon_com.o):./src/vol/daemon_com.c:49: multiple 
> definition of `V_BreakVolumeCallbacks'; 
> vlib.a(fssync-server.o):./src/vol/fssync-server.c:83: first defined here
> gcc -fPIC   -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -g -O   
> -I/<<PKGBUILDDIR>>/src/config -I/<<PKGBUILDDIR>>/include -I. -I.   
> -I/usr/include/heimdal   -o X11windows.o -c X11windows.c
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/openafs_1.8.6-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.

Reply via email to