[12:36] <cjwatson> superm1: it's in the main sponsors queue
[12:36] <cjwatson> superm1: I assigned it to myself for sponsorship review
[12:36] <superm1> cjwatson, ah right.  Just wanted to check and see if that was why or if you had other ideas for it
[12:36] <cjwatson> I don't know yet :-)
[12:37] <LaserJock> hi cjwatson
[12:38] <cjwatson> LaserJock: hi, you have mail ;-)
[12:39] <ajmitch> morning
[12:39] <cjwatson> you know, I might be able to respond to mikmorg if he didn't keep asking me questions in my evening and then quitting before I get back ... sigh
[12:40] <LaserJock> heh
[12:40] <LaserJock> cjwatson: so, any ETA on when the CD build machine will be back up?
[12:41] <ajmitch> great, still 2 weeks until UVF
[12:41] <ajmitch> a new version of f-spot came out today
[12:42] <cjwatson> LaserJock: I'll get it sorted out tomorrow one way or the otherr
[12:42] <cjwatson> other
[12:42] <LaserJock> ok cool
[12:42] <cjwatson> either by fixing mkisofs to stop segfaulting or by just downgrading it to dapper
[12:42] <LaserJock> I'd just like to make sure it works before Tribe 4
[12:43] <cjwatson> oh, sure
[12:43] <cjwatson> I'm not going to leave CD builds broken over the weekend if I can help it
[12:43] <LaserJock>   cool, thanks for doing all that
[12:43] <superm1> cjwatson, is this what was breaking the ppc dailies too, or is that a sep issue?
[12:43] <LaserJock> I *might* need to do one more patch to add in icons before Gutsy is released
[12:44] <LaserJock> but I'm not sure at this point so I didn't want to add it in for nothing
[12:45] <dobey> ajmitch: hey
[12:45] <ajmitch> hello
[12:46] <cjwatson> superm1: err I have no idea what was breaking the powerpc dailies; reference?
[12:46] <cjwatson> as in, roughly when
[12:46] <cjwatson> and which images, etc.
[12:46] <superm1> cjwatson, i just tried the last 3 days images
[12:46] <superm1> aug 1, july 31, july 30
[12:46] <cjwatson> broken in what way?
[12:46] <superm1> they boot to a busy box shell
[12:47] <superm1> and sit there
[12:47] <cjwatson> that's not this problem
[12:47] <cjwatson> I have no idea what that is
[12:47] <cjwatson> live cd?
[12:47] <superm1> yes
[12:47] <cjwatson> booting to a shell is usually the kernel failing to detect hardware, though it could conceivably also be initramfs-tools or casper breakage
[12:47] <superm1> i just obtained a powerpc eMac for a week or two to experiment with, and ran into that imm
[12:47] <superm1> i see
[12:47] <cjwatson> have you got *any* Ubuntu live CD to boot on it?
[12:47] <superm1> yes
[12:47] <superm1> well
[12:47] <superm1> with a little work yes
[12:48] <superm1> xorg conf generation needs a litle work
[12:48] <superm1> but after fixing the xorgconf on a live boot it boots
[12:48] <superm1> i did a feisty live disk
[12:49] <superm1> actually as i recall, a dist-upgrade to gutsy did the same thing
[12:49] <superm1> i'll have to look more into it and file a bug yet then
[12:50] <mpt> hi LaserJock
[12:52] <mpt> Was my bootloader GUI feedback helpful?
[12:52] <LaserJock> mpt: I think quite
[12:52] <LaserJock> mpt: hopefully he can parse it all
[12:54] <LaserJock> mpt: I also have a 1024X768 screen and it was fine (in fact that's what I used to take the screenshots in my blog)
[12:54] <LaserJock> mpt: so I guess it must be some sort of bug
[12:57] <mpt> LaserJock, one possibility that occurs to me
[12:57] <mpt> Is the "Operating System List" set to scroll?
[12:57] <LaserJock> mpt: not sure
[12:57] <mpt> I can see about 12 items in the list, there are probably more
[12:57] <LaserJock> oh geeze :-)
[12:57] <cjwatson> ok, what the hell
[12:58] <mpt> and if the list is set to insist on showing all of them, that might be the problem :-)
[12:58] <cjwatson> mkisofs on antimony works fine if I recompile it in an edgy chroot
[12:58] <cjwatson> sigh, tomorrow
[01:00] <LaserJock> mpt: yep, that could be it
[03:13] <calamari> hi
[03:14] <calamari> I'm attempting to loop mount a fuse systems in the initramfs.  Got the fuse working, but for some reason losetup doesn't seem to work (the resulting /dev/loop0 is empty.  Any ideas?  Works okay from normal environment
[03:22] <calamari> actually, maybe I'd be better off working from normal init.. nm
[03:40] <ajmitch> hello Hobbsee
[03:40] <Hobbsee> hi ajmitch
[03:49] <mneptok> good morning campers!
[03:50] <bddebian> Sheesh, glad I didn't say hello :-)
[03:50] <ajmitch> good day mneptok
[03:51] <mneptok> arr ajmitch
[03:55] <bhale> hi ajmitch
[03:55] <bddebian> Whoa, hey bhale
[03:55] <ajmitch> hello bhale, how are you?
[03:55] <bhale> whoa bddebian
[03:55] <bhale> ajmitch: good, you?
[03:56] <ajmitch> alright
[03:59] <Hobbsee> dobey: if you dont file bugs on u-r-e, how do you expect me or someone else to find out about what other codecs people want, and add them too?
[04:00] <Hobbsee> Nafallo: irc is a dodgy bug tracker.  please use the proper one.
[04:00] <TheMuso> Hobbsee: I did one a while ago.
[04:01] <TheMuso> Or it maybe was two.
[04:01] <Hobbsee> oh, sorry, u-r-e
[04:01] <Hobbsee> TheMuso: which?
[04:01] <dobey> huh?
[04:01] <TheMuso> Hobbsee: nvm since you are referring to ure.
[04:02] <Hobbsee> dobey: ubuntu-restricted-extras, how you're complaining that it doesnt have fluendo stuff.  please make a bug against u-r-e for that, so it gets fixed.
[04:02] <dobey> i wasn't complaining that restricted-extras doesn't have fluendo stuff
[04:03] <Hobbsee> s/complaining/mentioning/ :)
[04:03] <Hobbsee> dobey: still, i'd appreciate if you could file said bug.
[04:04] <dobey> i mentioned that the codec installer didn't list the fluendo stuff. it has nothing to do with restricted-extras to me. and i mentioned it because it was relevant to the conversation of people complaining about automatix :)
[04:05] <dobey> and i never said i wouldn't file a bug
[04:05] <Hobbsee> dobey: afaik, the codec installer *is* the restricted-extras.  or close to it.
[04:05] <Hobbsee> dobey: i think i've seen too much of forums - they say "it'd be so cool to have this added" yet never file a bug or actually tell someone about it, usefully
[04:06] <dobey> welcome to teh internets
[04:07] <mneptok> it would be so cool to kck Hobbsee's ass. maybe i should start working out .... nah, i'll have some more Doritos and do it tomorrow.
[04:08] <Hobbsee> mneptok: :P
[04:09] <mneptok> i like it rough.
[04:09] <mneptok> which is a good thing, as my reprehensible personality incites abuse.
[04:09] <Hobbsee> dobey: then again, if they know that they have to file bugs, and refuse to, do they really want it added?  :)
[04:09] <Hobbsee> dobey: tbh, i'd prefer not to try the uni uplink - it works for irc, but uploading things might be a bit evil
[04:11] <ajmitch> Hobbsee: you've been reading the thread about packages to add to universe, haven't you?
[04:11] <Hobbsee> ajmitch: no.  although i get that every once in a while, as i got subscribed to everything i post
[04:11] <Hobbsee> ajmitch: i was more thinking little bugs
[04:37] <Hobbsee> hi spam
[04:48] <StevenK> infinity: Have I hit near the top of your todo list yet?
[04:50] <infinity> Ish. :)
[04:50] <infinity> Only 8000 lpia builds to go, after all.
[04:50] <StevenK> Hah
[04:56] <calc> lol
[04:57] <kylem> hhe.
[04:58] <StevenK> calc: Have you got a plan to upload OO.o 2.3?
[04:58] <StevenK> calc: And will it build on powerpc? :-)
[04:59] <infinity> That's our hope.
[05:12] <bddebian> Is there an archive admin aboot that could throw a package back up for me?
[05:12] <calc> StevenK: plan is as soon as i get it fully merged, and i don't know about ppc yet
[05:14] <su-hoens`rZ> anyone know why the kubuntu alt cd installer doesn't locate 3 of my 4 sata drives even though the bios and the main cd find them fine? :(
[07:25] <drago> guys, what kernel will be used in 6.06.2 release?
[07:25] <Burgundavia> drago: given the api/abi stability statements, probably the same one as is in current 6.06.1
[07:25] <RAOF> 2.6.15, same as always?
[07:27] <LaserJock> are we doing a 6.06.2?
[07:28] <ajmitch> apparantly it's planned
[07:31] <ScottK> Yes.
[07:31] <ScottK> It's due out this month.
[07:31] <ScottK> If your LP-foo is sufficent you can get a list of the targetted bugs.
[07:32] <Burgundavia> ScottK: you doing evil things to goats again?
[07:33] <ScottK> Not that I'm willing to admint too, no.
[07:33] <ScottK> admint/admit
[07:36] <Burgundavia> ScottK: by admitted you are able to get that kind of information out of LP, you already have :)
[07:36] <ScottK> Ah.
[07:36] <ScottK> No, I can't do it.
[07:36] <ScottK> I just happened to be on IRC when I saw someone else.
[07:36] <ScottK> Didn't book mark it though.
[07:37] <ScottK> My LP-foo mostly consists of bitching and filing bugs.
[07:38] <Burgundavia> https://launchpad.net/ubuntu/+milestone/ubuntu-6.06.2
[07:39] <ScottK> Yeah.  That's the one.
[07:41] <Seveas> Burgundavia, so *you* are doing evil things to goats?
[07:42] <Burgundavia> Seveas: a gentleman never tells
[07:42] <Seveas> but a wease^H^H^H^H^HBurgundavia does :)
[07:43] <Burgundavia> you know, I thought somebody might make that joke
[07:43] <Seveas> it's fairly predictable
[07:43] <Burgundavia> nah, I just sleep with LP developers
[08:34] <pitti> Good mooooorning!
[08:35] <LaserJock> morning pitti
[08:36] <StevenK> Morning pitti
[08:36] <StevenK> pitti: lib{gn,kl}ash0 look be able to be NBS'd when gnash gets NEW'd
[08:37] <pitti> the unstoppable Steve :)
[08:37] <StevenK> Heh
[08:37] <StevenK> pitti: It seems infinity can stop me. He doesn't love me at all. :-)
[08:41] <lamont> NBS?
[08:41] <StevenK> Not Build from Source
[08:42] <StevenK> It looks like gaim has hit NBS, too.
[08:42] <lamont> as in FTBFS?
[08:42] <coNP> You mean pidgin?
[08:43] <lamont> (fails to build from source)
[08:43] <RAOF> No, gaim.  Pidgin still builds from sources, obviously :)
[08:43] <coNP> But why do we still have gaim? :)
[08:43] <RAOF> lamont: As in: there are binaries in the archive that can't be rebuilt.
[08:44] <StevenK> lamont: No, as in Pidgin no longer builds a gaim package, not that it fails to build. :_)
[08:44] <lamont> ah, ok
[08:46] <StevenK> One I can fix simply.
[08:46] <StevenK> My problem is, the others have gaim- in their name.
[08:47] <pitti> StevenK: erk, pidgin not building a transitional package any more? that's wrong
[08:47] <coNP> Replaces: gaim (<< 1:2.0.0+beta6-3)
[08:48] <StevenK> pitti: Nope. Okay, let's get seb128.
[08:48] <StevenK> pitti: You get the pitchforks, I'll get the flaming torches, and then we can lay in wait. :-)
[08:49] <coNP> Why is gaim needed any more?
[08:49] <StevenK> pitti: I saw no mention of it being dropped in the changelog.
[08:52] <StevenK> pitti: I can upload pidgin adding gaim back, or I can wait, and we can interogate seb128 and ask him what for. :-)
[08:53] <pitti> Package: pidgin
[08:53] <pitti> Binary: pidgin-dbg, pidgin-data, pidgin, pidgin-dev, gaim
[08:53] <pitti> hmm
[08:53] <StevenK> Weird.
[08:54] <pitti> StevenK: seems it's a glitch in archive-cruft-check...
[08:54] <StevenK> pitti: It isn't listed as being published on Launchpad.
[08:54] <pitti>       gaim | 1:2.0.2-0ubuntu1 |         gutsy | all
[08:55] <StevenK> Binary: pidgin-dbg pidgin-dev pidgin-data pidgin
[08:55] <StevenK> (From the i386 build logs)
[08:56] <pitti> weird
[08:56] <StevenK> pitti: Actually, is your Package and Binary paste from 2.0.2?
[08:56] <pitti> yep
[08:57] <StevenK> That's why, it isn't in 2.1.0
[08:57] <pitti> ah, true /me tries to wake up properly
[08:57] <coNP> it seems it is based on a debian sync
[08:58] <pitti> thanks, that helps
[08:59] <StevenK> pitti: So, should I fix pidgin, or shall we ask seb128 what happened?
[09:00] <pitti> StevenK: if you feel like it, please fix it (just a debian/control re-addition, I think)
[09:01] <StevenK> Agreed.
[09:06] <coNP> StevenK: why is it a problem that gaim has been dropped?
[09:07] <infinity> coNP: Upgrade path.
[09:07] <infinity> coNP: How do you upgrade gaim to pidgin if there's no gaim transitional package?
[09:07] <coNP> Is "provides not enough?
[09:07] <pitti> coNP: no, apt won't see that
[09:08] <pitti> coNP: well, it won't install pidgin just because of that
[09:08] <coNP> Oh. I see, many thanks. It seems to be Debian-related.
[09:08] <coNP> Okay I see the problem.
[09:08] <pitti> coNP: you need an actual Conflicts: to coerce apt/dpkg to replace a package
[09:09] <infinity> Sure, we'll just make libc6 conflict with gaim, that'll force the upgrade!
[09:09] <StevenK> pitti: I daresay you trust me enough to just upload it? :-)
[09:09] <pitti> StevenK: sure
[09:09] <StevenK> infinity: :-)
[09:09] <infinity> I look at it every day.  It brings me joy.
[09:09] <infinity> Sometimes I look twice.
[09:10] <infinity> I'd upload, but I fear that sharing that much beauty and perfection with the world may cause mass hysteria and confusion.
[09:10] <StevenK> /dev/mapper/system-home 15G   15G     0 100% /home
[09:10] <StevenK> Sigh
[09:10] <infinity> And so, regretfully, I keep it to myself.
[09:11] <infinity> StevenK: I'm sure you understand.
[09:11] <infinity> (Also, lpia can bite me... That is all)
[09:11] <StevenK> infinity: But I want yada demoted! *bounce impatiently*
[09:13] <infinity> So do I, so do I.
[09:13] <infinity> Patience, young one.
[09:16] <ivoks_> nonexsisting ALLMULTI and RUNNING makes some services broken
[09:18] <ivoks_> is it possible to set those flags somehow? :)
[09:25] <carlos> pitti: btw, Gutsy full export should be ready
[09:25] <pitti> yay
[09:25] <carlos> pitti: the Dapper one should be ready anytime between this afternoon and this evening
[09:26] <pitti> carlos: does the gutsy one also have the problem of dropped .po files?
[09:26] <carlos> pitti: I guess some files would have that problem
[09:26] <carlos> yes
[09:26] <carlos> let me see the log...
[09:27] <carlos> pitti: there are two files in that situation
[09:27] <carlos> so I guess is ok to go ahead and use it
[09:27] <pitti> carlos: something important?
[09:27] <carlos> next full export update will include them (I fixed the problem so future exports should work)
[09:28] <pitti> ok, cool
[09:29] <Tonio_> Mithrandir: ping ?
[09:30] <Hobbsee> Tonio_: on leave
[09:30] <StevenK> Mithrandir is on VAC until Tuesday
[09:30] <carlos> pitti:
[09:30] <carlos>  system-config-kickstart | fr
[09:30] <carlos>  pppoeconf               | zh_TW
[09:30] <Hobbsee> StevenK: ^5 :(
[09:30] <Hobbsee> * :)
[09:30] <Tonio_> StevenK: argh :/
[09:30] <Tonio_> StevenK: well he told me he would upload latest bluez packages before leaving, but it looks like one of them is missing
[09:31] <StevenK> pitti: I'm test building pidgin, since the transitional package also provides symlinks.
[09:31] <Tonio_> oki let's wait a week then ;)
[09:32] <pitti> carlos: ok, doesn't sound too bad, it doesn't affect central desktop packages; I'll use that then
[09:33] <infinity> Don't we modify rmadison to work against a CGI on gluck?
[09:33] <infinity> Cause my rmadison here is hitting qa.debian.org...
[09:33] <infinity> (And clearly isn't modified at all)
[09:34] <stgraber> asac: ping
[09:34] <StevenK> infinity: Trying to query Ubuntu packages?
[09:34] <infinity> StevenK: Yeah.  Just doing it on drescher instead. :P
[09:35] <StevenK> infinity: rmadison -u ubuntu
[09:35] <infinity> Unknown option: u
[09:35] <infinity> Oh, wait.  I bet this snazzy feature was added in gutsy's devscripts.
[09:35] <infinity> And I'm a slacker on feisty.
[09:35] <StevenK> Heh
[09:36] <infinity> I'm still not used to not being distro and, hence, not running development crack...
[09:36] <infinity> On the other hand, the stable system is kinda a pleasant change.
[09:37] <Fujitsu> Stability is boring, though.
[09:37] <infinity> Exceitment is pain.
[09:37] <infinity> Excitement, too.
[09:38] <Fujitsu> I don't think I could live with knowing for sure that my system will work when I boot it up. :P
[09:38] <StevenK> Then turn it off and put an axe through it?
[09:38] <Fujitsu> StevenK: Good idea!
[09:38] <StevenK> Then you'll know for sure it won't work when you boot it up. :-P
[09:39] <infinity> Bugs lead to anger, anger leads to hate, hate leads to dead coworkers.  I'm sure we're all better off with me running stable releases.
[09:39] <StevenK> Maybe I should send you an AGP video card we have here.
[09:39] <Fujitsu> infinity: You have no local coworkers, do yo
[09:39] <Fujitsu> +u?
[09:40] <infinity> I'm willing to travel.
[09:40] <StevenK> The other sysadmin here put a different AGP video card into a server on last Friday and fried the motherboard. The server being a dual Xeon 2GHz expensive thing.
[09:40] <Fujitsu> StevenK: Ooh, nice.
[09:40] <infinity> StevenK: Was he trying to get a better framerate in Doom or something?
[09:43] <lamont> infinity: feisty is love
[09:43] <lamont> well, with gutsy's git-core backported
[09:44] <StevenK> infinity: No, trying to free up a remote management board.
[09:46] <StevenK> Oh, nice one Pidgin. It's Makefile has CFLAGS that contains " -g -g  -O2 -O2"
[09:46] <StevenK> Evidently, it wants to be really sure.
[09:46] <infinity> No harm in that, except for the "HAHA" factor.
[09:46] <infinity> AKA, the Nelson Factor.
[09:47] <StevenK> infinity: Which is why I'm commenting. :-)
[09:47] <infinity> Morning, Michael.
[09:47] <infinity> mvo: I'm not entirely happy with apt, you have a moment?
[09:48] <infinity> Not my day, this one.
[09:49] <mvo> infinity: sure
[09:49] <mvo> good morning infinity
[09:49] <infinity> mvo: Aww, I was hoping for a more entertaining response.
[09:49] <infinity> mvo: (I don't have any issues with apt right now, I just like to see you panic)
[09:50] <mvo> infinity: like 'I'm not happy with apt either' ?
[09:50] <mvo> infinity: don't do this to me in my morning before I had a cup of tea :P
[09:50] <infinity> mvo: Something closer to "dear god, Adam has another obscure apt feature request, where can I hide?"
[09:50] <Hobbsee> hiya mvo.  please dont break things again for the tribe ;)
[09:50] <infinity> mvo: Your last bizarre feature request is holding up well, though.
[09:51] <mvo> Hobbsee: actually that was the plan ... new abi breaking apt today
[09:51] <infinity> mvo: A mainline upload with the SecondaryArch hacks would be cool.  Do you have a branch with those patches on it that I could branch from and help you clean up the code?
[09:51] <StevenK> pitti: Pidgin uploaded.
[09:52] <Hobbsee> calc: please get OOO fixed ASAP.  I dont want to have to boot to windows, and write this long evil report there.
[09:52] <pitti> yay you, thanks
[09:52] <lamont> infinity: s/obscure/obscene/???
[09:52] <mvo> infinity: I have a branch, I just need to check if I pushed it to the world
[09:52] <infinity> lamont: Yeah, or that.
[09:52] <mvo> lamont: :P
[09:52] <infinity> lamont: Have you SEEN the SecondaryArch stuff?  It's just plain wrong.
[09:53] <infinity> (But feels oh so right...)
[09:53] <lamont> mvo: many of infinity's requests are obscene.  not sure how much he's walking in my footsteps, and how much he's leading-out now.
[09:53] <lamont> infinity: lalalalalalalala
[09:54] <mvo> lamont: that is really hard to say, but infinity is definitely creative in his feature reuquests
[09:54] <infinity> lamont: I owe everything I am to having been driven insane by your shell.
[09:54] <lamont> mvo: "creative" ...  I'll have to remember that term
[09:54] <lamont> infinity: dude.  it works.  who needs python/perl/whatever
[09:55] <lamont> ??
[09:55] <infinity> lamont: I do everything in shell too, generally.  But my shell used to be readable until I met you. :P
[09:55] <lamont> learned some tricks? or just fried your brain?
[09:55] <infinity> The latter.
[09:55] <lamont> hehe
[09:56] <lamont> hrm... 2am... I should really sleep soonish
[09:56] <infinity> Wimp.
[09:56] <lamont> I'm only like 3 times your age until you graduate from high school, turkey.
[09:57] <lamont> (I actually expect that I'm less than twice your age...)
[09:57] <infinity> Hey, I'm hitting the big three-oh in a month, I'm feeling more LaMonty every day.
[09:57] <lamont> 44 in a month or so
[09:57] <StevenK> That's three-uh-oh
[09:57] <Hobbsee> you're just all old :P
[09:58] <lamont> after mine
[09:58] <stgraber> morning
[09:58] <lamont> mine's more work, since I'm not on that page anymore.
[09:58] <lamont> iz 11 days before yours
[09:58] <mvo> infinity: welcome to the old-farts club
[09:59] <infinity> lamont: Damn, I was going to use db.debian.org to find yours, but you don't have it listed.
[09:59] <lamont> :-)
[10:00] <infinity> Hrm, neither do I.
[10:00] <infinity> Is that field new?
[10:00] <lamont> I think so
[10:00] <lamont> Fujitsu has been in business since before I was born, I believe
[10:00] <lamont> == not young. :-)
[10:00] <StevenK> Hah
[10:00] <Fujitsu> Heh.
[10:04] <Fujitsu> Hm, why did ubuntu-crashes-universe get subscribed to bug #130089?
[10:04] <ubotu> Bug 130089 on http://launchpad.net/bugs/130089 is private
[10:06] <StevenK> pitti: Get him, he's here!
[10:06] <seb128> ?
[10:06] <mvo> hey seb128!
[10:06] <Hobbsee> Fujitsu: because it's private?
[10:06] <Hobbsee> heya seb128!
[10:06] <seb128> mvo: hello
[10:06] <seb128> Hobbsee: hello
[10:07] <StevenK> seb128: Your Pidgin merge from Debian dropped the gaim transitional package.
[10:07] <Hobbsee> Fujitsu: marked as dead
[10:07] <seb128> StevenK: yes, that's because Debian use the gaim source to build transitional packages now and I'm going to sync that
[10:07] <StevenK> Oh drat, I didn't know that.
[10:07] <Hobbsee> seb128: got any new stuff since the last tribe that should be in the release notes?
[10:07] <seb128> Hobbsee: GNOME 2.19.6
[10:08] <seb128> Hobbsee: transition to rarian
[10:08] <seb128> Hobbsee: fast user switching using consolekit
[10:08] <stgraber> Hobbsee: I think the problem is that it should have been in crashes-main not -universe as notification-daemon is main
[10:08] <StevenK> pitti: Right, what do we do now?
[10:08] <Fujitsu> Hobbsee: The package is in main, though.
[10:08] <Hobbsee> StevenK: ah right
[10:08] <seb128> Hobbsee: gnome-keyring pam integration (coming)
[10:08] <Hobbsee> seb128: great.  pity i dont know what #2 and #3 are :)
[10:08] <seb128> Hobbsee: tracker installed (need some work though)
[10:08] <Hobbsee> seb128: thanks
[10:09] <pitti> hey seb128
[10:09] <seb128> StevenK, pitti: can't you wait for me to show up before uploading desktop things?
[10:09] <seb128> I did drop that transitional package on purpose
[10:09] <seb128> hello pitti
[10:10] <StevenK> But if that was mentioned in the changelog, I wouldn't have questioned it.
[10:10] <seb128> StevenK: why should I have mentionned it? that's a merge, I mention only things we add there, not every change we don't do
[10:10] <pitti> seb128: oh, you want to have a separate source package which only builds a transitional package?
[10:10] <seb128> pitti: yes, what Debian does and what we can sync
[10:11] <seb128> easier
[10:11] <pitti> hmkay; sorry then...
[10:11] <seb128> StevenK: I'm on IRC often enough to wait for me to be connected and ask before uploading random changes
[10:11] <StevenK> seb128: Shall I revert my change and grovel at your feet?
[10:11] <seb128> not that's ok
[10:11] <Fujitsu> Can someone please give back mysql-admin on i386 and powerpc?
[10:11] <seb128> I still have my upload from yesterday, I'll dch on it and upload
[10:11] <StevenK> seb128: Okay. Sorry for the trouble.
[10:12] <seb128> that's alright
[10:12] <seb128> thanks for the work
[10:13] <pitti> seb128: ok, next time we'll wait; perdon
[10:13] <seb128> if that's a package I maintain actively though better to ask before doing changes
[10:13] <seb128> usually I don't screw to much and there might be a reason for a change ;)
[10:13] <seb128> s/to/too
[10:13] <seb128> pitti: that's alright
[10:21] <tuxcrafter> Can somebody explain to me the difference between libc6and libc6-i686and why  they are both installed. And what happens if I have removed libc6-i686?
[10:22] <seb128> tuxcrafter: apt-cache show libc6-i686
[10:22] <tuxcrafter> in fedora you can install only one
[10:23] <Seveas> ubuntu is not fedora
[10:23] <Seveas> and #ubuntu-devel is not for support :)
[10:23] <infinity> We're obviously more clever.
[10:24] <tuxcrafter> infinity: exactly
[10:24] <tuxcrafter> Filename: pool/main/g/glibc/libc6_2.5-0ubuntu14_i386.deb
[10:24] <tuxcrafter> oke so if i remove  libc6-i686
[10:25] <infinity> Then you don't have a 686-optimised libc anymore.
[10:25] <tuxcrafter> it will automatic be take over by ibc6_2.5-0ubuntu14_i386.deb
[10:25] <tuxcrafter> and i will use i386 instructions
[10:25] <infinity> i486, actually, but yeah.
[10:25] <tuxcrafter> on my i686 cpuy
[10:26] <seb128> tuxcrafter: where do you want to go with that?
[10:27] <tuxcrafter> is there some trick to let linux think there is an i386 machine instead of an i686
[10:27] <seb128> tuxcrafter: if the optimized version is installed it's used, if it's not installed it's not used
[10:27] <seb128> seems to be logical, no?
[10:27] <tuxcrafter> there is an bug with the via C7 cpu and glibc / libc6 thanks makes the system get a total lockup
[10:28] <tuxcrafter> under fedora we could fix this by only using i386 instructions
[10:28] <tuxcrafter> but we want this also on ubuntu
[10:28] <tuxcrafter> just for testing
[10:28] <seb128> uninstall the i686 package?
[10:29] <tuxcrafter> seb128: yes i will do this, but i needed to be sure it has the wanted effect
[10:29] <seb128> pitti: I'm doing syncs, you are busy enough and I've nothing urgent to do
[10:29] <tuxcrafter> so I came to this cannel
[10:29] <pitti> seb128: ah, thanks; appreciated
[10:30] <pitti> Riddell: I published the koffice and qt updates now, waiting for them to appear before sending out USNs
[10:31] <tuxcrafter> apt-cache show glibc-2.5.0-0exp1 and ..exp2 does not show any information
[10:31] <infinity> Why would it?
[10:31] <infinity> That's not a package name.
[10:31] <tuxcrafter> whould be nice
[10:31] <tuxcrafter> ow
[10:34] <pitti> seb128: alternatively, if you feel like it, there's https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/129940
[10:34] <ubotu> Launchpad bug 129940 in koffice "[XPDF]  possible buffer overflow and execution of arbitrary code" [Undecided,Fix committed] 
[10:35] <seb128> pitti: will have a look to that as well
[10:35] <ogra> pitti, could you update mkelfimage ? Q-Funk fixed the build in -3 in debian
[10:36] <pitti> ogra: right, I remember, I sponsored the upload
[10:36] <pitti> ogra: I'll sync it (unless seb128 is doing syncs ATM)
[10:36] <tuxcrafter> seb128: thank you for the information, i did every thing i could on a default xubuntu installation run the i368 kernel and removed libc6-i686
[10:36] <ogra> pitti, thanks :)
[10:36] <tuxcrafter> good luck with gusty everybody
[10:37] <tuxcrafter> gutsy
[10:37] <seb128> tuxcrafter: you're welcome
[10:37] <seb128> thanks
[10:37] <ogra> pitti, and please, please dont make dhcp use a static interface setup, that will make our lifes in ltsp support lots harder :(
[10:37] <pitti> ogra: no, I wasn't planning to :) (it was just an example more or less)
[10:38] <ogra> phew
[10:38] <ogra> you scared me :)
[11:02] <Fujitsu> pitti: If you haven't got anything better to do, can you please give back mysql-admin on {i386,powerpc}?
[11:04] <tkamppeter> hi pitti
[11:04] <pitti> Fujitsu: I have, byt that's quick :) done
[11:04] <pitti> hi tkamppeter
[11:04] <pitti> tkamppeter: just answered your mail, thanks for pointing out
[11:06] <tkamppeter> pitti, this means that the aa protection for CUPS should be only optional?
[11:06] <pitti> tkamppeter: in gutsy final I want it installed by default
[11:06] <pitti> tkamppeter: but -profiles is supposed to stay in universe for gutsy
[11:07] <pitti> tkamppeter: so either the #includes move to apparmor itself, or I'll drop the #includes and copy their contents
[11:07] <tkamppeter> From the two solutions which you suggest in your mail I prefer the one of movin the includes into the aa main package.
[11:07] <pitti> tkamppeter: me too, it makes most sense
[11:07] <pitti> (for custom profiles installed by the admin, too
[11:08] <tkamppeter> under no circumstances you should move the CUPS profile into the aa package. This profile should stay with CUPS.
[11:09] <tkamppeter> Also copying the contents of the includes into the CUPS profile is bad, as then one has a duplicate implementation of one thing which is bad for maintainability.
[11:09] <Hobbsee> holy cow
[11:10] <tkamppeter> pitt, so you are filing a bug now for moving the profiles into the main package of aa?
[11:10] <Fujitsu> pitti: Thanks.
[11:10] <pitti> tkamppeter: bug 130114
[11:10] <ubotu> Launchpad bug 130114 in apparmor "#include files should be in apparmor itself" [Undecided,New]  https://launchpad.net/bugs/130114
[11:11] <pitti> tkamppeter: I agree, that's my favourite as well
[11:11] <pitti> tkamppeter: (why oh why does Mike even reject such simple and nonintrusive patches like adding a PidFile option??)
[11:13] <pitti> tkamppeter: sorry, I don't have time ATM to look into bug 103878
[11:13] <ubotu> Launchpad bug 103878 in python-cups "[apport]  system-config-printer.py crashed with SIGSEGV in free() //trying to print test page on my Canon i560 " [Medium,New]  https://launchpad.net/bugs/103878
[11:14] <Hobbsee> ooo actually works, it seems.
[11:19] <cjwatson> drago: authoritatively (and agreed with your boss ;-)), 2.6.15
[11:21] <drago> cjwatson: OK. tks for attention ;-)
[11:24] <tkamppeter> pitti, I cannot reproduce bug 103878, it simply works for me. Seems to be already fixed upstream.
[11:24] <ubotu> Launchpad bug 103878 in python-cups "[apport]  system-config-printer.py crashed with SIGSEGV in free() //trying to print test page on my Canon i560 " [Medium,New]  https://launchpad.net/bugs/103878
[11:25] <tkamppeter> pitti, so perhaps there is nothing to do. Perhaps better to ask Tim Waugh.
[11:25] <pitti> tkamppeter: can you please ask the reporter to check in gutsy?
[11:27] <tkamppeter> pitti, done.
[11:52] <carlos> seb128: hi
[11:52] <seb128> hello carlos
[11:52] <carlos> seb128: is a known bug that 'Places' entries doesn't get the Music, Pictures, etc... folders if you change them by hand?
[11:53] <seb128> what do you mean "change them by hand"?
[11:53] <carlos> seb128: edit ~/.config/user-dirs.dirs , rename directories and restart the session
[11:54] <carlos> after that, Places doesn't have the updated entries
[11:54] <seb128> carlos: they are GTK+ bookmarks I think and not updated dynamically
[11:54] <seb128> carlos: what is listed to .gtk-bookmarks?
[11:54] <carlos> seb128: I see, I guess it makes sense
[11:54] <carlos> right, that's the problem
[11:55] <carlos> it points to old directories
[11:55] <carlos> seb128: is there any UI to do this change?
[11:55] <seb128> you can change bookmarks from nautilus
[11:55] <seb128> in the shortcut menu
[11:56] <carlos> I mean to edit everything in one single step
[11:56] <seb128> no
[11:56] <carlos> ~/.config/user-dirs.dirs + bookmarks
[11:56] <carlos> ok
[11:57] <carlos> seb128: is there any tool planned to do it?
[11:57] <seb128> not that I know but I would not be surprised if somebody gets annoyed enough to write one
[11:58] <carlos> ok :-)
[11:58] <carlos> seb128: thanks for your help
[11:58] <seb128> you're welcome
[12:10] <Hobbsee> pitti: since when could you read my mind?
[12:11] <pitti> Hobbsee: forever, why?
[12:11] <Hobbsee> pitti: ah right :P
[12:11] <Hobbsee> pitti: was just going to ask you to shove a sync i just filed, to give a hopeful a chance to fix it tonight
[12:12] <Hobbsee> and then i saw my email :)
[12:13] <pitti> Hobbsee: that was seb128, though
[12:13] <seb128> k, I'm done with syncs, removal and backports cleaning
[12:13] <mvo> thom: did you had a chance to test the https patch I send to you? I would like to merge it if it works for you
[12:13] <seb128> pitti: ^
[12:13] <pitti> seb128: you rock, thanks
[12:13] <seb128> you're welcome
[12:14] <seb128> pitti: when you have a minute can you have a look to cheese in source new?
[12:14] <seb128> pitti: it should be easy, I did sponsor the upload so I would prefer have somebody else having a quick look at it
[12:14] <pitti> seb128: when you got a minute, can you please test http://people.ubuntu.com/~pitti/tmp/gutsy-langpack/ for French?
[12:14] <pitti> seb128: sure, will do
[12:15] <seb128> pitti: ok, looking now to the language pack update
[12:15] <pitti> seb128: ^ those are new gutsy langpacks (fresh -base for tribe CDs)
[12:17] <thom> mvo: no, going to do so in a minute
[12:18] <seb128> pitti: the restricted-manager po has been dropped
[12:18] <seb128> the mo rather
[12:18] <seb128> pitti: same for freetype
[12:18] <pitti> bwah
[12:19] <pitti> carlos: ^ ?
[12:19] <seb128> and gdebi is new ;)
[12:19] <mvo> thom: thanks!
[12:21] <thom> just need to get it to build on edgy ;)
[12:25] <mvo> thom: let me know if that is a problem, I can build something for you if it does not apply cleanly or anything like this
[12:26] <Nafallo> mvo: fluendo reminder :-)
[12:26] <mvo> Nafallo: haha, thanks!
[12:26] <Nafallo> :-P
[12:27] <Nafallo> mvo: I'll remind you later then ;-)
[12:29] <seb128> hum, lunch ;)
[12:31] <Nafallo> lunch!
[12:33] <thom> mvo: compared to the rest of the packaging madness i've suffered this week, backporting apt is trivial :)
[12:41] <thom> mvo: looks good, go for it
[12:44] <pitti> carlos: did you see above problems with  the gutsy langpack? (missing restricted-manager and freetype)
[12:48] <mvo> thom: rock, thanks a lot!
[12:54] <pitti> asac: can you please make bug 119038 conformant to SRU requirements? i. e. verify that it is fixed in gutsy, attach reproducing instructions for verifiers, subscribe ubuntu-sru, etc.
[12:54] <ubotu> Launchpad bug 119038 in enigmail "MASTER Key management / Recipient Key Selection broken (endless loop in EnigConvertToUnicode)" [High,In progress]  https://launchpad.net/bugs/119038
[12:55] <pitti> ugh, quite a patch
[12:55] <carlos> pitti: no, I didn't see it
[12:55] <carlos> let me check...
[12:58] <carlos> pitti: could I see more details?
[12:58] <pitti> carlos: <seb128> pitti: the restricted-manager po has been dropped
 the mo rather
 pitti: same for freetype
[12:58] <carlos> freetype is not available in Gutsy, but restricted-manager is
[12:58] <pitti> carlos: restricted-manager moved from main to restricted a while ago, could that be it?
[12:58] <asac> pitti: isn't https://wiki.ubuntu.com/MOTU/SRU the document describing the procedure?
[12:59] <carlos> pitti: for sure, that's it
[12:59] <carlos> pitti: we only have main packages
[12:59] <pitti> asac: no, it's in main, therefore https://wiki.ubuntu.com/StableReleaseUpdates
[12:59] <pitti> carlos: d'oh, why?
[12:59] <carlos> pitti: dude, because language packs are only for main
[12:59] <carlos> nothing changed here...
[01:00] <pitti> carlos: hm, too bad; can we have restricted? it's supported and isntalled by default, after all?
[01:00] <carlos> pitti: if you tell me that restricted should be handled in language packs now, we can change it without problems
[01:00] <pitti> seb128: hm, I guess we'll go with those langpacks then for now, and fix that later
[01:00] <pitti> carlos: that would be cool
[01:00] <carlos> pitti: this means that your script should strip off translations from restricted packages too
[01:00] <pitti> carlos: for most stuff in restricted it probably doesn't matter, since most of it doesn't have po files
[01:01] <pitti> carlos: right, good point; I'll do that
[01:01] <carlos> pitti: the problem is that until we 'fix' launchpad no translations will be imported
[01:02] <pitti> carlos: can I get the old translations still? and put them into upstream bzr?
[01:02] <carlos> pitti: I will need to check with kiko whether I could get this cherry picked or whether you need to wait until 1.1.8 milestone (later this month)
[01:02] <carlos> pitti: yeah, for restricted-manager is not a problem
[01:02] <pitti> carlos: if I can get the .po files, then waiting a bit is no problem
[01:02] <carlos> it's still available
[01:02] <pitti> carlos: right, just for that one
[01:02] <carlos> and I could include its translations in next full export without major problems
[01:03] <carlos> but my point is that newer .pot files will not be uploaded into launchpad until we allow restricted packages to be imported
[01:03] <carlos> ok
[01:04] <carlos> pitti: https://translations.launchpad.net/ubuntu/gutsy/+source/restricted-manager/+pots/restricted-manager/+export
[01:04] <carlos> pitti: you can get the .po files now if you want
[01:04] <pitti> carlos: thanks a lot
[01:06] <Kmos> PHP 5.2.4 RC1 is out.. let's test it :)
[01:09] <asac> pitti: bug 119038 updated ... as you wished
[01:09] <ubotu> Launchpad bug 119038 in enigmail "MASTER Key management / Recipient Key Selection broken (endless loop in EnigConvertToUnicode)" [High,In progress]  https://launchpad.net/bugs/119038
[01:10] <pitti> asac: cheers
[01:11] <pitti> asac: ah, so the gutsy task can be closed, I figure; thanks
[01:11] <asac> was it ever opened?
[01:12] <pitti> asac: yes, it was 'in progress'
[01:12] <asac> i don't see a gutsy task ... just main task + dapper/edgy/feisty
[01:12] <asac> oh ... so you say that main task is gutsy task?
[01:12] <pitti> right 'main' -> development rellease -> gutsy ATM
[01:12] <asac> ok
[01:13] <asac> the visualisation as root node of the task tree is a bit confusing then
[01:14] <asac> pitti: its really a bit confusing that you have MOTU/SRU + StableReleaseUpdates
[01:14] <asac> pitti: i just searched for SRU :)
[01:14] <pitti> asac: yeah; StableReleaseUpdates was there first, though
[01:14] <asac> pitti: and there are even two SRU documents that appear to be somehow redundant ... SRU + Process/SRU
[01:14] <pitti> eek
[01:14] <asac> what shall we do about that?
[01:15] <asac> i mean ... maybe we say: wiki.ubuntu.com/SRU/Main
[01:15] <asac> SRU/MOTU ?
[01:15] <asac> or ... just use one policy for all
[01:15] <asac> e.g. just SRU aka StableReleaseUpdates
[01:16] <pitti> asac: Processes/SRU redirects to MOTU/SRU already
[01:16] <asac> ah
[01:17] <asac> pitti: maybe we can make one policy document out of it ... with a section for "special main requirements" ?
[01:17] <pitti> asac: not sure whether this would be more easy to read
[01:17] <pitti> asac: but the packages should link to each other at least
[01:17] <pitti> with a prominent warning about main/universe
[01:17] <asac> right ... i will add those links on top for now
[01:17] <pitti> policy changes on one don't automatically apply to the other, after all
[01:18] <pitti> asac: thank you
[01:20] <pitti> asac: enigmail again> what about the 'dapper ftbfs' changelog bit in the edgy diff?
[01:23] <asac> pitti: it fails on edgy too
[01:24] <pitti> asac: ok, so it's just a copy&paste glitch in the changelog and actually necessary?
[01:24] <pitti> good
[01:24] <asac> sorry for the inaccurate changelog ... copy&paste error
[01:24] <pitti> ok, np; I just want to make sure
[01:24] <asac> yes ... needed ... don't ask me why it fails now
[01:24] <asac> its black-magic ... but it does
[01:25] <pitti> bug updated
[01:25] <asac> thanks
[01:32] <carlos> pitti: https://bugs.launchpad.net/rosetta/+bug/130138
[01:32] <ubotu> Launchpad bug 130138 in rosetta "Allow translations imported for 'restricted' pocket" [Undecided,New] 
[01:32] <carlos> pitti: just in case you want to track it
[01:32] <pitti> carlos: thanks, I'll subscribe
[02:10] <Kmos> Can I do a request sync for gambas to fix it (because it only builds on i386) - http://packages.qa.debian.org/g/gambas/news/20070702T140204Z.html ?
[02:14] <Hobbsee> Kmos: looks smart
[02:15] <Kmos> Hobbsee: not enough for a sybc ?
[02:15] <Kmos> *sync
[02:16] <Hobbsee> Kmos: looks worthy of a sync, to fix the ftbfs on the other arches
[02:16] <Kmos> jono: hey
[02:16] <jono> hey
[02:17] <Kmos> Hobbsee: i'll request the sync soon
[02:17] <Hobbsee> hi jono
[02:18] <Hobbsee> (and any other archive admins interested)
[02:23] <seb128> re
[02:23] <seb128> carlos, pitti: fine with me for the language pack update
[02:29] <cjwatson> doko,agoliveira_brb: re the conversation in #ubuntu-meeting last night, the germinate output in http://people.ubuntu.com/~ubuntu-archive/germinate-output/gutsy/ already looks at universe and multiverse as well as main and restricted, so you should be able to use it to build the list of source packages for lpia bootstrapping
[02:30] <cjwatson> I'm seeing if I can give you an automated compiled list now
[02:33] <cjwatson> doko,agoliveira_brb: how about http://people.ubuntu.com/~ubuntu-archive/gutsy-lpia-sources ?
[02:33] <cjwatson> 561 /home/ubuntu-archive/public_html/gutsy-lpia-sources
[02:34] <doko> cjwatson: minus the binary-all packages, if you have this information handy?
[02:34] <cjwatson> I can give it a try
[02:34] <cjwatson> and presumably minus Architecture: powerpc and the like
[02:34] <cjwatson> though actually the germinate output that's generated from is for i386 so that's not relevant
[02:36] <doko> well, currently you don't get correct dependencies for lpia, because many packages are still missing
[02:39] <cjwatson> indeed
[02:43] <cjwatson> doko: I think that's right now
[02:43] <cjwatson> 396 public_html/gutsy-lpia-sources
[02:43] <cjwatson> for x in required minimal standard mobile mobile-dev; do for y in "$x" "$x.build-depends"; do tail -n +3 "$HOME/public_html/germinate-output/gutsy/$y" | head -n -2 | cut -d\| -f1,2 --output-delimiter=' ' | tr -s ' ' | sed 's/^ *//; s/ *$//'; done; done | sort -u >"$TMPDIR/germinate"
[02:43] <cjwatson> for c in main restricted universe multiverse; do wget -q -O- http://archive.ubuntu.com/ubuntu/dists/gutsy/$c/binary-i386/Packages.gz | zcat; done | grep-dctrl -nsPackage -vXFArchitecture all | sort -u >"$TMPDIR/not-all"
[02:44] <cjwatson> join -o 1.2 "$TMPDIR/germinate" "$TMPDIR/not-all" | sort -u >"$HOME/public_html/gutsy-lpia-sources"
[02:44] <cjwatson> hello, SQL in shell
[02:44] <doko> hello or hell?
[02:44] <cjwatson> I meant the former, though either would do :)
[02:49] <StevenK> infinity: Is it libnss-db time yet? :-P
[02:50] <cjwatson> doko: I'm not sure I can easily split that up by priority, since the list is by source package so I'd have to fish out priorities for all the binary packages and compare them and stuff
[02:50] <cjwatson> but hopefully <400 is accessible enough that that's less of a problem
[02:53] <cjwatson> doko: can you have the existing wiki list in a form that you can automatically cross-reference with that? maybe wget ?action=raw, munge, join
[02:53] <doko> no, that's ok,
[02:54] <doko> will look at it
[02:55] <cjwatson> if you can prepare a shell snippet that prints out the list of remaining packages by fetching the list of done packages from the wiki and subtracting them off, I could make that output to ~ubuntu-archive/something as well
[02:58] <pitti> Hobbsee: back from lunch, what's up?
[02:59] <Hobbsee> pitti:
[02:59] <Hobbsee> [22:16]  <kiko> so the new queue UI is live:
[02:59] <Hobbsee> [22:16]  <kiko> https://edge.launchpad.net/ubuntu/gutsy/+queue
[02:59] <Hobbsee> [22:16]  <kiko> Hobbsee, you can now inspect packages directly
[03:02] <pitti> Hobbsee: that's awesome!
[03:03] <Hobbsee> pitti: yeah!
[03:05] <seb128> pitti: good, now other people can do reviews ;)
[03:08] <pitti> seb128: shall I sync gaim from Debian then?
[03:08] <seb128> pitti: feel free to do it, I'll upload pidgin, the update from this morning should be available now
[03:09] <pitti> seb128: ah, cool
[03:11] <pitti> seb128: hmm, not sure whether this will work... 'gaim' binary is at 2.0.2, while the fake gaim is 2.0.0
[03:11] <pitti> elmo: gaim is in main but its source (gaim) is not.
[03:11] <pitti> elmo: sorry, that was "E:"
[03:11] <pitti> seb128: sync failure ^
[03:12] <pitti> seb128: I'll --force it away, but it's still a bit fishy
[03:12] <pitti> seb128: I'll also promote gaim binary to main
[03:12] <seb128> pitti: we need to take the Debian package and dch it to add a new revision number
[03:13] <pitti> seb128: if you do that, then it might be easier to just keep the transitional package in pidgin...
[03:13] <pitti> but your call
[03:13] <seb128> pitti: hum
[03:14] <seb128> let me think about it, there is no hurry
[03:14] <pitti> ok
[03:14] <seb128> but adding new binary packages to pidgin is non trivial
[03:14] <seb128> where running dch on a package is
[03:14] <StevenK> It so is, it took me three minutes.
[03:15] <pitti> seb128: that's done already, question is how much effort it is to maintain it until 8.04 release
[03:15] <seb128> StevenK: should I say I admire you or something like that for being so quick? ;)
[03:15] <pitti> seb128: we can drop this after the next LTS, after all
[03:15] <StevenK> seb128: *shrug*
[03:15] <seb128> k, let it your way if you prefer
[03:16] <seb128> I'm not going to argue against that
[03:16] <cjwatson> CD builds should be alive again; I just turned the cron jobs back on
[03:16] <seb128> I've other things to do
[03:16] <pitti> cjwatson: yay
[03:16] <cjwatson> with a local rebuild of mkisofs, but who's counting
[03:16] <pitti> what was the new name of lithium now?
[03:17] <pitti> phosphor? iridium? uranium? helium? :)
[03:17] <cjwatson> antimony
[03:17] <cjwatson> Li -> Sb
[03:18] <pitti> cjwatson: thanks
[03:21] <pitti> asac: sunbird binary NEWed FYI
[03:23] <Company> pitti: ping
[03:23] <pitti> Company: I just said something three seconds ago :) Hi
[03:24] <Company> i just joined ;)
[03:24] <pitti> Company: right, nevermind
[03:24] <Company> pitti: i want apport to have a "i'm a developer, give me the stacktrace" button
[03:24] <pitti> Company: I agree, that would be nice
[03:25] <Kmos> a Save button, but also submit it :)
[03:25] <pitti> Company: it's quite a lot of effort to generate this on the client side, though
[03:25] <pitti> Company: that's bug 75901 FYI
[03:25] <ubotu> Launchpad bug 75901 in apport "Integrate apport-retrace into GUI" [Wishlist,Confirmed]  https://launchpad.net/bugs/75901
[03:25] <Company> pitti: good, i guessed you were aware of the issue :)
[03:26] <Company> i'm hitting it with the swfdec mozilla plugin - when epiphany crashes, i'd like to see the trace
[03:26] <pitti> Company: yeah, it's just a moderate amount of work to port it to the three frontends
[03:26] <pitti> Company: I mean, you can run apport-retrace on your box today, so it's not very hard
[03:27] <pitti> but it doesn't have a button yet :0
[03:27] <Company> heh
[03:27] <Company> stereotypical gnome user
[03:31] <superm1> Any udev hackers around?  I was was looking for a workaround to using RUN+="/etc/init.d/SCRIPT restart" for hotplug events, since it seems to hang if i try that
[03:33] <pitti> seb128: btw, did you already change the seeds for rarian?
[03:33] <seb128> pitti: no, neither that nor consolekit nor tracker
[03:34] <pitti> ah, seems I should stop attacking NEW and start looking at CK; I still gotta do the RM bits for today
[03:35] <seb128> pitti: https://wiki.ubuntu.com/MainInclusionReportConsolekit is about consolekit, is that you who should look at accept it or iwj?
[03:35] <pitti> seb128: yes, it is
[03:35] <seb128> I would appreciate if that could be done today
[03:35] <pitti> so I'll just do cheese and then turn my attention to that
[03:35] <seb128> so we can add it to desktop now
[03:35] <seb128> thanks
[03:47] <pitti> dendrobates: so that auth-client-config in source NEW from Jamie Strandboge is what you need for server?
[03:47] <dendrobates> pitti: what about auth-client-config?  It was written by jdstrand, as part of my ldap-auth-client .
[03:48] <pitti> just curious
[03:48] <dendrobates> Yes.  It will allow a user to use a template to configure pam and nss.
[03:49] <dendrobates> Currently, it uses python ConfigParser, but I would like to switch to something better for the templates.  XML perhaps.
[03:50] <pitti> ok, package looks fine, accepted
[03:50] <dendrobates> BTW,There is nothing server specific about any of the stuff I am doing.  So far it is all client side stuff.
[03:54] <dendrobates> pitti: thanks.
[03:55] <pitti> hi mathiaz
[03:55] <mathiaz> hi pitti
[03:55] <pitti> mathiaz: do you think that bug 130114 is reasonable?
[03:55] <ubotu> Launchpad bug 130114 in apparmor "#include files should be in apparmor itself" [Undecided,New]  https://launchpad.net/bugs/130114
[03:56] <mathiaz> pitti: makes sense.
[04:03] <mathiaz> pitti: about bug 129920
[04:03] <ubotu> Launchpad bug 129920 in apache2 "/var/lock/apache2 has wrong owner and group for webdav" [Low,In progress]  https://launchpad.net/bugs/129920
[04:03] <mathiaz> I've used nominate bug instead of adding feisty in the url.
[04:04] <mathiaz> if after that I close the bug for as fix released I can't find it anymore.
[04:04] <mathiaz> ie the bug is not listed under /ubuntu/feisty/+source/...
[04:06] <ScottK> mathiaz: I believe there is an open LP bug about that.
[04:06] <pitti> mathiaz: but over the non-release URL you should still see it
[04:07] <mathiaz> pitti: by non-release, you mean ubuntu/+source/... ?
[04:07] <pitti> mathiaz: yes
[04:08] <mathiaz> pitti: I don't think so, as it's marked as Fix released.
[04:08] <mathiaz> I had this problem for a bug in mysql-dfsg
[04:08] <pitti> https://launchpad.net/ubuntu/+source/apache2/+bugs
[04:08] <pitti> I see it here
[04:08] <mathiaz> I used nominated for a release, then marked as Fix released. Now I cannot find it anymore
[04:09] <pitti> and here https://launchpad.net/ubuntu/feisty/+source/apache2/+bugs
[04:09] <mathiaz> pitti: yes - that's because bug 129920 is not marked as fix released.
[04:09] <ubotu> Launchpad bug 129920 in apache2 "/var/lock/apache2 has wrong owner and group for webdav" [Low,In progress]  https://launchpad.net/bugs/129920
[04:09] <mathiaz> pitti: let me try to find the mysql-dfsg bug
[04:12] <mathiaz> pitti: hum. I can't find it anymore.
[04:13] <pitti> mathiaz: that was the bug, right? :)
[04:13] <mathiaz> pitti: anyway, it's better to use the url hack over the nominate ?
[04:13] <pitti> mathiaz: nominate works again for me at least
[04:13] <pitti> but it shouldn't make a difference
[04:14] <mathiaz> pitti: well - yesterday I used nominate, but there wasn't any task for feisty that was created.
[04:14] <mathiaz> pitti: that's why I didn't mark it as 'Fix released' for gutsy.
[04:14] <mathiaz> pitti: as I though I would 'loose' the bug.
[04:15] <pitti> mathiaz: I don't remember any more, I might have accepted the feisty task
[04:15] <mathiaz> pitti: that's my point. If I use the url hack, the release task shows up directly.
[04:16] <mathiaz> pitti: but if I use nominate, someone else has to accept (a member of the driver I guess) - correct ?
[04:16] <pitti> mathiaz: I can do this again, so it's apparently restricted to a group you aren't a member of
[04:16] <pitti> mathiaz: I'm not in -drivers and I can accept
[04:16] <pitti> mathiaz: are you in ubuntu-qa?
[04:17] <pitti> I'll be right back
[04:17] <Hobbsee> pitti: you're in release thoguh.  i thought it was ~ubuntu-dev
[04:18] <ScottK> For accepting tasks I'm pretty sure you need to be MOTU or core-dev for Universe/Main packages.  -qa just gets you importance, IIRC.
[04:19] <pitti> Hobbsee: yeah, -release might be it
[04:19] <Hobbsee> it's certainly not drivers
[04:19] <Hobbsee> but i though tit was ~ubuntu-dev now
[04:21] <pitti> iwj, seb128: hm, I just wanted to test f-u-s with new gdm, but the password dialog now doesn't allow me to click any button; mouse clicks don't work at all
[04:21] <seb128> pitti: how do you switch?
[04:22] <iwj> pitti: Freaky.
[04:22] <pitti> seb128: System -> quit -> switch
[04:22] <iwj> Can you log in by typing ?
[04:22] <pitti> seb128: ah, after opening a new session and Ctrl+Alt+F7, that second time the mouse worked
[04:22] <pitti> iwj: yeah, typing and tab+enter to select a button works
[04:22] <iwj> Why do you need to select a button ?
[04:22] <iwj> I mean, not that you shouldn't be able to ...
[04:22] <pitti> iwj: default is 'unlock', I wanted 'switch user'
[04:23] <pitti> door bell
[04:23] <iwj> Oh, on the unlock password prompt screen.
[04:24] <iwj> Wait a moment.  System / quit / switch  ought to produce a new gdm, not a screen lock.
[04:26] <infinity> If it's producing a screen lock, the second X is crashing. :P
[04:26] <iwj> That would be consistent with the mouse being broken somehow.
[04:26] <iwj> I mean, the mouse might have been messed up by the second X.
[04:28] <pitti> re
[04:29] <pitti> iwj: it still locks the screen by default before
[04:29] <iwj> Yes.  It locks the screen you're leaving and is supposed to start a new X server with a gdm flexiserver.
[04:29] <pitti> erk, and now ctrl+alt+Fn doesn't work any more
[04:29] <iwj> Definitely an X bug then.
[04:29] <pitti> it definitively did before I started that second X session
[04:30] <pitti> how am I supposed to switch now?
[04:30] <iwj> You can use chvt if you like.
[04:30] <iwj> But that may not work either.
[04:31] <iwj> Can you reproduce these problems ?  If so then the X people will thank you for your bug report :-).
[04:31] <pitti> nope, it doesn't
[04:31] <pitti> yes, I can
[04:31] <pitti> I just tried the 'switch user' button in the logout dialog again, again no mouse
[04:31] <iwj> Good.  Err, well, better than random lossage, anyway.
[04:31] <pitti> and this time I cannot even switch users any more
[04:31] <pitti> "Too many X screens"
[04:31] <iwj> No, I mean, start from a fresh boot.
[04:31] <iwj> Too many X screens ?
[04:31] <iwj> How many do you have ?
[04:31] <pitti> iwj: believe it or not. TWO!
[04:32] <pitti> my usual one, and the test user session I just started before
[04:32] <StevenK> Evidently, two is too many.
[04:32] <pitti> (I think; I don't know, I can't switch any more after all)
[04:32] <iwj> Even if it were leaking sessions it's supposed to go up to 50 or 60 or something.
[04:32] <StevenK> pitti: ssh in and run w, that'd tell you.
[04:32] <iwj> I think that's probably a misdiagnosis then.
[04:33] <pitti> seb128: anyway, this stuff is gdm/g-s-s or so; CK itself seems quite harmless to me, and "advanced static code analysis" (IOW: grep for usual vuln patterns) didn't show anything, so please go ahead and seed it
[04:33] <pitti> StevenK: point
[04:33] <seb128> pitti: ok, doing it
[04:33] <pitti> joe      pts/5        2007-08-03 16:21 (:22.0)
[04:33] <pitti> joe      tty12        2007-08-03 16:21 (:22)
[04:33] <seb128> thanks
[04:33] <pitti> that's the second one
[04:33] <iwj> pitti, seb128: Yay, thanks.
[04:33] <iwj> grep> I did that too :-).
[04:34] <pitti> iwj: "grep -r alloc" was impressively small
[04:34] <iwj> It likes to start at about :20 IIRC.
[04:34] <seb128> pitti: I'll add fast-user-switch-applet to the MIR queue soon, time to write it
[04:34] <iwj> pitti: Most of the actual memory allocation is dbus or gobject craziness which uses new and init and names like that.
[04:34] <pitti> so, I don't usually use that "switch user" button in the logout dialog, so it might have been broken before CK and the new gdm
[04:34] <pitti> iwj: right, but that's usually fine
[04:34] <iwj> pitti: Right.
[04:35] <pitti> iwj: I'm particularly looking for stuff like malloc(n * sizeof(foo)) and such
[04:35] <iwj> broken before> Do you normally do VT switching at all ?
[04:35] <pitti> (integer overflow)
[04:35] <iwj> pitti: Mmm.
[04:35] <pitti> iwj: yes, I do
[04:35] <pitti> iwj: both to the text consoles, and other X screens
[04:35] <iwj> And no trouble ?  You use gdmflexiserver ?
[04:35] <pitti> but for the latter I just got used to Alt+F2 gdmflexiserver -l
[04:35] <pitti> iwj: I do
[04:35] <pitti> iwj: but with -l, since that 'lock screen by default' annoys me
[04:35] <iwj> Ah, but not starting a new X when the VC is currently another X ?
[04:36] <pitti> iwj: if I run "gdmflexiserver -l" in my current X, that should be the case
[04:36] <pitti> iwj: Alt+F2 in the sense of the gnome "run command" dialog, not Ctrl+Alt+F2 (switch to VT)
[04:36] <iwj> Yes.  That's approximately what the switch user logout dialogue does.
[04:36] <iwj> OIC.
[04:36] <iwj> Mysterious.
[04:37] <pitti> aah
[04:37] <iwj> Maybe some kind of hideous race, but between what ?
[04:37] <pitti> so Ctrl+Alt+F12 actually works
[04:37] <pitti> that brings me to that 'joe' session
[04:37] <pitti> (I'm used to normal X on 7 and second X on 9, but now the first session is on 9)
[04:38] <iwj> Which one the first session is on seems to vary, annoyingly.
[04:38] <iwj> That is, if you switch users a bit you can end up with the first one moving itself from 7 to 9.
[04:38] <pitti> right, that's what apparently happened
[04:38] <iwj> But we still don't understand this mouse thing, right ?
[04:39] <pitti> right
[04:39] <iwj> You selected switch user and got a gnome-screensaver unlock prompt ?
[04:39] <pitti> and why my text VTs are broken
[04:39] <iwj> In which the mouse didn't work ?
[04:39] <pitti> yep
[04:39] <iwj> Your text VTs are broken ?
[04:39] <iwj> I definitely blame X.
[04:39] <pitti> well, I cannot switch to them any more after the first user switch
[04:39] <iwj> What does chvt 2 do ?
[04:40] <pitti> the very same; quickly switch to vt 2, flicker, and switch back
[04:40] <pitti> maybe it relies on ck-list-sessions listing a valid session?
[04:40] <pitti> (which it doesn't for VT)
[04:40] <pitti> I'm logged into VT1, the rest is just getty
[04:40] <iwj> It should let you switch to an inactive vt.
[04:40] <iwj> Can you /etc/init.d/consolekit stop and try then ?
[04:40] <iwj> I admit that I didn't try using the text VTs much during testing.
[04:41] <pitti> confirmed, that fixes it
[04:41] <iwj> OK.  Definitely a bug then.
[04:41] <pitti> I start it again -> still works
[04:42] <iwj> wtf
[04:42] <iwj> Oh, I know.
[04:42] <iwj> I bet I can reproduce this but my testbed is doing something else right now.
[04:42] <iwj> I should fix this for the next tribe at least though.
[04:43] <StevenK> 
[04:43] <StevenK> Oops
[04:43] <pitti> hm, now 'switch user' didn't give me the lock dialog, but immediately a new gdm
[04:43] <iwj> That's what it's supposed to do.
[04:43] <pitti> oh, gdmflexiserver -l is interesting
[04:44] <pitti> iwj: it shows me a list of four 'nobody' sessions on :20 to :24 (terminals 10 to 14)
[04:44] <pitti> it didn't do that in the past
[04:44] <lamont> pitti: just oh by the way, abiword and nabi are two main packages that currently (and apparently for a while) build-depend universe packages...
[04:44] <pitti> iwj: indeed, those are now full of gdms. funny
[04:45] <pitti> lamont: erk
[04:45] <StevenK> lamont, pitti: Happy to look at the two of them in the morning, if you wish.
[04:45] <pitti> lamont:  link-grammar?
[04:45] <pitti> and libhangul
[04:46] <lamont> pitti: I only mention it because I noticed them looping in hppa's efforts to get ready to get back into the archive (tries, fails, dep-waits, dep-wait gets cleared because wb doesn't know about universe not being avail to main, repeat)
[04:46] <lamont> pitti: yeah thouse./
[04:46] <pitti> lamont: they are on anastacia output; I'll get them fixed soon, thanks
[04:46] <pitti> I just wish anastacia wouldn't be so cluttered with mobile stuff...
[04:46] <seb128> pitti: https://wiki.ubuntu.com/MainInclusionReportFastUserSwitchApplet ;)
[04:46] <iwj> pitti: Did you do any manual vt switching before it went wrong ?
[04:47] <pitti> iwj: yeah, I stopped and restarted gdm from vt1 after the dist-upgrade
[04:47] <pitti> iwj: maybe it's best to just reboot this bloody thing and test again
[04:47] <StevenK> pitti: I can take one of them if you want to look at the other. My machine is busily rebuilding ghc6, so a test-build could take a little longer than usual.
[04:47] <pitti> StevenK: test build?
[04:47] <pitti> StevenK: it's just reviewing/promoting them, possibly involving a MIR
[04:48] <StevenK> I shall leave it alone then. :-)
[04:48] <iwj> pitti: Well, these things ought to work.  I don't understand why ck is fighting with other programs over vt switches.
[04:49] <pitti> seb128: rarian is in main, too, btw; so if you are confident in it for tribe 4, please seed it as well
[04:49] <iwj> I suppose it needs to fight with exiting X servers.
[04:49] <pitti> hm, I have CK running for a few days already, so that wasn't installed just today
[04:50] <seb128> pitti: yeah, it's on my list, trying to fix some issues still
[04:50] <pitti> seb128: if we don't do it for T4, that's perfectly fine for me; I'd just like to know what to watch out for
[04:51] <iwj> pitti: There's a new thing in latest ck and gdm which might cause what you're seeing.  Ie, a new thing I did.
[04:51] <iwj> I only did the briefest of tests with the gdm I merged yesterday; perhaps there's some conflicting logic.
[04:52] <jwendell> Hi, seb128
[04:53] <jwendell> seb128, the fast switch user you said in your blog is that one: http://ignore-your.tv/fusa/ ?
[04:54] <seb128> jwendell: no, read the comments on my blog entry, there is a link to the fedora wiki
[04:54] <seb128> hi jwendell
[04:54] <jwendell> :)
[04:56] <pitti> seb128, Riddell, Hobbsee: WDYT is worth mentioning on the Tribe 4 wiki page from the Gnome/KDE front?
[04:57] <Hobbsee> pitti: seb128 answered some of that earlier.
[04:57] <Hobbsee> pitti: the stuff in http://blogs.gnome.org/seb128/2007/08/02/ubuntu-desktop-updates/
[04:57] <Hobbsee> pitti: kde 4.0 beta 1
[04:58] <seb128> pitti: GNOME 2.19.6, fast user switching and consolekit, gnome-keyring pam integration, rarian, tracker
[04:59] <seb128> pitti: do you still have to review the fast-user-switch-applet today so I can commit consolekit and that? ;)
[04:59] <pitti> seb128: yeah, I will
[04:59] <seb128> thanks
[05:00] <pitti> seb128: currently doing the bits of MilestoneProcess, then I'll turn to that
[05:00] <pitti> seb128: tracker still needs those b-dep fixes, btw, before I cannot promote it
[05:00] <seb128> pitti: I did upload that like an hour ago
[05:00] <pitti> seb128: you are too fast for me!
[05:01] <pitti> seb128: (for changelogs.u.c. anyway)
[05:01] <seb128> well, the list of new things is not short and I would like to get most of it landing before next tribe ;)
[05:01] <Hobbsee> aug 16 or something
[05:02] <seb128> so tribe5?
[05:02] <Hobbsee> sounds about right, from memory
[05:02] <seb128> k
[05:02] <seb128> I was not sure if that was the coming tribe or the next one
[05:02] <seb128> anyway would be better to land things now so they get testing
[05:02] <lamont> beyond "you're screwed" that is
[05:02] <seb128> lamont: "update your glib2.0 to a fixed version"
[05:03] <seb128> that's what it mean :p
[05:03] <lamont> oh, rock
[05:03] <lamont> iz glib bug.  got it
[05:03] <seb128> yeah
[05:03] <seb128> I've fixed it like 1 week ago
[05:03] <seb128> what version do you use?
[05:04] <lamont> hrm... I hope glib2.0 builds this time, instead of timing out in the tests
[05:04] <pitti> seb128: tracker will be in desktop seed?
[05:04] <lamont> libglib2.0-0_2.13.7-1ubuntu2_hppa.deb is what I currently have in the archive....
[05:05] <pitti> seb128: gnome-keyring pam integration> ah, it won't ask you for the keyring password by default any more?
[05:05] <seb128> pitti: if your keyring password is the same as your login one, no
[05:05] <pitti> cool
[05:05] <seb128> lamont: 2.13.7-1ubuntu3 is the fixed version
[05:06] <lamont> and 1ubuntu4 is current
[05:06] <seb128> pitti: tracker, I think so
[05:06] <seb128> lamont: right
[05:06] <seb128> pitti: I'm not 100% happy with it but we need to give it some testing, might roll back if that's not good enough
[05:07] <pitti> seb128: right
[05:15] <asac> calc: can you please try if my crazy nm.dev branch cures you?
[05:15] <asac> calc: https://code.launchpad.net/~asac/network-manager/ubuntu.0.6.x.dev
[05:15] <calc> asac: ok i'll take a look at it
[05:15] <asac> calc: its an all-in branch ... just branch and build ... no need for an orig et al
[05:16] <calc> asac: ok
[05:27] <iwj> pitti: I can reproduce your can't-select-text-vt thing.
[05:27] <pitti> iwj: good! it does seem to be a race somewhere
[05:28] <iwj> ck is fighting you is the problem.
[05:28] <iwj> It thinks you're an exiting X server.
[05:29] <pitti> heh
[05:30] <doko> calc: new glibc-2.6.1~pre packages in the archive; please update and make sure that you reinstall, overwriting my packages from puc.
[05:30] <calc> doko: ok
[05:32] <pitti> ogra: just gently poking you about the two tribe-4 bugs in ltsp? we already moved them two times
[05:36] <pitti> BenC: there are currently 5 tribe-4 kernel bugs (one is fix committed); for the sake of planning and NEWing, do you mean to have another upload today, or shall we move them over to Tribe 5?
[05:38] <pitti> cjwatson: that gfxboot vs. syslinux bug (118744) -- is that something you still plan for T4?
[05:42] <BenC> pitti: let me check them..the main one I want to for tribe-4 is this AMD mobile timer problem
[05:42] <pitti> mathiaz: I take the liberty and sponsor bug 129920
[05:42] <ubotu> Launchpad bug 129920 in apache2 "/var/lock/apache2 has wrong owner and group for webdav" [Low,In progress]  https://launchpad.net/bugs/129920
[05:43] <pitti> BenC: oh, dynticks on amd64? yay
[05:44] <BenC> pitti: No, lost timer interrupts on Turion when running 32-bit kernel
[05:44] <asac> calc: any news?
[05:47] <calc> asac: not yet i was in the middle of working on an OOo build
[05:47] <calc> asac: i am going to try to build it now
[05:49] <Riddell> iwj: if ubuntu is having consolekit installed by default, will that be required by HAL as I believe it is in fedora?
[05:50] <pitti> Riddell: no, it's not required at all ATM
[05:50] <Riddell> ok, so I don't need to worry about making KDM talk to consolekit
[05:50] <doko> calc: if aot-compile still fails, please give me the failing jar file
[05:50] <pitti> Riddell: our hal has CK disabled ATM
[05:50] <calc> doko: ok
[05:50] <pitti> Riddell: I might look what that actually does (I think I have an idea), and turn it on if it is compatible with CK not being installed
[05:51] <iwj> Riddell: You should test that ck doesn't fight with kdm.
[05:51] <iwj> But only after the upload I'm going to make shortly :-).
[05:52] <pitti> iwj: oh, you fixed it already? awesome
[05:52] <Riddell> pitti: it doesn't seem to be, judging by fedora's experience
[05:52] <iwj> I'm testing my fix but I'm pretty sure it will work.
[05:53] <Riddell> iwj: what does the fix do?
[05:54] <fdoving> seb128: as you're the glib/gtk guy, can you figure out something usefull from https://bugzilla.novell.com/show_bug.cgi?id=294385 ? - that's making konqueror with nspluginviewer (flash) and openoffice.org among others, unusable on gutsy.
[05:54] <ubotu> Novell bug 294385 in KDE "nspluginviewer block konqueror and takes 100% CPU" [Critical,Assigned] 
[05:55] <iwj> Riddell: Makes it not fight with X's VT switch except once after a session ends.
[05:56] <seb128> fdoving: looking, calc said that openoffice is working correctly with 2.3 and he wants to do the update soon
[05:57] <fdoving> seb128: i care more about nspluginviewer, but it also kills acroread for example.
[05:57] <iwj> pitti: consolekit_0.2.1-1ubuntu2 should fix it for you, just uploaded.
[05:58] <pitti> yay
[05:58] <seb128> fdoving: acroread http://www.adobeforums.com/cgi-bin/webx/.3bc4895e
[05:58] <cjwatson> pitti: yeah, I'm going to sit down on Monday and see if I can squash that once and for all
[05:58] <pitti> cjwatson: good, then I'll leave it to T4 for now, thanks
[05:58] <seb128> fdoving: I'm not convinced that's a GTK bug
[05:59] <mathiaz> pitti: thks for the sponsor.
[05:59] <seb128> fdoving: openoffice and acroread seem to be bugs from those applications and there is no indication that's not the same for nspluginviewer
[06:00] <fdoving> seb128: well, it works if i build gtk with glib 2.13.5.
[06:00] <seb128> fdoving: that doesn't mean they are not doing something wrong which used to work because GTK+ was permissive on it
[06:01] <fdoving> seb128: true..
[06:01] <pitti> tepsipakki, bryce: erk, current live CD fails to start X with "SubSection is not a valid keyword in this section" (in section "Display"); WTF?
[06:05] <calc> asac: about to reboot and try out the new nm branch on i386 gutsy
[06:07] <asac> calc: ok ... already build?
[06:08] <pitti> bryce: ok, I tracked it down, see bug 130206
[06:08] <ubotu> Launchpad bug 130206 in xorg "X.org fails to start: "SubSection is not a valid keyword in this section"" [Critical,Triaged]  https://launchpad.net/bugs/130206
[06:09] <Q-FUNK> a LinuxBIOS developer is asking me who he should talk to at Debian/Ubuntu, to ensure that the GRUB menu.lst generated by kernel packages will be compatible with options needed by FILO.
[06:09] <Q-FUNK> who should I send him to?
[06:13] <cjwatson> Q-FUNK: the kernel packages don't generate that directly; update-grub does it - so probably best send him to ubuntu-installer@lists.ubuntu.com
[06:16] <Q-FUNK> cjwatson: noted.  thanks!
[06:16] <calc> asac: doing that now
[06:29] <pitti> bryce: wow, this is the first time EVER that the live CD correctly detected my screen resolution (through DVI cable; it has always worked through VGA); presumably this is because xorg.conf does not have any "Modes" any more by default; is that by design?
[06:32] <pitti> bryce: hm, this could actually be related to above bug, since the bit of dexconf that writes this looks quite broken
[06:40] <calc> asac: gutsy has diverged to much from tribe3 to be able to install the compiled debs :\
[06:41] <asac> calc: well thanks ...
[06:42] <asac> anyone else with ipw3945  here?
[06:42] <pitti> bryce: I think I got down to the bottom of that bug now
[06:43] <calc> asac: i could try it once i have time to upgrade my laptop to gutsy again, but that will be at least several days from now, since i need to try to get OOo 2.3 done asap
[06:43] <asac> sure ... np
[06:43] <asac> :)
[06:43] <calc> i will hopefully have OOo 2.3 done by the end of the weekend, since OOo 2.2 is broken
[06:44] <asac> calc: how large is the patchset we carry for ooo =
[06:44] <asac> ?
[06:44] <calc> and tribe4 is due next week .oO oh crap  ;)
[06:44] <pitti> calc: so you intend to get this into tribe4?
[06:44] <calc> asac: vs debian or overall?
[06:44] <pitti> calc: typo: s/.oO/OOo/ :-P
[06:44] <calc> pitti: yes, OOo 2.2 is broken at the source level apparently
[06:44] <asac> calc: he? ... i mean the patches you have against pristine upstream sources
[06:44] <calc> pitti: and i haven't looked into how to fix it for 2.2 since i expected to have 2.3 done soon
[06:45] <pitti> yeah
[06:45] <calc> asac: well ooo-build + debian dir is around 90MB i think (uncompressed)
[06:45] <pitti> calc: broken in which way? I just tested current ubuntu i386 desktop CD, and it started at least
[06:45] <calc> pitti: oh the claims i had seen were that it would not start at all
[06:46] <calc> pitti: due to break in glib abi compatibility of something that wasn't guaranteed to be stable
[06:46] <calc> if OOo 2.2 starts on current cd images then i have a bit of breathing room
[06:46] <pitti> calc: from what I have heard, it does work if you have ooo-gnome installed
[06:47] <calc> pitti: ok
[06:47] <pitti> and spectacularly fails if not (e. g. when installing on ubuntu)
[06:47] <pitti> erm, kubuntu
[06:47] <calc> ok :\
[06:47] <pitti> calc: so if all else fails, I think the current packages would at least not block the T4 release
[06:47] <pitti> seb128: wow, upstream bugs for f-u-s-a look scary
[06:51] <doko> calc: may I have a look at the source before you upload?
[06:54] <calc> doko: i had to disable java for a different reason now its broken in another way, grr :(
[06:54] <calc> after about 5min into the compile it dies
[06:55] <pitti> seb128: fusa approved and promoted
[06:56] <Kmos> # Add here commands to compile the package.
[06:56] <Kmos> CFLAGS+='-fPIC' /usr/bin/make FOUND_PERL5=0 FOUND_RUBY=0 FOUND_PYTHON=0 FOUND_SWIG=0 FOUND_SPL=0
[06:56] <Kmos> /bin/sh: CFLAGS+=-fPIC: not found
[06:56] <Kmos> make: *** [build-stamp]  Error 127
[06:56] <Kmos> someone knows what's that error about ?
[06:57] <stdin> is that in a scrpt or makefile?
[06:57] <Kmos> stdin: from debian/rules
[06:57] <Kmos> http://launchpadlibrarian.net/7567284/buildlog_ubuntu-gutsy-i386.stfl_0.8-2_FAILEDTOBUILD.txt.gz
[06:57] <Kmos> and the newest version on debian gives the same error
[06:58] <Kmos> on my pbuilder for gutsy
[06:58] <stdin> hmm
[06:58] <stdin> because /bin/sh shouldn't be sourcing that, should be make
[07:01] <Seveas> stdin, i think it does and then executes sh -c 'CFLAGS+='-fPIC' /usr/bin/make FOUND_PERL5=0 FOUND_RUBY=0 FOUND_PYTHON=0 FOUND_SWIG=0 FOUND_SPL=0'
[07:01] <Seveas> which looks weird to me (the +=)
[07:02] <stdin> yeah, += will work with make, but not in sh
[07:02] <stdin> hmm, shouldn't there be a space after CFLAGS too ?
[07:03] <Kmos> stdin: on debian it uses
[07:03] <Kmos> the /usr/bin/make
[07:03] <stdin> and after +0
[07:03] <stdin> *+=
[07:03] <Kmos> http://buildd.debian.org/fetch.cgi?pkg=stfl;ver=0.15-1;arch=hppa;stamp=1185653888
[07:04] <stdin> yeah, shouldn't there be a space after CFLAGS tho?
[07:05] <Kmos> CFLAGS +='-fPIC' $(MAKE) $(MAKE_FOUND_INTERPR)
[07:05] <Kmos> like this ?
[07:05] <stdin> yeah, that looks better to me
[07:06] <Kmos> i'll try
[07:06] <Kmos> if it builds
[07:07] <Kmos> at debian it doesn't have that space
[07:07] <Kmos> and it builds
[07:07] <Kmos> strange
[07:08] <lamont> doko: ping
[07:08] <stdin> debian/rules is really a makefie, and I recall that there are spaces after the variable name and the oporator
[07:09] <infinity> Who told you that?
[07:09] <infinity> makefiles MAY have whitespace surrounding the operator, they don't HAVE to.
[07:09] <Kmos> it doesn't build
[07:09] <Kmos> dh_testdir
[07:09] <Kmos> CFLAGS +='-fPIC' /usr/bin/make FOUND_PERL5=0 FOUND_SWIG=1 FOUND_SPL=1 FOUND_RUBY=0 FOUND_PYTHON=0
[07:10] <Kmos> make: CFLAGS: Command not found
[07:10] <Kmos> make: *** [build-stamp]  Error 127
[07:10] <Kmos> pbuilder: Failed autobuilding of package
[07:10] <lamont> uh.. .that's shell generating that error, not make
[07:10] <lamont> well, that's make trying to run the binary CFLAGS
[07:10] <infinity> Yeah.  DDTT.
[07:10] <infinity> Put your variable assignment on a line of its own.
[07:11] <infinity> Non-indented.
[07:11] <Kmos> this is at build-stamp:
[07:11] <Kmos> infinity: i'll try
[07:12] <pitti> evand: were you ever able to get to the bottom of bug 122645?
[07:12] <ubotu> Launchpad bug 122645 in ubiquity "manual partitioning hangs indefinitely" [Medium,Confirmed]  https://launchpad.net/bugs/122645
[07:12] <lamont> seb128: glib2.0 tests seem to be running for a very long time...
[07:12] <lamont>  /build/buildd/glib2.0-2.13.7/gobject/gobject.c:1776: warning: dereferencing type-punned pointer will break strict-aliasing rules
[07:13] <Kmos> infinity: it gives error
[07:13] <lamont> I wonder if that's bad
[07:13] <Kmos> ebian/rules:22: *** commands commence before first target.  Stop.
[07:13] <evand> pitti: yes, I have a patch, but I'm not sure why it works: http://people.ubuntu.com/~evand/tmp/18_stderr.patch
[07:13] <Kmos> debian/rules:22: *** commands commence before first target.  Stop.
[07:14] <pitti> kwwii: did you notice that the usplash progress bar recently got much too big and not centered any more?
[07:15] <infinity> Kmos: http://cerberus.0c3.net/~adconrad/argh.diff
[07:15] <lamont> strace -p 4803
[07:15] <lamont> Process 4803 attached - interrupt to quit
[07:15] <lamont> futex(0x40a6088c, FUTEX_WAIT, 2, NULL
[07:16] <pitti> evand: curious; did you show this to mvo already?
[07:16] <lamont> something tells me it's gonna stay there for a while, too
[07:16] <Kmos> infinity: nice, thanks
[07:16] <evand> pitti: negative.  mvo, care to take a look?
[07:18] <mvo> evand: the above patch? let me have a look. is it to fix the hang in gksu that seems to appear sometimes?
[07:20] <mvo> evand: you remove the "-	gksu_context_launch_complete (context);" line, why is this?
[07:20] <evand> mvo: yeah, stderr gets mangled
[07:20] <mvo> evand: do you have a bugnumber for this?
[07:21] <Kmos> infinity: it works, but there is more problem like that one in next steps of rules :)
[07:21] <evand> mvo: it was a regression from 2.0.3, so to be honest I just diffed and stripped what I thought wasn't necessary.
[07:21] <su-hoens> does dmraid work for sata?
[07:22] <evand> mvo: bug 122645
[07:22] <ubotu> Launchpad bug 122645 in ubiquity "manual partitioning hangs indefinitely" [Medium,Confirmed]  https://launchpad.net/bugs/122645
[07:22] <mvo> evand: thanks, the launch_complete bit is something I would like to keep in, is there a testcase too?
[07:22] <Kmos> $(MAKE) -C ruby$* clean && CFLAGS+='-fPIC' $(MAKE) -C ruby$* LIBS+="../libstfl.a -lncursesw" CFLAGS+="-I.."
[07:22] <Kmos> CFLAGS again =)
[07:23] <evand> specifically https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/122645/comments/6
[07:23] <ubotu> Launchpad bug 122645 in ubiquity "manual partitioning hangs indefinitely" [Medium,Confirmed] 
[07:23] <evand> mvo: it's hard to reproduce, it only seems to happen for some people, but basically:
[07:23] <infinity> Kmos: Just remove that, since it's already set above.
[07:24] <Kmos> infinity: yep, that's what i've done
[07:26] <evand> mvo: take a live cd, comment out the try block on line 184 in /usr/lib/ubiquity/bin/ubiquity and run the installer.  Select manual partitioning, make some changes and hit next.  If the bug is reproduceable on your system it will hang.
[07:26] <evand> there's probably a simpler test case
[07:26] <zyga> mvo: hi
[07:26] <mvo> hey zyga, long time not seen, how are you?
[07:27] <zyga> mvo: yeah! I've been quite busy -- and still am unfortunatly
[07:27] <zyga> I'm in Tokyo right now
[07:28] <zyga> (I was in Poland before that)
[07:28] <mvo> zyga: cool, that is quite a change
[07:28] <zyga> I have no time to maintain c-n-f now
[07:29] <zyga> maybe once I return home in october
[07:29] <Seveas> I just found a nice c-n-f bug
[07:29] <Seveas> dennis@mirage:~$ --moo
[07:29] <Seveas> Usage: command-not-found [options]  <command-name>
[07:29] <Seveas> command-not-found: error: no such option: --moo
[07:29] <Seveas> bash: --moo: command not found
[07:29] <zyga> Seveas: fixed
[07:29] <zyga> Seveas: just not released
[07:29] <Seveas> ah
[07:30] <Seveas> no need to file then, was about to
[07:30] <zyga> I didn't have the time to work on that in ages
[07:30] <zyga> the patch basically adds '--'
[07:30] <zyga> mvo: how about you? I see you are keeping busy as usual :-)
[07:30] <Kmos> infinity: now it builds fine :)
[07:30] <zyga> what time is it in EU right now?
[07:30] <mjg59> Which bit of the EU?
[07:31] <zyga> median ;] 
[07:31] <mjg59> Somewhere between 17:31 and 20:31
[07:31] <IntuitiveNipple> It's harvest-time!
[07:32] <Kmos> 18:32
[07:32] <Kmos> at Portugal =)
[07:32] <zyga> one thing I hate about being here is the timezone
[07:32] <zyga> the other is that tokyo is pretty much linux free :/
[07:33] <Seveas> zyga, use ubotu as worldclock
[07:33] <Seveas> @now Amsterdam
[07:33] <ubotu> Current time in Europe/Amsterdam: August 03 2007, 19:33:13 - Next meeting: Kernel Team in 3 days
[07:33] <zyga> :-)
[07:33] <zyga> @now Tokyo
[07:33] <ubotu> Current time in Asia/Tokyo: August 04 2007, 02:33:30 - Next meeting: Kernel Team in 3 days
[07:33] <mvo> zyga: unfortunately yes :)
[07:33] <zyga> time to sleep soon
[07:33] <agoliveira> @now Joainville
[07:33] <agoliveira> Bah :)
[07:34] <mvo> zyga: its fine, thanks for keeping me updated, I will see that I maintain it and get it ready for gutsy
[07:36] <zyga> mvo: I can help you get the most of what I have unfinished
[07:36] <zyga> there is alot of interesting stuff that I started soon after feisty got released
[07:38] <zyga> if you don't have the time to pick everything up then I'd recommend to get the UI fixes and improvements and leave the new build system untill someone finishes the process
[07:38] <Kmos> infinity: patch sent to debian maintainer :)
[07:49] <mvo> zyga: ok, thanks
[07:55] <Kopfgeldjaeger> does the ipw4965 support monitor mode with the ubuntu drivers?
[07:55] <Kopfgeldjaeger> (gutsy)
[08:08] <dendrobates> jdstrand: did you see we got approved.
[08:08] <jdstrand> dendrobates: yeah-- I thought the timing was funny
[08:09] <dendrobates> jdstrand: in what way
[08:10] <jdstrand> dendrobates: just that I thought you were still thinking about all the details (particularly remove/purge)
[08:10] <jdstrand> dendrobates: but obviously that can still be worked out
[08:10] <dendrobates> jdstrand: we can creep the scope a bit. It was implrtant to get it approved so we can be sure and get into gutsy.
[08:11] <jdstrand> dendrobates: this is great news.  big steps towards easier network authentication.  users will be pleased
[08:11] <jdstrand> dendrobates: you were generous to say 'we' too.  :)
[08:13] <dendrobates> jdstrand: how well do you think the ini semantics work for the templates?   I know it is an RFC standard.
[08:14] <jdstrand> dendrobates: you mean for auth-client-config?  I think it works fine, particularly since it is standard python config parsing.
[08:14] <jdstrand> dendrobates: I should probably add a manpage for it though, now that you mention it
[08:15] <dendrobates> for auth-client-config.  I like the python module, but wonder if in the long run xml doesn't make sense.
[08:15] <dendrobates> Maybe both.
[08:16] <jdstrand> dendrobates: I understand the attraction for xml.  I think the simplicity of the code with ConfigParser as well as getting ordering lines (ie for pam) for free is nice too.
[08:17] <jdstrand> dendrobates: I am open to other ideas though
[08:18] <jdstrand> dendrobates: right now I am focusing on writing the tests, as well as verifying the state machine.  I also added an '-a' option, so you can specify just the profile instead of having to specify each type individually.
[08:19] <dendrobates> jdstrand: I like ConfigParser as well.  It will do a good job for now, but we might want to keep a more complex solution in the back of our minds.  Just in case.
[08:19] <jdstrand> dendrobates: will do
[08:19] <dendrobates> jdstrand:  are you in Rochester NY?
[08:19] <jdstrand> dendrobates: yep
[08:20] <psusi> iwj: ping
[08:20] <dendrobates> jdstrand: I've got lots of family there.  I go there every couple years.  Not the same since kodak had so many layoffs, though.
[08:21] <iwj> psusi: Yes ?
[08:21] <jdstrand> dendrobates: cool (not about kodak).  I am not from here, but been here 8 years now.
[08:22] <psusi> iwj: wanted to discuss the relattionship between udev and lvm/dmraid with someone familiar with it... would that be you and do you have time?
[08:22] <dendrobates> jdstrand: i have to get writing the the MIR's to get this auth stuff into main.  I'm a bit behind.
[08:23] <iwj> I'm somewhat out of date but I may be able to help.
[08:23] <jdstrand> dendrobates: I will keep plugging away at 0.3.  Did you want to talk about the ldap-client-config more now, or do you want to think about what we said earlier for a bit?
[08:24] <dendrobates> I want to think about it.  We should bring others into the conversation as well.
[08:24] <psusi> iwj: ok.... I think that right now, lvm operates by running pvscan, which essentially does an ls /dev/hd? and checks any found devices for lvm signatures, and when found, adds them to a list somewhere in /etc right?
[08:24] <iwj> More or less.
[08:24] <psusi> then later another utility looks at the devices in that conf file and tries to activate the list
[08:25] <psusi> essentially then, lvm has no working relationship with udev at this time
[08:26] <psusi> except that udev re-runs lvscan etc al on new device add events to rescan all devices in the system and add any new ones to its database and try to activate them
[08:26] <psusi> right?
[08:26] <iwj> More or less, yes.
[08:26] <psusi> that's pretty crappy and we want it to work better with udev don't we?
[08:28] <iwj> Err, well it's not wholly ideal but what specifically do you think is wrong ?
[08:30] <psusi> well, several problems... one is that lvm on dmraid is broken because lvm wants to use the underlying physical disks instead of the dmraid device
[08:30] <psusi> I would think the same problem would happen with mdraid
[08:30] <iwj> This is just a general problem with autodetection.
[08:31] <iwj> lvm knows about md metadata and avoids those partitions.
[08:31] <iwj> Does dmraid put the metadata at the end then ?
[08:31] <psusi> ahh, but not about dmraid?  k
[08:31] <psusi> yea
[08:31] <iwj> IDIOTS
[08:31] <iwj> That CAN'T BE MADE TO WORK PROPERLY
[08:31] <psusi> sure it can
[08:31] <iwj> No, not reliably.
[08:31] <psusi> why not?
[08:32] <iwj> If you've got a disk that looks like this       lvm metadata | something | raid metadata
[08:32] <iwj> how can you tell whether it's raid-in-lvm or lvm-in-raid ?
[08:32] <psusi> hrm...
[08:32] <iwj> What if in fact it was    lvm metadata | filesyste
[08:32] <iwj> where filesystem happens to contain a user file containing something that looks like raid metadata.
[08:33] <psusi> well, in the case of dmraid, it will ALWAYS be lvm on dmraid
[08:33] <psusi> can't go the other way
[08:33] <iwj> ... unless it's just a user file with some interesting data.
[08:33] <iwj> Still as a workaround, teach lvm not to touch things with dmraid metadata.
[08:33] <psusi> wouldn't be in the right location on disk, and the activation attempt would fail
[08:33] <iwj> Then you're just left with the hideous security vulnerability and not an actual complete inability to boot.
[08:34] <iwj> It might well be in the right location on disk.
[08:34] <psusi> the right location is like the last cylinder of the disk, outside of any partitions
[08:34] <iwj> If I'm a resourceful user I can probably fill the cause the bit of the disk where dmraid looks to look like a dmraid.
[08:34] <iwj> If dmraid is outside any partitions then what's the problem ?
[08:34] <iwj> LVM is inside partitions.
[08:35] <psusi> the problem is that lvm is directly accessing the physical disk because it sees its header there
[08:35] <psusi> instead of going though the raid device
[08:35] <iwj> The problem is that the kernel is showing these partitions.
[08:35] <psusi> yes, that is
[08:35] <iwj> This isn't just a problem for lvm.  What if you have dmraid with a filesystem ?
[08:36] <psusi> what do you mean?
[08:36] <iwj> That is     partition table | filesystem | dmraid metadata
[08:36] <psusi> the metadata is at the very end of the disk
[08:36] <iwj> now the auto fs finder thingum will spot your fs and mount it by uuid.
[08:36] <psusi> so it's outside the filesystem
[08:37] <psusi> right... what needs to happen is for dmraid to "claim" the disk
[08:37] <iwj> You have hda1 which containing 1234...., hdc1 containing 1234...., and dmraidsomething1 containing 1234... as well.
[08:37] <psusi> so other components don't try to detect things in it
[08:37] <iwj> Yes.  So nothing to do with lvm.  If you can stop partitions showing up then you're sorted.
[08:37] <psusi> true....
[08:38] <psusi> well, partly
[08:38] <psusi> the second part of the problem is getting lvm to look for pvs in the dmraid device
[08:38] <psusi> right now it only looks for them on /dev/hd? and not on other device-mapper devices, right?
[08:39] <iwj> That part is probably easy.  You may need to add some dev patterns to the relevant udev rules.
[08:39] <iwj> No, it looks for them on various other things too.
[08:39] <psusi> well the udev rules just run pvscan... pvscan doesn't scan /dev/mapper/*
[08:39] <psusi> does it?
[08:39] <iwj> /etc/udev/rules.d/65-persistent-storage.rules is the relevant file.
[08:40] <iwj> OIC
[08:40] <iwj> You want pvscan to look at dmraid stuff.
[08:40] <psusi> yea, you can run pvscan, but it won't do anything
[08:40] <iwj> Yes, you'll have to patch lvm for that.
[08:40] <psusi> right
[08:40] <psusi> ok... now... I kind of don't like how lvm is not udev friendly
[08:40] <psusi> I don't like seeing utilities detect hardware by stat()ing well known names
[08:41] <psusi> so it seems to me that pvscan should be looking for disks to scan in the udevdb, where you can use attributes to easily control things like "claiming" devices so it doesn't look there
[08:41] <iwj> Hah.
[08:42] <iwj> What you really want is just an interface provided by lvm2 which can be called by udev, where udev can say `here is new block device which is one of your pvs'.
[08:42] <psusi> plus when the state of the vg changes, i.e. if a pv goes offline, udev pushes that state change out to monitoring applications which can lead to things like desktop popups warning the user of a failed disk and degraded raid operation
[08:42] <iwj> And never to pvscan.
[08:42] <psusi> more like here is a new block device, scan it and see if it looks like a pv
[08:42] <psusi> if it does, let me know and I will record that in my db
[08:43] <iwj> udev already calls vol_id.
[08:43] <iwj> To decide what kind of thing it is.
[08:43] <psusi> then the other tools can consult the udevdb to see what pvs are there instead of its proprietary conf files
[08:43] <psusi> yea... but lvm does nothing with that information
[08:43] <iwj> Having that there is good because it's much faster than passing the device to every possible thing which might understand it.
[08:44] <psusi> that's fine.... but my point is that once it is decided that the thing is an lvm pv, that fact should just be added to the device's udevdb attributes
[08:44] <psusi> rather than recorded in an lvm conf file
[08:44] <iwj> The whole thing with lvm's conf files in /etc is just hideously ebw.
[08:45] <psusi> ebw = evil?
[08:45] <iwj> Evil, Bad, and Wrong.
[08:45] <psusi> yea
[08:45] <psusi> that info should be in udevdb I think
[08:45] <mweichert> I want to start ubuntu dev. What do you guys use for a python ide?
[08:45] <psusi> I don't do python, but I use emacs for everything ;)
[08:46] <psusi> iwj: so what do you think about moving it out of the /etc files to udevdb?
[08:47] <iwj> I think lvm shouldn't depend on udev.
[08:47] <psusi> why not?
[08:48] <psusi> and where do you think the evil /etc stuff should be moved to if not udevdb?
[08:50] <mweichert> does anyone use pydev/eclipse for their python development?
[08:51] <iwj> udev is not an essential part of the system and shouldn't be made into one.
[08:51] <iwj> Plenty of people are using lvm without udev and they will all come and murder you personally if you try to force them to have udev :-).
[08:53] <mweichert> does anyone know how to get gtk "intellisense" working in eclipse? When I use "import gtk" I get the error "unresolved import: gtk" ?
[08:53] <mweichert> I'm going insane here trying to figure it out!
[08:53] <psusi> well I guess they could fall back to using the ebil conf files then ;)
[08:59] <psusi> iwj: so where do you think the data should be moved instead of the ebil conf files?
[09:02] <iwj> It would be fine if it had some kind of cache in /var/run.
[09:10] <psusi> ahh, true
[09:11] <psusi> but I'd rather have it in udev because it makes the information so much easier to share and access
[09:12] <psusi> and build rules with
[09:16] <psusi> I wonder if we can disable the partition detection in the kernel and let udev take care of that, and when it finds a dmraid disk, skip the partition check
[10:15] <mvo> Riddell: I uploaded a new apt + rdepends, adept should be fine, but please keep a eye open in case of problems
[10:15] <Riddell> mvo: ok, will do
[10:24] <doko> seb128: does gtk support parallel builds?
[10:25] <Riddell> mvo: do you know where the beryl kcontrol module has disappeared to in the merge?
[10:26] <seb128> doko: what do you mean by parallel?
[10:26] <mvo> Riddell: no, I guess it was never ported to compiz-fusion
[10:27] <doko> seb128: DEB_BUILD_OPTIONS=parallel=... but it seems so
[10:27] <doko> trying DEB_BUILD_OPTIONS=parallel=32
[10:43] <desertc> Hello - I am taking a look at the Ekiga package, and I see that there was a security fix released (2.0.5) in February.  I wonder whether Feisty should not be updated from current version (2.0.3)
[10:44] <desertc> Information identifying the release information can be seen on http://www.ekiga.org (second page of news, Ekiga 2.0.5 Released)
[10:45] <seb128> desertc: new versions are not uploaded to stable, we backport patches rather
[10:46] <seb128> not sure about what security issue you are speaking about
[10:46] <mjg59> desertc: The security fix was backported to 2.0.3
[10:46] <seb128>  ekiga (2.0.3-0ubuntu6) feisty; urgency=low
[10:46] <seb128>  .
[10:46] <seb128>    * SECURITY UPDATE: remote code execution via format string overflows.
[10:47] <desertc> I understand that the security fix was backported to 2.0.3 -- thank you for your time
[10:47] <seb128> you're welcome
[11:01] <ynezz> any idea how to tell the 7.04 installer to perform "modprobe ide-generic" during boot? otherwise the installer can't find cdrom (new notebook)
[11:03] <mjg59> Press alt-f2, hit enter, type "modprobe ide-generic"
[11:04] <mjg59> Though this implies some sort of ridiculous failure on our part to begin with
[11:04] <ynezz> i can't do alt-f2
[11:04] <mjg59> ?
[11:05] <ynezz> (initramfs) cat /casper.log
[11:05] <ynezz> Unable to find a medium containing a live filesystem
[11:06] <ynezz> I'm inside busybox
[11:06] <mjg59> Oh.
[11:06] <mjg59> In that case, I have no idea
[11:07] <ynezz> i think, that there is no such option to specify additional module to load during boo
[11:11] <ynezz> seems to be related to this http://bugzilla.kernel.org/show_bug.cgi?id=8835
[11:11] <ubotu> bugzilla.kernel.org bug 8835 in Serial ATA "IDE CD/DVD RW drive ignored at boot with sata hd" [Normal,Closed: patch_already_available] 
[11:11] <ynezz> thanks for looking into it
[11:11] <ynezz> just wonder what to do now
[11:12] <ynezz> patch a kernel and cook own install cd?
[11:17] <wasabi> Hmm. apt-cdrom uses a "cdrom id". What is this?
[11:52] <mikmor1> wasabi: I believe the id you are referring to is in the '.disk' directory in the base of the ISO
[11:53] <wasabi> ahh.
[11:53] <wasabi> And that's only required for apt cds?
[11:54] <mikmor1> wasabi: Not sure.. however, I don't know of anything else that uses it.
[11:55] <mikmor1> ynezz: If you want an external module to be loaded during boot, you have to use a driver disk. It doesn't work in Feisty Desktop, but it is fixed for Gutsy
[12:06] <ynezz> mikmor1: ah ok, thanks
[12:07] <mikmor1> ynezz: np.