This was an expected failure due to new incompatible tool packages, and same goes for all the other Apertium-related FTBFS.
How can one prevent such a slew of superfluous automatic bugs from being filed? Is there a way to mark packages as "will be updated, just waiting for deps in NEW queue"? -- Tino Didriksen On Sat, 26 Mar 2022 at 22:06, Lucas Nussbaum <lu...@debian.org> wrote: > Source: apertium-spa-arg > Version: 0.5.0-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220326 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > checking for gawk... (cached) gawk > > checking for pkg-config... /usr/bin/pkg-config > > checking pkg-config is at least version 0.9.0... yes > > checking for apertium >= 3.7.1... yes > > checking for apertium-lex-tools >= 0.2.7... no > > configure: error: Package requirements (apertium-lex-tools >= 0.2.7) > were not met > > > > No package 'apertium-lex-tools' found > > > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > > installed software in a non-standard prefix. > > > > Alternatively, you may set the environment variables > APERTIUM_LEX_TOOLS_CFLAGS > > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > > See the pkg-config man page for more details. > > make[1]: *** [debian/rules:20: override_dh_auto_configure] Error 1 > > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > > > The full build log is available from: > http://qa-logs.debian.net/2022/03/26/apertium-spa-arg_0.5.0-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! > > 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 > mine > so that we can identify if something relevant changed in the meantime. > > -- > debian-science-maintainers mailing list > debian-science-maintain...@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers >
