Source: vmem
Version: 1.8-1
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[3]: Entering directory '/<<PKGBUILDDIR>>/doc'
> ../utils/md2man.sh libvmem/libvmem.7.md default.man generated/libvmem.7;
> ../utils/md2man.sh libvmmalloc/libvmmalloc.7.md default.man
> generated/libvmmalloc.7;
> ../utils/md2man.sh libvmem/vmem_create.3.md default.man
> generated/vmem_create.3; ../utils/md2man.sh libvmem/vmem_malloc.3.md
> default.man generated/vmem_malloc.3;
> man ./generated/libvmem.7 > generated/libvmem.7.txt
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> make[3]: *** [Makefile:103: generated/libvmem.7.txt] Error 3
The full build log is available from:
http://qa-logs.debian.net/2020/06/20/vmem_1.8-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.
