[01:20] <pwnguin> heh, yet another gentoo fork
[01:21] <pwnguin> I love this one: things we find problematic with gentoo: "portage, management, developers, qa, users, and the lack of designers"
[01:21] <jdong> pwnguin: lol isn't that the whole distribution
[01:21] <jdong> pwnguin: head over to Ulteo too to learn about their innovative "application balls"
[01:21] <jdong> pwnguin: in my sleep deprived state I've found that extremely amusing.
[01:21] <pwnguin> it gets better
[01:22] <pwnguin> http://kloeri.livejournal.com/5016.html
[01:22] <pwnguin> they're ready to tackle the problems of gentoo, and also write yet another initsystem
[01:23] <pwnguin> " * We're writing a completely new initsystem free of all the weird, useless legacy stuff and based on user needs in the 21st century."
[01:23] <RAOF> work is ongoing on this topic [multilib] and there'll probably be huge changes but we have a fairly decent idea how to handle all the multi stuff sanely.
[01:24] <RAOF> Heh.
[01:24] <selckin>  not hurting anyone, let em try
[01:24] <selckin> can't deny gentoo is a mess
[01:24] <pwnguin> apparently sysvinit, initng, runinit, launchd, upstart, eINIT, SMF and so on wasn't up to task
[01:25] <pwnguin> selckin: gentoo might be a mess, but I'm not sure they're going to actually clean anything up
[06:36] <emgent> heya
[07:35] <Q-FUNK> mornin'!
[07:35]  * Q-FUNK just arrived in Prague
[07:53] <pitti> Good morning
[08:34] <soren> pochu: Hey.
[08:35] <soren> pochu: Just to let you know, I'm doing  the gtk-vnc update now.
[08:40] <pochu> soren: the sru?
[08:40] <pochu> soren: thanks :)
[08:42] <pitti> cjwatson: YokoZar proposed https://blueprints.edge.launchpad.net/ubuntu/+spec/killing-ia32-libs, which is quite toolchainish (multiarch); is there time/interest to discuss it this week?
[08:44] <Amaranth> that spec is pretty empty
[08:45] <soren> pochu: Yeah, sorry for the delay. Feel free to ping me more often I suck like this again :)
[08:53] <YokoZar> Amaranth: I'll fill it out a bit, but the main issue is discussing how to kill ia32-libs since it needs to die and there are many ways we might kill it
[08:55] <persia> YokoZar: Is there anything planned other than death-by-1000-cuts, as we modify each library otherwise included in ia32-libs?
[08:55] <Riddell> tkamppeter: when and where are the printing sessions today?
[08:55] <YokoZar> persia: Well making a bunch of packages a la lib32asound2 is one option, but pitti seemed to have other ideas about doing it more elegantly within the toolchain.  We've been waiting on multiarch for years, however.
[08:56] <ScottK-uds> And AFAIK no one is actually working on multiarch.
[09:29] <tkamppeter> Riddell, biff
[09:31] <Riddell> tkamppeter: are the printing sessons scheduled yet?
[09:31] <Riddell> not 11 to 13 for me, otherwise fine
[09:34] <tkamppeter> Riddell, on the dialog we will then schedule an extra session. There we do not get everyone together at once, I go to one after the other and talk with hm ...
[09:35] <tkamppeter> The dialog session is also very early, we cannot get Alexander Wauck to call in.
[09:35] <tkamppeter> Keybuk, ping
[09:35] <Riddell> oh, if I press F5 they're on the schedule
[09:35] <Riddell> right, I can't do that 12:00 one
[09:36] <Riddell> keybuk is busy running this desktop session
[09:37] <tkamppeter> Riddell, I will ask Keybuk for another session today or tomorrow in the afternoon to get at least him and Alex together with me.
[09:38] <tkamppeter> Im mixing up everything, let me retry
[09:38] <tkamppeter> Riddell, I will ask Keybuk for another session today or tomorrow in the afternoon to get at least you and Alex together with me.
[09:38] <Riddell> right
[09:39] <alkisg> Hello everyone. I'd like to add some features to ldm (LTSP Display Manager), like user-sign-up feature for new students, a remote desktop button etc, but I don't want to "just fork". What is the proper way to do something like that?
[09:40] <Riddell> alkisg: talk to ogra when he's online
[09:40] <\sh> alkisg, talking to ogra
[09:40] <tkamppeter> Riddell, are you in a session currently?
[09:40] <Riddell> tkamppeter: yes
[09:41] <alkisg> Thank you, I'll try to find him!
[09:41] <tkamppeter> Riddell, have you 1pm today you have time to meet me informally, in the lobby, to talk about the dialog?
[09:42] <tkamppeter> Or perhaps at lunch?
[09:42] <Riddell> tkamppeter: yes, lunch is fine
[09:46] <tkamppeter> Riddell, so come here to the Lobby of the third floor at 1pm and then we go to lunch together.
[09:47] <pwnguin> if travis is is NotAmaranth, then that must mean...
[09:47] <pwnguin> It's opposite day!
[09:53] <Riddell> pwnguin: no it's not
[09:56] <emgent> persia: i saw mail, Thanks :)
[10:04] <pochu> soren: thanks! hope it doesnt break your virt* stuff :)
[10:08] <soren> pochu: Me too :)
[10:12] <emgent> tseliot: where are you now?
[10:12] <tseliot> emgent: volga
[10:12] <tseliot> kubuntu-kde4
[10:13] <emgent> argh, is not for me :)
[10:53] <saispo> hello, anyone known this error when you build a package ? (parsechangelog/debian: avertissement:     debian/changelog(l5743): fin de fichier trouvée, first heading attendu)
[10:54] <james_w> saispo: you're debian/changelog probably has a syntax error
[10:54] <wgrant> s/probably //
[10:55] <james_w> if you pastebin it then we can help you fix it up.
[10:56] <ln-> james_w: "you're" -> "your"
[10:56] <saispo> james_w: grab the changelog from http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=blob;f=debian/changelog;h=3fb3f2de98cf665bf147b4511a727eb4af6ab2a2;hb=HEAD :)
[10:56] <saispo> it's this changelog :p
[10:58] <james_w> I can't see anything immediately.
[10:58] <wgrant> Particularly not on line 5743.
[10:59] <saispo> it's the end of the file :/
[10:59] <saispo> after i do a debchange -i
[10:59] <wgrant> Ah, so it's not that changelog.
[11:00] <saispo> it's the same with a debchange -i, just that
[11:00] <wgrant> Can you please translate that error?
[11:01] <saispo> yes, with my english words
[11:02] <saispo> parsechangelog/debian: warning: debian/changelog(l5743): end of file found, first heading waited)
[11:05] <wgrant> Huh.
[11:08] <saispo> wgrant: no idea ?
[11:08] <wgrant> saispo: Does it work OK if you use that changelog without `dch -i`ing?
[11:09] <saispo> don't try at this time, but i can, must waiting a long time for the build process :)
[11:11] <saispo> wgrant: it's working...
[11:11] <saispo> debchange -i don't work ??
[11:12] <wgrant> saispo: It might have become confused at the format of that latest entry.
[11:12] <wgrant> Check the diff between the old and new ones.
[11:12] <saispo> ok
[11:13] <saispo> thanks wgrant
[11:16] <saispo> wgrant: i found why, thanks
[11:43] <Keybuk> Keybuk's Wishlist #1 : ~/.local/share/hal/fdi
[12:31] <sdh> cjwatson: ping?
[12:31] <sdh> cjwatson: I mailed Matthew Veron, he tells me you're now openssh maintainer... so, incoming :)
[14:40] <hiho-man> http://xrl.us/bkj9x
[15:45] <tmmoyer> is there any place which describes how versions of packages are compared to determine if one package version is greater than the other?  or at least explains the different possible combinations of version that could appear on package?  The way I understand it, there are potentially 4 different numbers the upstream version, the debian build number, the ubuntu build number and a possible NMU version number (am I missing any?)
[15:47] <tmmoyer> is there any place that describes the structure/rules of version numbers in ubuntu? the way I am currently understanding things, there are potentially 4 numbers the upstream, the debian, the ubuntu, and a non-maintainer upload version number is this correct?
[15:48] <geser> tmmoyer: the debian policy manual describes the format of the version string and you can compare versions with "dpkg --compare-versions"
[15:48] <broonie> tmmoyer: The Debian policy document (debian-policy package) describes the comparison function;
[15:50] <geser> looks like it wasn't that important that he couldn't wait some minutes for an answer
[15:57] <fabbione> BenC: silo pull request? :)
[16:08] <dee> Hello Ubuntu-Devs.
[16:09] <dee> Could someone tell me why Ubuntu Live is cancelled in June? Does anybody has some background information? Or are you just as clueless as I am? :(
[16:12] <MacSlow> dee no clue
[16:21] <N00B> hi
[16:26] <dee> thx MacSlow. Maybe someone else knows more
[20:59] <mok0> soren: ping
[23:00] <wildcode> how do I find a maintainer of a particular package
[23:01] <wildcode> specifically, who maintains the wildmidi package in ubuntu
[23:02] <wildcode> I'm the author of WildMIDI and would like to see any patches ubuntu made to the original source
[23:03] <beuno> wildcode, http://patches.ubuntu.com/ is a good place to look
[23:03] <wildcode> thankyou
[23:05] <wildcode> hmm, no patch ... does that mean no changes?
[23:05] <beuno> wildcode, yeap
[23:07] <wildcode> k, so who do I find out wh the maintainer is, so I can see if there is anything I can do to make their life easier ... apart from stop breaking the cvs source :)
[23:08] <beuno> wildcode, https://launchpad.net/ubuntu/+source/wildmidi
[23:09] <beuno> Uploaded By:  Emilio Pozuelo Monfort
[23:09] <beuno> Maintainer:  Emmet Hikory
[23:10] <beuno> wildcode, https://launchpad.net/ubuntu/+source/wildmidi/+publishinghistory
[23:10] <wildcode> I appologize if I am being annoying, its judt I was supprised to see wildmidi in a distro specially since it was made out of curiosity
[23:10] <beuno> wildcode, not a problem
[23:10] <beuno> open source works that way  :)
[23:11] <wildcode> :)
[23:11] <Adri2000> wildcode: the package comes from debian and is not modified in ubuntu, so you should talk to the debian maintainer, Emmet Hikory, who is also an ubuntu developer by the way
[23:13] <wildcode> hehe, no problem
[23:16] <ScottK-uds> wildcode: His IRC handle is persia.  He is most often found on #ubuntu-motu, altough he's not there now.
[23:16] <ScottK-uds> Urgh.  To slow.
[23:19] <ispiked> when one presses volume keys on their keyboard, Ubuntu adjusts the volume... what code handles this? I've gotten as far as figuring out that it uses the X11 "XF86Audio*" commands, but I don't know what program/daemon handles those commands