tags 766762 +pending tags 766762 +patch tags 766762 +fixed-upstream severitz 766762 serious thanks
On Fri, Nov 28, 2014 at 03:49:05PM +0100, intrigeri wrote: > Michael Banck wrote (28 Nov 2014 14:19:32 GMT) : > > I think this bug is severe enough that it should be fixed now, and as > > soon as it is accepted in testing, the rest of the upstream point > > release could be submitted for inclusion, if time still permits. > > Agreed. If you had time to test if the commit I'm ponting at fixes the > bug for you too, it would be great! Well, I'm running with that patch applied now, but I've only ever saw this bug every other week or so, so it will be difficult to verfiy that the bug is gone in a timely manner. > And if you want to take care of the NMU and unblock request, please > do. I had a quick chat with a release team member and they seem to believe this bug warrants RC status: <azeem> so upowerd tends to eat up 2+GB in some cases due to a memleak, RC or not? <azeem> (2GB memory, that is) <LocutusOfBorg1> 2GB is not too much anymore :) <azeem> well, at 2GB my notebook keeps thrashing, and with luck I get to the console and kill -9 it <azeem> not sure what the upper bound is <thijs> I'd say RC <thijs> can always downgrade later if impact is better understood I've prepared an NMU by taking the git commit and will upload it to DELAYED/1-day later today. Debdiff is attached. I'll look into filing an unblock request as well. Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org