Source: parmap Version: 1.0~rc7-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161021 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<<PKGBUILDDIR>>' > ocamlfind ocamlopt -shared -o parmap.cmxs bytearray_stubs.o setcore_stubs.o > bytearray.cmx parmap_utils.cmx parmap.cmx > ocamlfind remove parmap > ocamlfind: [WARNING] No such directory: /usr/local/lib/ocaml/4.02.3/parmap > ocamlfind install parmap META bytearray.cmi parmap_utils.cmi parmap.cmi > setcore.cmi parmap.cma parmap.cmxa parmap.cmxs *.a *.mli bytearray_stubs.o > setcore_stubs.o *.so > ocamlfind: Cannot mkdir /usr/local/lib/ocaml/4.02.3/parmap: Permission denied > Makefile:34: recipe for target 'install' failed > make[2]: *** [install] Error 2 If the failure looks somehow time/timezone related: Note that this rebuild was performed without the 'tzdata' package installed in the chroot. tzdata used be (transitively) part of build-essential, but it no longer is. If this package requires it to build, it should be added to build-depends. For the release team's opinion on this, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185 If the failure looks LSB-related: similarly to tzdata, lsb-base is not installed in the build chroot. The full build log is available from: http://aws-logs.debian.net/2016/10/21/parmap_1.0~rc7-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.
