[00:01] <slangasek> stgraber: ah, I see that it was there in jaunty too; alas
[00:12] <TheMuso> slangasek: Are we likely to get multi-arch for karmic? I ask because if we're not, I guess I'd better start working on getting lib$bi packages done so we can have a lib$bi pulse package...
[00:13] <slangasek> TheMuso: it's in jeopardy; I'm afraid I have to recommend that you start working on the biarch bits needed for pulse
[00:14] <TheMuso> slangasek: Ok thanks.
[04:44] <jcastro> bryce: YOU ARE A HERO.
[04:44] <jcastro> bryce: I've been asking for lp to do excatly what you did with your script for like, ever.
[05:47] <ebroder> I want to try and get an SRU into Jaunty for bug #328575 - it's affecting our site deployment. The Debian maintainer introduced a fix in 2.26.2-2; the upstream maintainer committed a different fix on master (f41c3d14). Which one should I backport?
[05:47] <ebroder> (The upstream fix seems to be somewhat more correct than the Debian fix)
[07:03] <dholbach> good morning
[07:31] <dholbach> ArneGoetje: I just had a chat with lidaobing about ibus and it seems that MIR have been filed already - do you know what the state is and what's going to happen in karmic?
[07:31] <lidaobing> dholbach, hi
[07:40] <wgrant> StevenK: What gives you the idea that team unsubscription is broken again?
[07:40] <wgrant> WFM, and the tests still pass on edge's rev.
[07:44] <StevenK> wgrant: It didn't work for me yesterday
[07:45] <wgrant> StevenK: edge only updated over night.
[07:46] <dholbach> StevenK: it worked for me yesterday again iirc, but it indeed was broken
[07:46] <dholbach> but it definitely works now - I just did some sponsoring
[07:47] <dholbach> by the way: http://people.canonical.com/~dholbach/sponsoring/ :-)
[07:47] <dholbach> we're falling back
[07:47] <StevenK> Let me try, I'll subscribe -archive to a bug
[07:47] <wgrant> I fixed it fairly quickly, but a few PQM complications meant it took a day or two to land.
[07:47] <StevenK> Right, it certainly wasn't working yesterday
[07:48] <wgrant> And missed two edge rollouts.
[07:48] <StevenK> I'd click the -, and it would spin but then not disappear
[07:48] <dholbach> right
[07:59] <StevenK> wgrant: You can nail that bug shut, if you like
[08:04] <wgrant> StevenK: Thanks.
[08:10] <tseliot> StevenK, slangasek: any trace of nvidia-graphics-drivers-180_185.18.31-0ubuntu1 in the archive?
[08:13] <StevenK> nvidia-graphics-drivers-185/185.18.31-0ubuntu1
[08:14] <StevenK> That's in source NEW, which isn't what we agreed to
[08:18] <tseliot> StevenK: no, the source is -180
[08:20] <tseliot> therefore you should see an nvidia-graphics-drivers-180_185.18.31-0ubuntu1.dsc, etc.
[08:20] <StevenK> tseliot: nvidia-graphics-drivers-185_185.18.31-0ubuntu1.dsc
[08:21] <StevenK> It isn't -180, it's -185
[08:22] <tseliot> StevenK: no, please reject that. I don't know why it's there
[08:22] <StevenK> tseliot: Rejected.
[08:23] <tseliot> tjaalton: can you upload the correct nvidia driver for me, please?
[08:23] <tseliot> StevenK: thanks
[08:23] <tjaalton> tseliot: where
[08:23] <tjaalton> ?
[08:23] <tseliot> tjaalton: let me send you the links to the sources
[08:23] <tjaalton> shouldn't the source be renamed to n-g-d?
[08:23] <tjaalton> without the version
[08:25] <StevenK> If it stays as -180, it won't hit source NEW
[08:26] <tseliot> tjaalton: we'll do something similar in karmic+1
[08:27] <tjaalton> tseliot: ok
[08:27] <tseliot> tjaalton: I sent an email to your @cc.hut.fi address
[08:27] <tjaalton> tseliot: thanks
[08:27] <tseliot> tjaalton: thanks for the upload :-)
[08:31] <tjaalton> tseliot: done
[08:31] <tseliot> tjaalton: thanks a lot
[08:31] <tjaalton> npo
[08:31] <tjaalton> -o
[09:01] <dandre> hello,
[09:02] <dandre> Where can I find documentation on how to build a repository for ubuntu that could be put in ubuntu apt source ?
[09:09] <lifeless> dandre: man apt-ftparchive
[09:11] <dandre> is there any ubuntu specific data to consider or any debian style repository can be done?
[09:32] <ogra> evand, ping
[09:32] <evand> ogra: pong
[09:32] <ogra> evand, could you merge http://bazaar.launchpad.net/~lool/ubiquity/dh-installdirs-fix-for-ports/revision/3388
[09:33] <ogra> it fixed the ports build issue of ubiquity
[09:33] <ogra> and would enable me to finally get an image for armel :)
[09:34] <evand> ogra: yarp, speaking with him right now about it
[09:34] <ogra> ah, k
[09:38] <lool> ogra: We just discussed it on #ubuntu-installer
[09:38]  * ogra hates all these subchannels that fragment ubuntu-devel :/
[09:39]  * lool thinks the whole #u-i team can read the full backlog of its chan but not of #ubuntu-devel
[09:40] <ogra> yeah, i might just be nostalgic :P
[09:59] <\sh> Keybuk: someone stole dircproxy.net ;) bug #416842
[10:06] <lool> kees: Are you tempted to do a security review of papyon?  It's the MSN lib written in Python which will allow empathy to support MSN
[10:07] <lool> In C I'd ask for one but given that's in python I guessed you would be less concerned about stack overflows etc.
[11:38] <ogra> doko, around ?
[11:38] <doko> ogra: yes
[11:39] <ogra> doko, i'm looking at the FTBFS of graphviz and libshout on armel
[11:39] <ogra> doko, devlibs error: There is no package matching [ld-linux3-dev] and noone provides it, please report bug to d-shlibs maintainer
 thats the error (same in libshout and i bet if i dig i find more that try to use the nonexisting ld-linux3-dev
[11:40] <ogra> doko, one fix would be to add s/ld-linux3-dev// to d-shlibs as an override
[11:42] <ogra> doko, seems the same fix was used by the mojo guys since feisty, but now looking with objdump it seems that in karmic many packages have a "NEEDED" entry for ld-linux
[11:42] <ogra> on armel at least
[11:43] <ogra> well, ld-linux.so.3 to be specific
[11:45] <ogra> doko, so i'm looking for a suggestion what to do, if the d-shlibs would still be appropriate or not ... i discussed that with lool already and we both came to the conclusion that we dont know enough on the topic
[11:45] <ogra> s/d-shlibs/d-shlibs hack/
[11:48] <doko> ogra: ok, will try to look at this today
[11:48] <ogra> thanks
[13:16] <ArneGoetje> dholbach: the MIR for ibus is here: https://bugs.launchpad.net/bugs/398637 . There is still one outstanding packae in the New queue (ibus-qt). Once this is in the archive, we need to add it to the MIR and get it into main. Once all the packages have been approved, we can call for testing. I hope this all can be done this week...
[13:50] <dholbach> ArneGoetje: I'll let lidaobing know
[13:51] <ArneGoetje> dholbach: he is subscribed to the MIR
[13:51] <dholbach> ah, maybe he didn't know what was still in the queue or something
[13:51] <dholbach> ArneGoetje: so it's going to be the default in karmic?
[13:53] <ArneGoetje> dholbach: I'd like to have it the default. I'm using it in gnome for quite some time already and didn't have any problems yet. But with ibus-qt in place extensive testing needs to be done on Kubuntu. Anyways, we won't drop scim for now, the user can still switch back if he wants to. But the plan is to have ibus as default, yes.
[13:57] <dholbach> right
[13:57] <dholbach> good to know
[14:06] <liw> would anyone be willing to upload python-fstab and computer-janitor to karmic for me? (they're in main, hence not asking on -motu)
[14:26] <AnAnt> Hello, why does request-sync in karmic use LP lib by default ?
[14:26] <AnAnt> and how can I disable that ?
[14:39] <ogra> jdstrand, its your archive day today, right ?
[14:40] <jdstrand> ogra: yes
[14:40]  * jdstrand cowers a little
[14:40] <ogra> jdstrand, i'd like to get linux-fsl-imx51 out of binary NEW
[14:42] <jdstrand> ogra: ok
[14:42] <ogra> thanks :)
[14:49] <NCommander> oh, hey jdstrand :-)
[14:49] <jdstrand> ogra: should all this be in universe?
[14:49] <jdstrand> hi NCommander
[14:50] <ogra> jdstrand, no, actually in main, but i'm fine to wait for final approval from cjwatson or slangasek next week for that step, my images can build from universe atm
[14:50] <NCommander> jdstrand, I have a really really OMG priority package that needs to get through NEW ASAP as its a huge blocker. If you could please bump linux-mvl-dove to the top of your reviewing list, I'd greatly greatly appreciate
[14:50] <ogra> jdong, so wherever yu feel to put it is ok for me
[14:50] <ogra> *you
[14:50] <NCommander> ^it
[14:50] <jdstrand> NCommander: ack
[14:51] <jdstrand> ogra: done (to universe)
[14:51] <ogra> thanks :)
[14:51]  * ogra hugs jdstrand 
[14:51] <jdstrand> ogra: np
[14:51] <NCommander> jdstrand, thanks, your awesome, since this clears the way to build the package, binNEW it, and get the meta in archive
[14:52]  * jdstrand likes being called awesome
[14:52] <jdstrand> we'll see if it fits in a moment ;)
[14:52] <NCommander> jdstrand, if it doesn't, please CC me on the reject email (mcasadevall@ubuntu.com) so I can work on getting that fixed
[14:53] <jdstrand> NCommander: sure. by 'fits' I was talking about calling me 'awesome' :)
[14:53] <jdstrand> NCommander: I'm working on it
[14:54] <NCommander> jdstrand, oh, thank you very much
[15:04] <jdstrand> NCommander: there is 2.6.31-200.3 and 2.6.31-200.2. I assume it is safe to reject 2.6.31-200.2?
[15:06] <ogra> jdstrand, yes, somehow slangasek didnt drop them from the queue when he rejected .2
[15:06] <jdstrand> ok
[15:06] <ogra> .3 is the proper one
[15:35] <NCommander> jdstrand, yeah, sorry, I stepped out for breakfast
[15:41] <Riddell> Keybuk: can we chat about xsplash sometime?
[15:41] <ogra> Riddell, you want the extra flashing boot too ? :)
[15:42]  * ogra thinks his laptop flashes at least twice as much with xplash
[15:57] <jdstrand> NCommander, ogra: accepted linux-mvl-dove 2.6.31-200.3
[15:57] <ogra> thanks a lot
[15:58] <ogra> there will soon also be a metapackage for linux-imx51
[15:58] <ogra> rtg is working on it
[15:58] <jdstrand> ok
[15:58] <NCommander> jdstrand, you are awesome^2
[15:58] <jdstrand>  5
[15:58] <jdstrand> o/
[15:59] <jdstrand> np guys :)
[15:59]  * NCommander waits for a build record to pop up so I can rescore it
[17:45] <rtg> slangasek, what is 'Duplicated ancestry' wrt linux-meta-mvl-dove ?
[17:51] <ogra> slangasek, i would like to milestone bug 417009, but somehow i cant
[17:51] <kees> lool: I'm not hugely worried about it, but checking for stuff like "eval" or os.system, subprocess, etc might be nice.
[18:27] <mdz> robbiew_away: bug 357907 is a blocking issue for kernel crash dumps
[18:27] <mdz> robbiew_away: I've been talking with gmb about it on #launchpad
[18:38] <ebroder> Can somebody retarget bug #368895? It should be fix released in Karmic and confirmed in Jaunty
[18:45] <slangasek> rtg: "Duplicated ancestry" usually means: someone did a pocket copy of the source package, then the binary was uploaded, now soyuz can't figure out where to put it
[18:45] <rtg> slangasek, but its a new package, isn't it?
[18:48] <ogra> slangasek, even though i just made the changes to livecd-rootfs to support universe on all armel*, what do you think abotu moving imx51 and dove kernels and meta to main now ?
[18:49] <mvo> slangasek: I can upload the devicekit-disks patch now (it looks fine)
[18:50] <NCommander> jdstrand, can you demote linux-meta-mvl-dove? Its not supposed to be in main, and when it was promoted, it caused LP to explode since the package was still building
[18:50] <ogra> NCommander, you are great in contradicting my last sentence :P
[18:50] <NCommander> ogra, its just temporary
[18:51] <davidm> Guys please update https://wiki.canonical.com/UbuntuPlatform/Mobile/Hardware as to what you have and do not have currently
[18:51] <NCommander> ogra, the binary failed to upload because it was promoted while still building
[18:51] <jdstrand> NCommander: done
[18:51] <NCommander> ogra, we need to demote, build, then it can be promoted safely
[18:51] <davidm> Wrong channel
[18:51] <ogra> davidm, but even in this channel it should be up to date now :)
[18:56] <ogra> hmm, so linux-imx51 meta is in main now, linux-image-2.6.31-100-imx51 isnt yet, can someone make that consistent ?
[18:58] <sgallagh> mathiaz: ping
[18:58] <mathiaz> sgallagh: hey
[18:58] <sgallagh> mathiaz: Just wanted to give you a heads-up regarding SSSD 0.5.0
[18:59] <mathiaz> sgallagh: ok - what's the current plan?
[18:59] <sgallagh> mathiaz: We're still on track for releasing 0.5.0 on Monday. Tentatively we're planning to call the current HEAD of the upstream git repo 0.5.0 (unless testing over the weekend finds a showstopper bug)
[19:00] <mathiaz> sgallagh: awesome!
[19:01] <sgallagh> mathiaz: I was hoping you could tag someone to do a build from HEAD to make sure we didn't break the Debian/Ubuntu compatibility as well.
[19:01] <mathiaz> sgallagh: I did a build yesterday and pushed it to a PPA
[19:01] <mathiaz> sgallagh: I'll update the tree now and try again
[19:02] <sgallagh> mathiaz: That would be great. Thank you very much.
[19:02] <mathiaz> sgallagh: are you planning to push more patches to HEAD today?
[19:02] <mathiaz> sgallagh: or is the current HEAD feature complete?
[19:03] <sgallagh> mathiaz: No, my last push is intended to be complete.
[19:03] <sgallagh> mathiaz: Unless we find a critical bug
[19:03] <mathiaz> sgallagh: of course :)
[19:12] <slangasek> ogra: I think the kernels should have been published to main to begin with, not to universe; yes, they should be moved to main ASAP - and why are you building armel out of universe at all?
[19:13] <ogra> slangasek, colin didnt feel comfortable with the broken naming and asked to keep them in universe until its fully solved
[19:13] <ogra> which apprently is now
[19:13] <slangasek> rtg: yes, it does seem that it should be a new package, so perhaps you've hit a soyuz bug - what's the context for this error?
[19:13] <ogra> though strike dove from that
[19:14] <ogra> since there are apparently issues with moving them around atm
[19:14] <slangasek> ogra: looks like you figured out milestoning of 417009 after all?
[19:14] <ogra> yeah
[19:14] <rtg> slangasek, NCommander and jdstrand seem to think they have a handle on it.
[19:14] <ogra> i missed the nomination
[19:15] <NCommander> jdstrand, slangasek, please don't promote the meta package just yet until it uploads please
[19:15] <NCommander> slangasek, accepted as universe, build started, promoted to main, build finished. boom.
[19:16] <jdstrand> fwiw I promoted to main seconds after accepting it...
[19:17] <ogra> NCommander, to avoid confusion please lets add the subarch in such requests in the future instead of just saying "metapackage" :)
[19:17] <ebroder> If I want to try to get an SRU for bug #328575, should I cherry-pick the patch that the Debian maintainer added, or the patch that the upstream maintainer committed?
[19:17] <NCommander> jdstrand, we should probably make a safety note in ArchiveAdministration that if directly accepting a package to main, promote first, then add the override to let it enter the archive
[19:17]  * ogra just noted that we two might create a total confusing scheme atm
[19:18] <jefferai> Can anyone tell me how I can know which version of the kernel a particular linux-image is based on? 2.6.28-15...is this 2.6.28.[0-10]?
[19:19] <rtg> jefferai, a running kernel? cat /proc/version_signature
[19:19] <jefferai> rtg: that gives me 2.6.28-15.49, which isn't very useful
[19:19] <jefferai> since it's *buntu specfic
[19:20] <rtg> jefferai, well, it tells me a bunch. what is it that you want to know?
[19:20] <jefferai> what particular linux source version it's based off of
[19:20] <jefferai> 2.6.28.?
[19:20] <jefferai> since ? goes from 0-10
[19:20] <rtg> jefferai, yep
[19:20] <ebroder> 2.6.28, but it's probably pulled most of the patches in the stable releases
[19:21] <jefferai> so it'd be pretty safe to treat it as 2.6.28.10?
[19:21] <NCommander> slangasek, jdstrand, ok, it uploaded. I *think* its safe to promote now to main if that's what you want to do
[19:21] <ebroder> jefferai: For what purpose? Why do you care which stable release it is?
[19:21] <jefferai> The reason I ask is I'm trying to get as close to it in git as possible -- I have a repeatable (cross-distro!) issue I can see when using the kernel from git sources, and I'd like to try to figure out what Debian/Ubuntu is patching that fixes the problem
[19:22] <jefferai> so starting with the most alike source tree makes that much easier
[19:22] <rtg> jefferai, the git repo is git://kernel.ubuntu.com/ubuntu/ubuntu-jaunty.git
[19:23] <jefferai> Ah, ok
[19:23] <jefferai> Thanks...that should prove useful
[19:24] <jdstrand> NCommander: if it's all the same to you, based on ogra's comments re cjwatson's concerns (which I didn't know about before, re -dove), I'd just assume leave it for now. if slangasek feels differently, that's fine, but I'd rather not guess what should happen
[19:25] <ogra> jdstrand, no !
[19:25] <ogra> jdstrand, the concerns are solved with these packages, thats what we worked on the last weeks :)
[19:26] <jdstrand> ogra: so you are saying that both of these kernls *should* go to main, and all that is approved, etc?
[19:26] <NCommander> jdstrand, I don't really care, I just want my package to publisher SOMEWHERE :-)
[19:26] <ogra> jdstrand, right
[19:27] <jdstrand> ogra, NCommander: ok, then I'll get them to main
[19:27] <ogra> thanks :)
[19:27] <jdstrand> ogra: sorry for the misunderstanding
[19:27] <ogra> sorry for the bad expression
[19:27] <ogra> :)
[19:27] <jdstrand> :)
[19:28] <NCommander> :)
[19:29] <jdstrand> linux-fsl-imx51 promoted
[19:29] <ogra> \o/
[19:30]  * NCommander has to wait for 16:00 for his publisher run to conclude
[19:32] <jdstrand> NCommander: and you are saying that linux-meta-mvl-dove is safe to go to main now, and linux-mvl-dove goes to main *before* I binary deNEW it now, correct?
[19:32] <NCommander> jdstrand, if the binary and source have been accepted into universe it should be safe to bump them to main
[19:32] <NCommander> jdstrand, the problem comes when the source has been accepted, then {pro|de}moted, while there are builds running
[19:33] <jdstrand> that was not my question exactly
[19:33] <NCommander> jdstrand, the way to work around that is to simply promote the source before accepting it
[19:33] <jdstrand> NCommander: ok, so the builds are done afaict, so I'll promote
[19:34] <NCommander> jdstrand, yup. should be safe to do so now since publisher isn't running
[19:35] <jdstrand> linux-meta-mvl-dove promoted and then binary deNEWed
[19:36] <NCommander> jdstrand, deNEWed?
[19:36] <NCommander> As in binary accepted, right?
[19:36] <jdstrand> NCommander: yeah, the binary hadn't been deNEWed yet
[19:36] <jdstrand> NCommander: yes
[19:36] <NCommander> oh
[19:36] <NCommander> good
[19:36]  * NCommander breaths
[19:37] <jdstrand> NCommander: for a brand new package, source gets deNEWed before Accepted, then the binaries are built, which have to be separately deNEWed Accepted
[19:39] <NCommander> jdstrand, ah, that makes sense. When we freeze, then it hits Unapproved, then goes NEW -> Accepted
[19:41] <jdstrand> linux-mvl-dove binary deNEWed
[19:42] <jdstrand> (was previously promoted)
[19:42] <jdstrand> NCommander: so, you good now?
[19:42] <NCommander> jdstrand, yup!
[19:43] <jdstrand> NCommander, ogra: great! you should see everything in main after the next run
[19:43] <ogra> wonderful
[19:49] <mathiaz> sgallagh: could you cut an rc1 tarball of sssd?
[19:49] <mathiaz> sgallagh: it would help in finishing the packaging bits as I'm currently building from a bzr tree.
[19:51] <sgallagh> mathiaz: I'd prefer not to. It doesn't seem very sensible since we're going to release the final tarball on Monday.
[19:51] <sgallagh> mathiaz: At least not anything "official"
[19:51] <mathiaz> sgallagh: right - if I could just get a tarball that would be helpful
[19:52] <mathiaz> sgallagh: the packaging may be different between building from a src tree and from a tarball
[19:52] <sgallagh> mathiaz: I can give you one and call it rc1, but like I said I don't want to tag it in git and release it on the wiki
[19:52] <mathiaz> sgallagh: works for me.
[19:53] <sgallagh> mathiaz: Ok, give me a few minutes and I'll send you a link
[19:53] <mathiaz> sgallagh: thanks
[19:59] <slangasek> NCommander, jdstrand, ogra: are all the armel kernel packages now in main that should be?
[20:00] <ebroder> If I'm working on an SRU for a Python 2.6 migration bug in Jaunty (bug #368895), should I fix it to use python2.5, or 2.6?
[20:00] <ebroder> It's known to work with 2.6
[20:01] <jdstrand> I did linux-meta-mvl-dove, linux-mvl-dove, and linux-fsl-imx51
[20:01] <ScottK> ebroder: Is it an application or a module?
[20:02] <NCommander> jdstrand, slangasek, linux-meta-fsl-imx51 is left if no one promoted it
[20:02] <ebroder> ScottK: Application
[20:02] <ScottK> ebroder: Then I'd make it work with the one that involves the least invasive change.
[20:02] <jdstrand> slangasek, NCommander: I can do that
[20:02] <ogra> ogra@dove:~$ apt-cache show linux-image-2.6.31-100-imx51|grep -i filename
[20:02] <ogra> Filename: pool/universe/l/linux-fsl-imx51/linux-image-2.6.31-100-imx51_2.6.31-100.4_armel.deb
[20:03] <ogra> hmm, i dont see it in main yet
[20:03] <jdstrand> slangasek, NCommander: it's already there
[20:03] <NCommander> jdstrand, nifty
[20:03] <ogra> meta was there long ago
[20:03] <jdstrand> ogra: have to wait for the next publisher run
[20:03] <ogra> ok
[20:03] <NCommander> ogra, isn't the publisher run every two hours?
[20:03] <ogra> 30min afaik
[20:03] <jdstrand> should be at :03, aiui
[20:03] <ebroder> ScottK: Ok. I think they're pretty equally invasive, so I think I'll favor upgrading to 2.6
[20:03] <jdstrand> but it doesn't finish for much after that (I could be wrong on the time)
[20:04] <ScottK> All things being equal, that's probably best.
[20:04] <ogra> anyway, i'm off for the day
[20:05] <jdstrand> ogra: https://launchpad.net/ubuntu/+source/linux-fsl-imx51/2.6.31-100.4
[20:05] <jdstrand> ogra: it says " 2.6.31-100.4
[20:05] <jdstrand> PUBLISHED: Karmic pocket Release in component main and section devel"
[20:06] <jdstrand> ogra: so we just need to wait for it to get to the archive
[20:07] <jdstrand> ogra: I can tell you it is correct on cocoplum, so all should be good :)
[20:14] <sgallagh> mathiaz: ping
[20:14] <mathiaz> sgallagh: hey
[20:14] <sgallagh> mathiaz: Sorry for the delay. You can find the tarball and a signature at http://fedorapeople.org/~sgallagh/
[20:14] <mathiaz> sgallagh: great - thanks
[20:15] <sgallagh> mathiaz: Absolutely. Good luck!
[20:50] <strixv> Aptitude question: How to mark something (like ALSA 1.0.20) as "don't downgrade this back to 1.0.18" at every auto-update?
[20:58] <dtchen> hold it, or pin it using apt_preferences(5), etc.
[20:58] <dtchen> i presume you're referring to the userspace portion of alsa, anyhow.
[21:03] <sgallagh> mathiaz: Unsurprisingly, we found (and fixed) a showstopper bug. Do you want another tarball now, or can you wait for the release on Monday?
[21:11] <mathiaz> sgallagh: I don't need another tarball
[21:11] <mathiaz> sgallagh: it can wait for monday
[21:13] <sgallagh> mathiaz: Ok, great. Just wanted to keep you in the loop
[21:13] <mathiaz> sgallagh: thanks
[21:25] <NCommander> ogra, lool, anyone familiar with tasks, can anyone explain why the ubuntu-desktop task is pulling in the imx51 kernel?
[21:25] <NCommander> (which is obviously not desirable for non-imx51 builds :-))
[21:30] <lool> NCommander: Probably boot: * ${Kernel-Stem}-imx51 [armel]
[21:30] <lool> Not sure
[21:38] <NCommander> lool, what's that from?
[21:41] <slangasek> NCommander: the platform seed pod
[21:41] <NCommander> ah
[21:41] <slangasek> which pulls in /all/ the kernel flavors, of the old name
[21:42] <NCommander> I'm kinda curious on why its there since livecd-rootfs should handle kernel installation
[21:42] <slangasek> so dove probably needs added, and the others removed
[21:42] <NCommander> slangasek, no, we need both names, but one kernel per image
[21:42] <slangasek> well, ubuntu-desktop doesn't pull in any kernels directly on amd64
[21:42] <slangasek> yes, I meant "the others" that aren't imx51
[21:42] <NCommander> Oh
[21:45] <NCommander> slangasek, you feel like sponsoring the seed change?
[21:45] <slangasek> or I can just whack it in from here, whichever you prefer
[21:47] <Kano> hi, why is i915 always loaded even on system where this is not usefull at all?
[21:47] <Kano> initramfs-tools has got a very stupid behaviour
[21:49] <NCommander> slangasek, if you could, that would be appreciated as it brings us one step closer to dove images
[21:51] <slangasek> NCommander: committed
[21:52] <NCommander> slangasek, \o/
[21:52] <NCommander> slangasek, when (or should I saw how) do the tasks then in LP change. I'm familiar with normal seed changes, but not so much w/ the platform seed
[21:52] <slangasek> the tasks are updated by germinate as part of a publisher run
[21:53] <NCommander> slangasek, ah, so by the end of the 17:03 publisher of run, it should be done
[21:53] <NCommander> slangasek, thanks!
[21:53] <slangasek> NCommander: btw, linux-headers-2.6.31-100-imx51 is uninstallable because it depends on a non-existent linux-headers-2.6.31-100
[21:54] <slangasek> apw: ^^
[21:54] <NCommander> ^- ogra
[21:54] <NCommander> Still, we're looking on track to have some sorta image for FF
[21:55] <det> What is the default version of boost in Jaunty and Intrepid ?
[21:57] <slangasek> det: if by "default" you mean the packages without version numbers in them, then that would be 1.34
[22:09] <ScottK> If by default, you mean version in Main, it's 1.34 in Intrepid and 1.35 in Jaunty.