Bug#954620: apertium-es-gl: FTBFS: mkdir: cannot create directory ‘/<<PKGBUILDDIR>>/debian/apertium-es-gl/usr/share/apertium/modes/’: No such file or directory

Lucas Nussbaum lucas at debian.org
Sun Mar 22 08:27:17 GMT 2020


Source: apertium-es-gl
Version: 1.0.8~r57542-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 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>>'
> make[2]: Nothing to be done for 'install-exec-am'.
> apertium-gen-modes modes.xml
> apertium-gen-modes modes.xml
> apertium-gen-modes modes.xml apertium-es-gl
> test -d /<<PKGBUILDDIR>>/debian/apertium-es-gl/usr/share/apertium/modes/ || mkdir /<<PKGBUILDDIR>>/debian/apertium-es-gl/usr/share/apertium/modes/
> mkdir: cannot create directory ‘/<<PKGBUILDDIR>>/debian/apertium-es-gl/usr/share/apertium/modes/’: No such file or directory
> make[2]: *** [Makefile:806: install-data-local] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/apertium-es-gl_1.0.8~r57542-3_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.



More information about the debian-science-maintainers mailing list