Source: opam Version: 2.0.5-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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>>/doc' > Entering directory '/<<PKGBUILDDIR>>' > Entering directory '/<<PKGBUILDDIR>>' > rm -rf man > mkdir -p man > dune exec --profile=release -- opam --help=groff > man/opam.1 2> man/err > for i in help admin clean lint source unpin pin switch remote repository env > exec var config upgrade update reinstall uninstall remove install info show > search list init; do\ > dune exec --profile=release -- opam $i --help=groff > man/opam-$i.1 2>> > man/err ; \ > done > dune exec --profile=release -- opam admin --help=groff > man/opam-admin.1 2>> > man/err > for i in cache filter index lint list upgrade; do\ > dune exec --profile=release -- opam admin $i --help=groff > > man/opam-admin-$i.1 2>> man/err ; \ > done > dune exec --profile=release -- opam-installer --help=groff > > man/opam-installer.1 2>> man/err > make[2]: Leaving directory '/<<PKGBUILDDIR>>/doc' > grep: opam.install: No such file or directory > make[1]: *** [Makefile:111: opam-actual.install] Error 2 The full build log is available from: http://qa-logs.debian.net/2020/11/25/opam_2.0.5-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.
