[09:14]  * Laney respins the failed ubuntu dailies
[10:05] <xnox> FFe process applies to unseeded/universe packages as well. True or False?
[10:05] <Laney> yes
[10:05] <knome> hi Laney
[10:05] <Laney> hey knome
[10:05] <knome> Laney, i'm sorry, i had a misunderstanding on the gtk2 indicator issue - i'm been told we knew about it well before
[10:06] <knome> Laney, and now the answer for your question: we are going to reupload them; if you can help..
[10:06] <knome> Laney, ..then please tell us you can. :)
[10:06] <Laney> help in what way?
[10:06] <Laney> I can't help you maintain them ...
[10:06] <knome> help reuploading
[10:07] <knome> of course not, but we still need to reupload them
[10:07] <Laney> ah, well if you prepare a package then I can help on that side
[10:07] <knome> we'll get it sorted
[10:07] <Laney> you'll need FFe too.
[10:08] <knome> yes, i hope those will be granted
[10:08] <knome> mr_pouit is working on it with gilir from lubuntu
[11:11] <davmor2> Hey guys there looks to be an issue with webcam detection on my laptop did a current install from yesterday and ubiquity fails on the webcam page.  This in turn nails the system I have to hard power switch it, reisub fails, ssh fails.  I'm going to see if it effects the installed system and see if I can get some debug info from there
[11:18] <davmor2> yeap same issue running cheese it just kills the system completely
[11:19] <davmor2> over the the kernel channel I guess and hopefully they can help
[19:58] <phillw> is the quantal kernel in todays release, or do we need to await for a rebuild ( re: http://irclogs.ubuntu.com/2012/08/28/%23ubuntu-meeting.txt|IRC )
[20:08] <slangasek> phillw: what do you mean by "in today's release"?  any quantal daily builds are using a quantal kernel.
[20:10] <phillw> slangasek: the notes from http://irclogs.ubuntu.com/2012/08/28/%23ubuntu-meeting.txt
[20:11] <phillw> was that updated Q kernel in for todays respins, or does it have to wait untill tomorrow?
[20:11] <Laney> you can check the manifest files to find out exactly which packages are included
[20:13] <phillw> Laney: do have a link handy, save me spending time on google when all I want to do is let the Qa teams know we have 'the final' kernel to be tested quickly before feature freeze lands on Thursday?
[20:14] <bjf> phillw: if you are talking about 3.5.0-13.13 then it will probably be in tomorrows daily. that quantal kernel was only published 7 hrs. ago.
[20:15] <phillw> bjf: thanks I'm referring to the part of the email http://pastebin.com/F8zYn4i6
[20:15] <Laney> eg http://cdimage.ubuntu.com/daily-live/current/quantal-desktop-amd64.manifest
[20:15] <phillw> It's always fun to the testers that they have 24 hours before a feature freeze for a kernel :P
[20:15] <bjf> phillw: that's the kernel version i just mentioned
[20:15] <phillw> no worries, I'll let them all know :)
[20:41] <cyphermox> arf, I blindly uploaded indicator-sync 12.10.1-0ubuntu1; it's perhaps not so clear, but it's a bugfix release despite the API/ABI changes; nothing should be using it in the archive yet
[20:59] <micahg> cyphermox: I'm sure you're aware that new binaries need an FFe
[21:09] <seb128> micahg, do they?
[21:10] <micahg> seb128: that's what I've been told
[21:10] <seb128> micahg, where is it written?
[21:10] <micahg> seb128: https://wiki.ubuntu.com/FeatureFreeze
[21:10] <micahg> second section, second bullet
[21:10] <micahg> that's ABI, not general though
[21:11] <seb128> micahg, that's not about new binaries, but about abi changes
[21:11]  * micahg thought this was fixed last cycle....
[21:11] <seb128> micahg, that page has no new binary mention
[21:11] <seb128> there is no "binary" match at all in fact
[21:12] <micahg> well, if you want to get technical, the first line doesn't say source explicitly :)
[21:13]  * micahg wishes a release person would come to his defense here :)
[21:13] <seb128> well,I disagree that new binaries should require a ffe in a systematic way
[21:13] <seb128> the documentation doesn't state it should
[21:13] <seb128> so if that's a real rule it should be stated somewhere
[21:14] <micahg> I would argue that it could have in impact on how other packages use this package in question
[21:14] <seb128> we have been accepting some new -dbg recently without asking for a ffe
[21:15] <micahg> *crickets*
[21:15] <seb128> why would adding a dbg impact on other packages?
[21:15] <micahg> seb128: that's a case where it wouldn't, but cases where you add a data/common package certainly could
[21:15] <seb128> ok, so the rules is not about "new binaries", it's more specific ;-)
[21:16] <micahg> well, some FFes you know will be approved, but you file them anyways, but I'll let someone from the release team verify what I've said before I go on with it
[21:17] <slangasek> seb128: it has an impact on how the developers are spending time post-FF; uploading (and archive processing) of -dbg packages doesn't seem like very much focusing on bugfixes?
[21:17] <slangasek> but I wouldn't reject a -dbg package I saw in the NEW queue during FF
[21:17] <slangasek> because it wouldn't be worth arguing about
[21:17] <seb128> right, that's basically my position as well...
[21:18] <seb128> slangasek, well, I could argue that -dbg can be useful for debugging,bug fixing
[21:18] <slangasek> no, that's what we have .ddebs for :)
[21:18] <seb128> ;-)
[21:19] <seb128> yeah, I wish we had ddebs support in launchpad though for those upstream who do daily builds and such in ppas using the same packaging
[21:27] <Laney> I understand that this indicator-sync upload /was/ an ABI break though?
[21:28] <Laney> So should have had an exception however you read that page...
[21:28] <Laney> it's kind of unfortunate that it now FTBFS on arm* ppc too
[21:36] <seb128> Laney, oh, it's indicator-sync we are talking about ;-) I joined just to read the comment on new binaries
[21:36] <seb128> Laney, well, indicator-sync is NEW in the archive for less than a week and used by nothing and there is a ffe for u1 to use it
[21:36] <seb128> Laney, I'm unsure there is a need to file yet another ffe for a new package just to make it work when it never worked