Bug#982865:
On Tue, 9 Mar 2021 at 21:51, Nicholas Brown wrote: > Will 0.57.1 be migrated to unstable? Or perhaps even to testing? > (I'm keen to see the parallel LTO support in 0.57 available in Bullseye) Unstable is frozen for build systems so 0.57 won't be allowed in Bullseye. The version in unstable will only be updated after the release.
Bug#982865:
> Yes. You can test it yourself if you want, 0.57.1 is in experimental. Fab, thanks. Will 0.57.1 be migrated to unstable? Or perhaps even to testing? (I'm keen to see the parallel LTO support in 0.57 available in Bullseye)
Bug#982865:
On Wed, 24 Feb 2021 at 21:57, Nicholas Brown wrote: > Is this fixed in the 0.57.1 release? Yes. You can test it yourself if you want, 0.57.1 is in experimental.
Bug#982865:
Is this fixed in the 0.57.1 release?
Bug#982865: meson: diff for NMU version 0.57.0+really0.56.2-0.1
Hi On 2021-02-15 23:51:12, Jussi Pakkanen wrote: > On Mon, 15 Feb 2021 at 23:21, Sebastian Ramacher 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
Bug#982865: meson: diff for NMU version 0.57.0+really0.56.2-0.1
On Mon, 15 Feb 2021 at 23:21, Sebastian Ramacher 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?
Bug#982865: marked as done (meson: meson ignores CPPFLAGS)
Your message dated Mon, 15 Feb 2021 21:33:29 + with message-id and subject line Bug#982865: fixed in meson 0.57.0+really0.56.2-0.1 has caused the Debian Bug report #982865, regarding meson: meson ignores CPPFLAGS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 982865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: meson Version: 0.57.0-1 When packaging https://salsa.debian.org/yangfl-guest/sequeler , I got blhc warning about CPPFLAGS missing (-D_FORTIFY_SOURCE=2) after upgrading meson from 0.56.2-1 to 0.57.0-1. Log attached. meson-old Description: Binary data meson-new Description: Binary data --- End Message --- --- Begin Message --- Source: meson Source-Version: 0.57.0+really0.56.2-0.1 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of meson, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 982...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated meson package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 15 Feb 2021 21:17:44 +0100 Source: meson Architecture: source Version: 0.57.0+really0.56.2-0.1 Distribution: unstable Urgency: medium Maintainer: Jussi Pakkanen Changed-By: Sebastian Ramacher Closes: 982865 Changes: meson (0.57.0+really0.56.2-0.1) unstable; urgency=medium . * Revert to 0.56.2 (Closes: #982865) 0.57.0 no longer honors CPPFLAGS and therefore silently drops -D_FORTIFY_SOURCE=2 during package builds. Checksums-Sha1: ea6c74c324a9afa068ba81a8bffadb133a990584 3528 meson_0.57.0+really0.56.2-0.1.dsc a62199aca12eb69d4df7e828a8d11cc241ecff73 1794847 meson_0.57.0+really0.56.2.orig.tar.gz e69a2a47fdbf33b97fbdf2bf66fed83e3ae2ce56 14308 meson_0.57.0+really0.56.2-0.1.debian.tar.xz Checksums-Sha256: 0b5e1d5d0a9c898d24455da060db1dc1ab96a56839299693e934bbb62b73b233 3528 meson_0.57.0+really0.56.2-0.1.dsc 3cb8bdb91383f7f8da642f916e4c44066a29262caa499341e2880f010edb87f4 1794847 meson_0.57.0+really0.56.2.orig.tar.gz 44023ff687e6ed8832fd4922bc4f03e6ea6e9cb1a02c95d508b96b5139cbeed4 14308 meson_0.57.0+really0.56.2-0.1.debian.tar.xz Files: 774cf1a037ace740bb31337a5b24d4bf 3528 devel optional meson_0.57.0+really0.56.2-0.1.dsc 52b57dc223e39ae8d84f23a74296a89a 1794847 devel optional meson_0.57.0+really0.56.2.orig.tar.gz bcfea2e80226b3d5e81dd98a1a6ae2a5 14308 devel optional meson_0.57.0+really0.56.2-0.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmAq5RgACgkQafL8UW6n GZOaTA/8DXXaFvbd14HoxIZPLJFJoAigi3ur6MCCfTwKR1N4zoiCnxrtgF9TFbHS HVB5YYpZWdkdGW/GFeGJTkaUBOVosyL/pu7WvBjQdbuxQHmSC5xOAw/1Puxig7FK Wbk12DldwcsH/19bsfgfqIW95h9Upt9Z2c5XOtlADjuZmZ3hKGHY6OzVXzy2l/oq /HwgCaijgxc+OM9eYHXrKmF0k2ifK50/NXo9md70DT+nBrf95vdbaRBHNHBgNupm 0CRHnN12OMamZ/SYl8uR3E+yxdIp1ZYGpWms9bxMeA67b5Aalheccsj75TQypQVa KQrIwNwRZMR4OFzE+ItriCCIfeU3/DE/8NTCn3qF2VGj7iM/VvDurLIn91z68eRW l4qUnF/uZBV24DIVeGnq1Ex+dWQ/KBTJmidCUKWKiuSWbH6spPfoAPoq8vpYjHqF 6V0n1+DyH9gw4grLEe4ZDIepPlilsCWkwuFHYQAPx15t8URtKkSg9wOTyHU8MJ/e tSXCefuyGxJCBZxq8WU9WgD+N92l78tEqyAiCvYtz3Z+0o6wBb3x3SUKhZovVbk2 iPhFaT9ZvZnHGshjUhwZiuwGu/s3xyjwT0zr3qyUwuSeSHsr2xMS1XP/+M0Ao9a7 MfpuyCQGIWWwxwiEYfbP7LwfSOJMAeJB+24eUs1VHTpDmeNdT3o= =IidJ -END PGP SIGNATURE End Message ---
Bug#982865: meson: meson ignores CPPFLAGS
On 2021-02-15 20:34:20 +0100, Sebastian Ramacher wrote: > Control: severity -1 serious > > On 2021-02-15 23:43:24 +0800, Yangfl wrote: > > Package: meson > > Version: 0.57.0-1 > > > > When packaging https://salsa.debian.org/yangfl-guest/sequeler , I got > > blhc warning about CPPFLAGS missing (-D_FORTIFY_SOURCE=2) after > > upgrading meson from 0.56.2-1 to 0.57.0-1. > > > > Log attached. > > Thanks for reporting this issue. Attached is a very simple reproducer. > The package builds fine in bullseye, but fails to build in unstable. Link to the package https://people.debian.org/~sramacher/bug_1.0-1.dsc Cheers > > This will cause builds of reverse build dependencies of meson to > silently drop flags from dpkg-buildflags. Since this also includes > hardening options, I'm raising the severity to serious. > > Also note that we are in the middle of getting bullseye released. > Such changes are no longer suitable for bullseye. Please see > https://release.debian.org/bullseye/freeze_policy.html#soft -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: Re: Bug#982865: meson: meson ignores CPPFLAGS
Processing control commands: > severity -1 serious Bug #982865 [meson] meson: meson ignores CPPFLAGS Severity set to 'serious' from 'normal' -- 982865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
