Apport

Merge lp://staging/~brian-murray/apport/no-devel-proposed into lp://staging/~ubuntu-archive/apport/lp-retracer-config

  1. no-devel-proposed
  2. Merge into lp-retracer-config
Proposed by Brian Murray
Status: Merged
Merged at revision: 40
Proposed branch: lp://staging/~brian-murray/apport/no-devel-proposed
Merge into: lp://staging/~ubuntu-archive/apport/lp-retracer-config
Diff against target: 41 lines (+6/-6)
2 files modified
Ubuntu 19.04/sources-ports.list (+3/-3)
Ubuntu 19.04/sources.list (+3/-3)
To merge this branch: bzr merge lp://staging/~brian-murray/apport/no-devel-proposed
Reviewer Review Type Date Requested Status
Steve Langasek Pending
Ubuntu Package Archive Administrators Pending
Review via email: mp+363629@code.staging.launchpad.net

Description of the change

apport-retrace is failing to retrace crashes from disco because there is a new glibc in -proposed for disco and the gdb sandbox code installs gdb and its dependencies which include glibc. Subsequently, glibc 2.29... gets install but crash reports are using glibc 2.28... and then there is a mismatch between the core file and the installed libraries. Thinking about it more we do not recommend that people have -proposed enabled for the development release and most people do not, so the easiest solution is to disable -proposed from the sources.list files until the release is stable.

To post a comment you must log in.
Revision history for this message
Steve Langasek (vorlon) wrote :

How do we track that this needs changing when the release goes stable? Also, does this mean that retraces will always fail across any release that has an SRU of glibc in progress?

Revision history for this message
Brian Murray (brian-murray) wrote :

> How do we track that this needs changing when the release goes stable?

We already have to add -updates to the ddebs.ubuntu.com sources entries when the release becomes stable so its just one more thing to do.

> Also, does this mean that retraces will always fail across any release that has an
> SRU of glibc in progress?

If its a major version bump e.g. 2.28 to 2.29 I guess, however looking at the currently supported releases there hasn't been an SRU like that.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches