On Tue, 2012-06-26 at 23:17 -0400, Jeff Mahoney
On 6/26/12 5:18 PM, Jiri Slaby wrote:
On 06/25/2012 01:10 PM, Marcus Meissner wrote:
> We are getting lots of bugreports that the current 12.1
> kernel update breaks suspend to ram.
> bnc#764864 and lots of duplicates.
We should be fine by now...
I'm afraid not. This is an issue severe enough that we revoked a
maintenance update and I don't see a mention of that bnc (or
related) in the changelog. I'm not going to push it as a
maintenance update until there's a entry in the changelog with a
bugzilla reference that shows the casual user that this problem
has been fixed.
Is this the relevant fix? If so, please document it.
Aw poo, no bug reference, and not verbose enough. Yeah, removing
the dud patch is the fix. Hm, so to properly document, edit
kernel-source.changes and push again, or revert and redo from
All the options suck. In 12.1, kernel-source.changes isn't used
anymore. The changelog is generated from the git log. Since it's the
top commit, I wonder if git commit --amend will work or if it'll break
things since you've already pushed. If that works, it'd be ideal.
Otherwise, a "previous commit did xyz (bnc#...)" commit will probably
be the cleanest.