[06:40] <pitti> skaet, Daviey: https://bugs.launchpad.net/ubuntu/lucid/+bugs?field.milestone%3Alist=30510 \o/
[08:34] <Daviey> pitti: I guess you are aware desktop is oversized?
[13:15] <quadrispro> hi all
[13:15] <quadrispro> could anyone give a feedback here? bug 930111
[13:15] <ubot4`> Launchpad bug 930111 in glew (Debian) (and 2 other projects) "glew 1.7.0 transition (affects: 1) (heat: 8)" [Unknown,Fix committed] https://launchpad.net/bugs/930111
[13:17] <seb128> quadrispro, just as a side note make sure that unity got tested on intel, ati and nvidia before getting an update, we got bugs in the past that made unity segfault on glew updates
[13:19] <quadrispro> seb128, ok!
[13:22] <quadrispro> seb128, no problem, the sync could be done at any moment since it won't introduce any big breakage
[13:23] <seb128> quadrispro, how do you know it won't? ;-)
[13:23] <seb128> it's a new version with quite some changes
[13:24] <seb128>  
[13:24] <seb128> could somebody approve my desktop update email to the release list?
[13:34] <quadrispro> seb128, no API/ABI break, I've been using it since december. I don't say "it won't break anything at all", just "it's likely that it won't break anything"
[13:34] <quadrispro> :)
[15:46] <seb128> skaet, hey
[15:47] <skaet> hiya seb128,  you rep
[15:47] <seb128> skaet, can you approve my desktop status update email on the release list? I'm replacing pitti today
[15:47] <skaet> for desktop
[15:47] <skaet> heh,  that answers that question
[15:47] <seb128> skaet, it got stucked in moderation...
[15:47] <skaet> yup will go in and approve
[15:47] <seb128> skaet, thanks
[15:47] <seb128> I asked earlier on the channel but I guess nobody was around yet ;-)
[15:50] <skaet> seb128, should be through now, and I've added you to the accept filter for future.
[15:50] <seb128> skaet, thanks!
[15:50] <skaet> :)
[16:21] <micahg> quadrispro: FYI, the glew 1.5 -> 1.6 transition was never completed
[16:33] <quadrispro> micahg, I'll be right back
[16:47] <bjf> skaet: i know it's getting close to eod for some. there are a number of kernels that need pocket-copying to various places (just fyi)
[16:55] <skaet> bjf - hmm.. pitti's off today,  RAOF is on weekend... lets see what I can come up with...
[16:56] <bjf> skaet: thanks, if it doesn't happen, no worries
[16:57] <skaet> bjf,  good to know.  thanks.
[17:32] <slangasek> bjf, skaet: well, I can certainly run the commands but I don't know how to validate that the commands dtrt
[17:33] <slangasek> bjf: i.e., which of the kernels listed on http://people.canonical.com/~ubuntu-archive/pending-sru.html are ready?
[17:35] <bjf> slangasek: http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html is a handy report which tells you things about each kernel
[17:35] <skaet> slangasek,  thanks for offering - I'd like to wait on anything affect lucid until pitti is around if possible.
[17:35]  * skaet is a little overcautious perhaps....
[17:36] <bjf> skaet, at this point, we'll probably just roll new lucid kernels and upload them next week anyway
[17:36] <skaet> bjf,  fair enough.
[17:36] <skaet> slangasek,  projbably just the maverick one then.
[17:37] <slangasek> bjf: where are the various "phase"s documented?
[17:38] <bjf> slangasek: they are so obvious, they are self documenting ;)
[17:39] <slangasek> bjf: well, no, I don't understand if "Phase: CopyToUpdates" means "is ready to be copied to updates", "copying to updates is the next step", "has been copied to updates"... :)
[17:39] <bjf> slangasek: it means that it is now ready to be copied to updates
[17:39] <slangasek> ok
[17:40] <slangasek> frustratingly, that page's output for maverick completely disagrees with http://people.canonical.com/~ubuntu-archive/pending-sru.html
[17:40] <bjf> slangasek: looking
[17:41] <slangasek> ah, no - it doesn't disagree, http://people.canonical.com/~ubuntu-archive/pending-sru.html just only reports about the CopyToProposed phase
[17:41] <bjf> slangasek: right
[17:47] <slangasek> bjf: is linux-firmware tied to the process?
[17:47] <bjf> slangasek: no
[17:47] <slangasek> ok
[17:48] <bjf> slangasek: but the maverick firmware has been "cooking" for some time
[17:48] <bjf> slangasek: natty as well
[17:49] <slangasek> ack
[17:55] <slangasek> bjf, skaet: copytoupdates done for maverick,natty,oneiric; lucid left alone due to the point release concern from skaet
[17:56] <bjf> slangasek: thanks
[17:59] <skaet> slangasek, thanks! :)
[18:11] <slangasek> linux-firmware also copied for maverick; for natty there's a verification failure