Control: retitle -1 ubuntu-dev-tools: FTBFS because of ./run-linters during build
Hello, On Fri, Feb 17, 2023 at 07:55:22AM +0100, Lucas Nussbaum wrote: > Source: ubuntu-dev-tools > Version: 0.192 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20230216 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > make[1]: Entering directory '/<<PKGBUILDDIR>>' > > ./run-linters [...] Running linters during build seems like an equally bad idea as using -Werror in release builds! When ever a linter changes opinion of something the package will start to FTBFS (just like when gcc gains a new warning and code with -Werror starts to FTBFS). I hope removing `./run-linters` from debian/rules is a simple fix for this issue (and future ones). Run the linters *before* release, not on every (re)build after release. (Or possibly catch this via an autopkgtest that would trigger when a new version of a dependency is uploaded. But I don't think linter package maintainers would appreciate you blocking their package from testing migration until you've uploaded a relinted version of your package.) Regards, Andreas Henriksson