Source: gimp Version: 2.10.22-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > find debian/tmp -name '*.la' -print -delete > debian/tmp/usr/lib/libgimpbase-2.0.la > debian/tmp/usr/lib/libgimpconfig-2.0.la > debian/tmp/usr/lib/libgimp-2.0.la > debian/tmp/usr/lib/libgimpmodule-2.0.la > debian/tmp/usr/lib/libgimpmath-2.0.la > debian/tmp/usr/lib/libgimpthumb-2.0.la > debian/tmp/usr/lib/libgimpwidgets-2.0.la > debian/tmp/usr/lib/libgimpui-2.0.la > debian/tmp/usr/lib/libgimpcolor-2.0.la > debian/tmp/usr/lib/gimp/2.0/modules/libdisplay-filter-color-blind.la > debian/tmp/usr/lib/gimp/2.0/modules/libdisplay-filter-high-contrast.la > debian/tmp/usr/lib/gimp/2.0/modules/libcontroller-midi.la > debian/tmp/usr/lib/gimp/2.0/modules/libdisplay-filter-gamma.la > debian/tmp/usr/lib/gimp/2.0/modules/libcolor-selector-cmyk.la > debian/tmp/usr/lib/gimp/2.0/modules/libcolor-selector-wheel.la > debian/tmp/usr/lib/gimp/2.0/modules/libcontroller-linux-input.la > debian/tmp/usr/lib/gimp/2.0/modules/libcolor-selector-water.la > debian/tmp/usr/lib/gimp/2.0/modules/libdisplay-filter-clip-warning.la > dh_install > dh_install: warning: Cannot find (any matches for) > "usr/lib/gimp/2.0/plug-ins/file-heif" (tried in ., debian/tmp) > > dh_install: warning: gimp missing files: usr/lib/gimp/2.0/plug-ins/file-heif > dh_install: error: missing files, aborting > make[1]: *** [debian/rules:44: override_dh_install] Error 25 The full build log is available from: http://qa-logs.debian.net/2020/12/26/gimp_2.10.22-2_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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. 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.
