** Changed in: nspr (Ubuntu)
Status: Incomplete => 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/2084460
Title:
[SRU] Please enable frame-pointer on Noble
To manage notification
** Also affects: nspr (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: nspr (Ubuntu Noble)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20844
Please make the following clarifications in the test plan and SRU "where
problems could occur":
a) Use the scripts as planned in the original test plan, but extend them
to all architectures, because we don't want frame pointers in s390x and
ppc64el, only arm64 and amd64 if I'm not mistaken (not on
I did a quick comparison between the build flags, using the first
compiler command line from the build log, when it's building now.o:
--- noble-devel 2024-11-28 15:36:33.478894133 -0300
+++ noble-unapproved2024-11-28 15:36:28.490813597 -0300
@@ -24,13 +24,18 @@
-D_REENTRANT=1
-DXP_UNIX=1
-f
I am not sure the Impact is relevant enough to grant an SRU, and I
believe that the issue mentioned under "Where problems could occur":
> The packaging fixes have enabled other security hardening flags.
> This could have unintended effects.
is not negligible at all. Given that the diff is technic
nspr in noble is a build1 of the Debian package. The only delta between
noble and oracular are the frame pointer changes, this patch is a
backport of the oracular changes as nspr - `2:4.35-1.1ubuntu1~24.04`.
Please see my dev PPA for a test build:
https://launchpad.net/~mkukri/+archive/ubuntu/dev
** Summary changed:
- [SRU] Please enable frame-pointer on Noble Edit
+ [SRU] Please enable frame-pointer on Noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084460
Title:
[SRU] Please enable f
