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
> 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)
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.
Is this fixed in the 0.57.1 release?
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 cou
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
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
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.
>
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
9 matches
Mail list logo