[08:14] <dholbach> good morning
[08:31] <ApOgEE> morning dholbach
[08:31] <dholbach> hi ApOgEE
[08:32] <ApOgEE> dholbach: how can i start my journey to become motu?
[08:33] <dholbach> https://wiki.ubuntu.com/MOTU/GettingStarted should be a good start
[08:33] <dholbach> it links to all the guides we have and also links to stuff you can do afterwards
[08:37] <ApOgEE> which ubuntu are you using currently on your desktop to do all this development? is it the latest one?
[08:38] <dholbach> yes
[08:39] <dholbach> but if you have a look at https://wiki.ubuntu.com/UsingDevelopmentReleases
[08:39] <dholbach> (which is also linked from https://wiki.ubuntu.com/MOTU/GettingStarted) you'll find out how to install it in a safe way
[08:39] <ApOgEE> i've read that documentation and learning on how can i help in fixing bugs. but i'm not clearly understand the flow yet
[08:45] <dholbach> best to start with a simple one and ask your questions here
[08:46] <ApOgEE> can you show an example of a simple bug that i can start with?
[08:49] <dholbach> there's a bunch of links that can help you find something at https://wiki.ubuntu.com/MOTU/TODO/Bugs (also http://harvest.ubuntu.com/opportunities/)
[08:57] <ApOgEE> thank you
[13:34] <evaluate> Hello.
[13:36] <evaluate> The package clipit from ubuntu natty has 2 bugs open which I would consider RC bugs. These can be easily fixed by synching the package from Debian (and not applying any patches to it, to force it to build with indicator support). I have sent an email to Andrew Starr like a week ago, since he seems to be the one that is taking care of the package, but I didn't receive any response yet. Could anyone please try and contact him about that or look
[13:36] <evaluate>  into synching the package?
[14:29] <lfaraone> Do we still subscribe ~ubuntu-sru to SRU bugs?
[14:30] <lfaraone> I just uploaded a fix for Lucid for bug 698122, and left it as "in progress". Should it be back to new, or "fix committed"?
[14:43] <tumbleweed> lfaraone: I tend to mark them committed when I've uploaded, and yes I subscribe SRU (not sure if that's necessary but it doesn't hurt)
[19:02] <micahg> YokoZar: why is wine1.3-gecko a native package?
[19:03] <YokoZar> micahg: because it doesn't actually build on Ubuntu
[19:03] <micahg> YokoZar: I don't think that makes a difference
[19:03] <YokoZar> micahg: (older gecko version, still requires a build step on windows).  Note that we've fixed this in Wine for gecko 1.2, but that's not the version needed by the wine1.3 in Natty
[19:03] <micahg> YokoZar: should be the same as anything else in multiverse
[19:05] <YokoZar> micahg: regardless it will comfort you to know that wine1.3-gecko 1.2.0 is in fact a nonnative package and does build in all the ways you would expect it to
[19:05] <YokoZar> and, indeed, can be in universe rather than multiverse
[19:05] <YokoZar> but that's for O
[19:06] <micahg> YokoZar: yes, but native has nothing to do with building but rather where the contents origin is (is this an upstream package or one w/out an upstream)
[19:06]  * micahg wonders if that changed with source format 3...
[19:08] <petani> all can i ask for php
[20:00] <RoAkSoAx> '/win 4
[20:04] <adam__> somebody here ?
[20:07] <micahg> !ask | adam__
[20:07] <adam__> ok !!
[20:09] <adam__> Once I've built a package how is it release on the official repositories ?
[20:09] <adam__> how to sign my package !! i don't have the official private key !! ?
[20:11] <adam__> :(
[20:13] <adam__> is this chan active ?
[20:14] <Pici> adam__: Have you read the Ubuntu packaging guide yet?
[20:15] <adam__> hum yes but not completely :( ok ... I'll read it completely
[20:15] <adam__> Pici, answers are inside .. isn't it ?
[20:15] <Pici> https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[20:16] <adam__> ok ok :( but it is getting like a big boring encyclopedia
[20:17] <adam__> thanks anyway
[20:18] <adam__> bye