** Changed in: glibc (Ubuntu Eoan)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833067
Title:
FTBFS on amd64 / i386 when compiled with new hardening defaults in
As per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834315/comments/7
this should be resolved once the launchpad builders are updated to the
kernel in xenial-proposed (4.4.0-155)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Using the hwe-edge kernel (5.0.0-17-generic) on a bionic host with an
eoan schroot seems to work - not sure what this says about the
copy_file_range test on the normal hwe kernel on bionic or for the
builders on launchpad...?
--
You received this bug notification because you are a member of
** Tags added: id-5d0ba41f0451f512579d2806
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833067
Title:
FTBFS on amd64 / i386 when compiled with new hardening defaults in
eoan
To manage
I am a bit stumped on this one - glibc_2.29-0ubuntu3 built fine in my
PPA (https://launchpad.net/~alexmurray/+archive/ubuntu/gcc-stack-clash-
protection2) but FTBFS on amd64/i386 for eoan-proposed - but I cannot
reproduce the same failure locally either in an schroot or in an eoan VM
- however, it
** Changed in: glibc (Ubuntu)
Importance: Undecided => High
** Also affects: glibc (Ubuntu Eoan)
Importance: High
Status: New
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The attachment "glibc_2.29-0ubuntu3.debdiff" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch"
