Hey Andreas, thanks for seeking clarification Crash still needs fixing in Resolute. When I initially made the SRU template it was during release week and as such Resolute was the new devel release, however, not everything was yet in place to properly target the release (ie. there was not yet a crash package on Resolute at that time). My understanding is that this is because autosyncs won't happen and / or require review if there's any outstanding / remaining patches in d/p. The "crash landed in Resolute" part of my comment was just referring to the fact that a package had been uploaded to Resolute against which the previously uploaded Resolute debdiff could be applied.
At the time I created the SRU template, I created the Resolute debdiff based on the Questing package, since there was no version of crash queued in Debian that would supercede the one that was already in Questing. Essentially, I was predicting that Resolute would inherit the Questing package. As of today Questing and Resolute both have 8.0.6-1ubuntu2 so the Resolute debdiff I uploaded still applies in the same way as when I proposed it -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2125145 Title: [SRU] Makedumpfile: Errors and Page Exclusions When Opening Kernel Crashdump Files Generated on the Latest HWE Kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2125145/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
