Hi On 2021-02-15 23:51:12, Jussi Pakkanen wrote: > On Mon, 15 Feb 2021 at 23:21, Sebastian Ramacher <sramac...@debian.org> wrote: > > > Silently breaking hardening build flags of roughly 430 packages is > > definitely a large and disruptive change. > > The rc was uploaded to experimental a week ago so that people could > use it to flush out problems like these. Apparently no-one did. Would > it be possible to set up an automatic gating system of some kind for > build-essential packages so these sort of things will never happen > again in the future?
I guess you could do some or all of the following: * Add a autopkgtest to meson that builds a package. This test could also check whether all flags from dpkg-buildflags are preserved during the build with blhc. After some time the autopkgtest results for the package in experimental would appear at https://release.debian.org/britney/pseudo-excuses-experimental.html. * Not automatic, but you could talk to lucas to run a test build of all reverse dependencies on AWS. Again check with blhc if all flags are preserved. But even if all of the above would have been done, uploading a new upstream version of a build system to unstable would have been inappropriate at this stage. Cheers -- Sebastian Ramacher
