[00:02] heya === tkamppeter_ is now known as tkamppeter [00:23] slangasek: okey doke, any chance you have a couple of minutes to review/sponsor my grub-raid patch? [00:23] kirkland: I think so :) [00:23] slangasek: okay, i've pushed, waiting for Launchpad to scan my branch.... [00:25] kirkland: OOI, do you think it would be better to drop the other patch from the tree, rather than applying && reverting? [00:25] slangasek: actually, that was another thing i wanted to talk to you about [00:26] slangasek: in the first revision, i do the minimal amount to solve this bug [00:26] slangasek: after you were happy with that, i was going to commit another revision that reduces that crappy 30-line function down to my 4-line equiv [00:26] * slangasek nods :) [00:26] i don't actually use that function for anything [00:27] slangasek: but it's kinda ugly, and the comments above the .diff in the patches directory draws its providence into question [00:28] slangasek: i'm still getting used to bzr-based package source management, and I wasn't sure if it was better to remove a patch that's in the debian sources, or to add an ubuntu patch that undoes it [00:28] I would argue that it's better to remove the patch from the debian sources [00:28] then the "remove" is visible as part of the repo history, and doesn't have to be encoded in the current source package [00:29] slangasek: okay, sounds good [00:29] slangasek: my code will be here: https://code.launchpad.net/~kirkland/grub/33649b [00:29] (I would also argue for per-feature branches instead of a debian/patches directory, but I'm a ways away from ramping up on this idea myself on any packages :) [00:29] slangasek: as soon as Launchpad does its magic [00:29] ah; I somewhat expected the new revision to be on the same branch, ok, I'll go grabbing that other one :) [00:30] slangasek: i suppose i could have done that.... [00:30] * kirkland needs a big fat bzr-best-practices brain dump from a bzr expert [00:31] * slangasek holds up his hands and backs away from the 'expert' label [00:31] although, 'bzr expert' would be a cool subcommand [00:33] slangasek: okay, it's there, in case you hadn't noticed [00:35] yep, reviewing :) [00:37] kirkland: I know as much as bzr co and bzr ci work like svn. [00:38] ScottK: :-) i'm doing pretty well with it... but sometimes people ask me questions like "why did you create a new branch to do that?" [00:38] heh [00:38] ScottK: and I just kinda stare at them blankly thinking.... hmm, why did it? i guess because I always just create a new branch [00:39] "because it was more than a single commit" [00:39] :-) [00:39] really, it's just to artificially elevate my karma [00:43] slangasek: i've got to head out to a rehearsal dinner [00:43] slangasek: the deletion of the raid.diff revision on my end will wait until tomorrow [00:44] kirkland: ok; unless I say otherwise in scrollback, you can expect this bit to be merged in the meantime, please just update the same branch if you refactor it [00:44] (and then I can merge when I'm on the ground in Argentina on Sunday) [00:44] slangasek: you bet, thanks a ton [00:44] slangasek: enjoy DebConf [00:44] kirkland: oh, before you go - I see you're assuming that the raid device is always going to be the first BIOS drive? [00:45] slangasek: the hd0, bit? [00:45] yes [00:45] slangasek: can you think of a smarter way to do that? [00:45] slangasek: kees seemed to be okay with it, so i just left it as is [00:45] not immediately :-) [00:46] slangasek: perhaps worthy of an inline comment, i suppose [00:46] is this going to regress anything that worked before? [00:46] slangasek: if you want to do that as you commit/push, that would be great [00:47] slangasek: it won't regress any non-raid systems [00:48] kirkland: will it regress any RAID systems? :-) [00:48] slangasek: for systems with /boot on RAID, the MBR writing will be handled slightly differently === cjwatson_ is now known as cjwatson [00:49] it seems to me that it will, that previously we at least looked at device.map [00:49] slangasek: the only additional thing we could do is perhaps pull the bios device out of device.map if it exists in the RAID case, and assume hd0 if it doesn't [00:49] yes, I think that would be the right thing to do [00:49] slangasek: okay, i can make another another revision, but not at the moment [00:49] understood [00:50] slangasek: generating the debian/patches/*diff crap is time consuming and error prone [00:50] yep [00:50] slangasek: okay... i'll fix that and drop you a note [00:50] * kirkland was hoping to put this baby to bed tonight ;-) [00:50] tomorrow then [00:50] merged&pushed the current rev [00:50] slangasek: okay, later. [00:50] thanks :) [00:50] slangasek: oh, good [00:51] adios === superm1|away is now known as superm1 [02:00] http://digg.com/linux_unix/An_Open_Letter_to_Ubuntu === ember_ is now known as ember [04:15] Is there some trick to adding mimetypes to Ubuntu? [04:18] File a bug against shared-mime-info, i think. Not 100% sure, though. [04:19] cjwatson: Yeah I can do so first thing Monday. === LucidFox_zzzzz is now known as LucidFox === superm1 is now known as superm1|away === superm1|away is now known as superm1 [09:03] heh http://people.redhat.com/esandeen/ext4/e4fsck-1T.png [09:32] is the timevault trunk still in active development? === LucidFox is now known as LucidFox_away [11:40] moin [12:58] Will Intrepid be getting PulseAudio 0.9.11 :) [13:09] YokoZar: You might file an upgrade bug, rather than hoping for a scrollback response: it's at least as likely to get an answer, and you get notified rather than having to watch carefully :) [13:09] (that is, if you want the upgrade: if you don't, I don't have any useful suggestions) [13:09] persia: good call :) === LucidFox_away is now known as LucidFox === Kopfgeldjaeger is now known as Kopfgeldjaeger|\ === Kopfgeldjaeger|\ is now known as Kopfi|\o === Kopfi|\o is now known as Kopfi|\m === Kopfi|\m is now known as Kopfi|o === Kopfi|o is now known as Kopfgeldjaeger === fta_ is now known as fta === asac_ is now known as asac === krusaf|bnc is now known as krusaf === DrKranz is now known as DktrKranz [18:10] hello === tkamppeter_ is now known as tkamppeter [19:36] anyone have experience with Empathy? [19:37] me :) [19:39] First of all, a technical question: How do I install backends for protocols? I can't find a menu that will do that, and it won't let me add accounts of any kind unless I have these backends instaleld. [19:39] *installed [19:39] and the help menu isn't working. I'm on Hardy. [19:40] lukehasnoname, do you use the package from the ppa? === max538 is now known as max === max is now known as Guest89408 === Guest89408 is now known as max === jscinoz_ is now known as jscinoz [22:35] <_gAri-> hi there, can you please help me out where can I find the ubuntu specific kernel patch in peaces that is applied to the vanilla kernel? I mean I only want to use parts of it, not totally [22:43] _gAri-: I can't help you with the specifics, but I know that git stores diffs between revisions that you can use to pull specific patches. ive never done it myself though [22:49] _gAri-: #ubuntu-kernel --- http://kernel.ubuntu.com [22:51] hi all