Control: tag -1 +moreinfo Hello,
I just tried to reproduce the FTBFS and failed. rake is defined as build-dependency and correctly pulled in according to linked the build logs. My best guess is that rake 12.3.1-2 had some bug that got fixed in 12.3.1-3. Lucas, could you trigger another rebuild to see whether this got fixed by the latest rake upload? In any case, it doesn't look like a bug in mustache.js package to me. Cheers, jonas On Wed, 2 May 2018 22:51:57 +0200 Lucas Nussbaum <lu...@debian.org> wrote: > Source: mustache.js > Version: 2.3.0-2 > Severity: serious > Tags: buster sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20180502 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): > > debian/rules build > > dh build --builddirectory=/<<PKGBUILDDIR>>/build > > dh_update_autotools_config -O--builddirectory=/<<PKGBUILDDIR>>/build > > dh_auto_configure -O--builddirectory=/<<PKGBUILDDIR>>/build > > debian/rules override_dh_auto_build > > make[1]: Entering directory '/<<PKGBUILDDIR>>' > > rake jquery > > make[1]: rake: Command not found > > make[1]: *** [debian/rules:13: override_dh_auto_build] Error 127 > > The full build log is available from: > http://aws-logs.debian.net/2018/05/02/mustache.js_2.3.0-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! > > 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. > >
signature.asc
Description: OpenPGP digital signature
