[Bug 2083937] [NEW] [SRU] Enable frame-pointer on Noble in update-notifier

[Julian Andres Klode]

Public bug reported:

[ Impact ]
In order to help developers with profiling, Ubuntu enabled frame-pointers for packages in the main archive.

https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame-
pointers-by-default

The `Affects` packages were missed due to the packaging issues. These
have been fixed on Oracular and can now be ported to Noble.

[ Test Plan ]

Look at the DW_AT_producer in the associated debug ELF file for flags.
-fno-omit-frame-pointer should be present after the fix.

The following scripts can be used as a reference
https://gist.github.com/julian-klode/85e55553f85c410a1b856a93dce77208
https://gist.github.com/julian-klode/95818246eaef0ac6a54588f7f368e25c

The autopkgtests cover the Python parts, so we should start update-
notifier on a real system and see that it still starts. We don't expect
any regressions from compiler flag changes, so I don't want to do a
whole bunch of UI tests or anything.

[ Where problems could occur ]

No source changes are made. The packaging fixes have enabled other
security hardening flags. This could have unintended effects.

[ Other Info ]

changes in dpkg have been made to make sure frame-pointers are not
enabled on s390x and ppc64el.

Bug reference with similar SRU -
https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949

** Affects: update-notifier (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: update-notifier (Ubuntu Noble)
     Importance: Undecided
         Status: Triaged

** Also affects: update-notifier (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Changed in: update-notifier (Ubuntu)
       Status: New => Invalid

** Changed in: update-notifier (Ubuntu Noble)
       Status: New => Triaged

** Description changed:

  [ Impact ]
  In order to help developers with profiling, Ubuntu enabled frame-pointers for packages in the main archive.
  
  https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame-
  pointers-by-default
  
  The `Affects` packages were missed due to the packaging issues. These
  have been fixed on Oracular and can now be ported to Noble.
  
  [ Test Plan ]
  
  Look at the DW_AT_producer in the associated debug ELF file for flags.
  -fno-omit-frame-pointer should be present after the fix.
  
  The following scripts can be used as a reference
  https://gist.github.com/julian-klode/85e55553f85c410a1b856a93dce77208
  https://gist.github.com/julian-klode/95818246eaef0ac6a54588f7f368e25c
  
- <package specific test plan goes here>
+ The autopkgtests cover the Python parts, so we should start update-
+ notifier on a real system and see that it still starts. We don't expect
+ any regressions from compiler flag changes, so I don't want to do a
+ whole bunch of UI tests or anything.
  
  [ Where problems could occur ]
  
  No source changes are made. The packaging fixes have enabled other
  security hardening flags. This could have unintended effects.
  
  [ Other Info ]
  
  changes in dpkg have been made to make sure frame-pointers are not
  enabled on s390x and ppc64el.
  
  Bug reference with similar SRU -
  https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-notifier in Ubuntu.
https://bugs.launchpad.net/bugs/2083937

Title:
  [SRU] Enable frame-pointer on Noble in update-notifier

Status in update-notifier package in Ubuntu:
  Invalid
Status in update-notifier source package in Noble:
  Triaged

Bug description:
  [ Impact ]
  In order to help developers with profiling, Ubuntu enabled frame-pointers for packages in the main archive.

  https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame-
  pointers-by-default

  The `Affects` packages were missed due to the packaging issues. These
  have been fixed on Oracular and can now be ported to Noble.

  [ Test Plan ]

  Look at the DW_AT_producer in the associated debug ELF file for flags.
  -fno-omit-frame-pointer should be present after the fix.

  The following scripts can be used as a reference
  https://gist.github.com/julian-klode/85e55553f85c410a1b856a93dce77208
  https://gist.github.com/julian-klode/95818246eaef0ac6a54588f7f368e25c

  The autopkgtests cover the Python parts, so we should start update-
  notifier on a real system and see that it still starts. We don't
  expect any regressions from compiler flag changes, so I don't want to
  do a whole bunch of UI tests or anything.

  [ Where problems could occur ]

  No source changes are made. The packaging fixes have enabled other
  security hardening flags. This could have unintended effects.

  [ Other Info ]

  changes in dpkg have been made to make sure frame-pointers are not
  enabled on s390x and ppc64el.

  Bug reference with similar SRU -
  https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/2083937/+subscriptions