[12:02] IGNORING YOUR OWN DEADLINES, EH?! :) [12:03] yes, low priority [12:03] :-) === jmg goes back to replying to all the recruiters that emailed him this morning [12:03] Keybuk: besides, the point of the deadline was to give us a chance to look over what we have without it changing all the time [12:03] hehe [12:03] I know [12:04] sabdfl: speaking of which, in case you're behind on mail, please don't accept any new stuff for paris for a bit; we're sorting through what we have [12:04] sabdfl: and Keybuk and I are borrowing #ubuntu-meeting to coordinate that effort === Amaranth [n=amaranth@ubuntu/member/amaranth] has joined #ubuntu-devel === LeeJunFan [n=junfan@adsl-69-210-207-5.dsl.klmzmi.ameritech.net] has joined #ubuntu-devel [12:07] BenC: see my last comment on bug 43531, would like to hear back while I'm working on the agenda for paris [12:07] Malone bug 43531 in linux-source-2.6.15 "Kernel isn't very useful without a boot loader, but doesn't depend on one" [Medium,Confirmed] http://launchpad.net/bugs/43531 [12:07] mdz: Ok [12:08] BenC: I think there's probably stuff to talk about since the installer is involved === Whoopie [n=Whoopie@p54A79595.dip0.t-ipconnect.de] has joined #ubuntu-devel [12:09] mdz: i'm not accepting anything for paris for fear of being accused of setting edgy goals ;-) [12:09] so far, so good [12:10] sabdfl: does blueprint automatically set things to accepted? [12:10] Keybuk: if you would have the right to accept it [12:10] so, if a member of ubuntu-drivers nominates a spec, it will be accepted [12:10] ah, so if anyone on ubuntu-drivers proposes a spec, it goes straight to accepted without collecting 200$ ? [12:11] btw, ubuntu-drivers should not include core dev, if it still does [12:11] the drivers really should be drivers [12:11] can i fix that now? [12:12] mdz: No sure if we need a talk, but if we make it low-priority, we can pick up discussion if there's time [12:12] mdz: Just added my comment to the bug [12:12] sabdfl: only if you fix "faster pussycat, kill kill kill" while you're there [12:12] mdz? [12:12] sabdfl: top of https://launchpad.net/people/ubuntu-drivers [12:13] wow [12:13] no idea where that came from === ubijtsa [n=ubijtsa@karlsson.force9.co.uk] has joined #ubuntu-devel [12:13] very non-CoC === ivoks [n=ivoks@ubuntu/member/ivoks] has joined #ubuntu-devel [12:13] sabdfl: h4x0rz [12:13] sabdfl: you're the only person who can edit that [12:13] did someone hack you with alcohol? [12:13] was this text added intentionally ? :p [12:14] hey hey simira [12:14] erggh, sivang* [12:14] weird [12:14] i can't see where to edit that text [12:14] it's probably the team's homepage [12:15] right - done [12:16] this page is seriously lacking a nice title/context [12:16] sabdfl: do we really need ubuntu-drivers at all? shouldn't that just be TB? [12:16] it's basically TB + people who were added because they were helping with the schedule at UBZ [12:16] mdz: useful to be able to add people here when its needed without affecting TB [12:17] i'll take the janes off the list [12:17] should the TB be the owner/administrator? [12:17] can do, too [12:17] that'd be slightly less cabalistic [12:18] done [12:18] sabdfl: my basic rule of thumb for accepting things for the paris agenda is that one of the attendees is interested [12:19] sabdfl: maybe for the next one we could have LP do that calculation for us? [12:20] mdz: could do... but we could also just show the people (or the number of people) associated with it that are also registered for the sprint, on the accept/decline page [12:20] I have a list of spec tracker ideas and needs resulting from working with it a bunch recently [12:20] so its still a manual process, just better informed [12:20] sabdfl: that's what I was suggesting [12:20] mdz: cool, suggestions welcome [12:20] that gives us a chance to scare up some interest about it [12:21] main thing on my todo is to move everything to blueprint.launchpad.net/ so you stay in a specs view while jumping from upstream to the distro and to people [12:21] though when it's proposed, LP should probably say "there's no one attending the sprint who's interested in it; it's unlikely to be accepted unless someone signs up to talk about it" [12:21] sabdfl: my stuff is so much more useful than that though ;-) [12:21] we should also ask people to note their attendance in LP rather than the wiki [12:22] mdz , sabdfl : maybe "My interest in this spec is [1.....x.10] " tick box for sub'ers ? [12:22] mdz: useful to... you? [12:22] ;-) [12:22] sort of a poll style.. [12:22] i primarily want to use blueprint to lead the other apps [12:22] sabdfl: correct [12:22] me being someone who uses the spec tracker a lot ;-) [12:23] Keybuk: why are you trying to join motu? [12:23] hehe === Fjodor [n=sune@0x55510b65.adsl.cybercity.dk] has joined #ubuntu-devel [12:23] mdz: s/motu/core-dev/ ... was just testing something and needed a team where it was a no-op to join [12:24] ie. one I was already a member of by inferance [12:24] I've been deactivated from Ubuntu Drivers! [12:24] Keybuk: why is mjg59 whining about the mailbombing when he was supposed to go to sleep? [12:24] BenC: we took the u-core-dev team out of drivers === fimbulvetr [n=danv@host-74-28-220-24.midco.net] has joined #ubuntu-devel [12:25] sabdfl: bug! I got a mail saying I was deactived from Ubuntu Drivers ... yet I'm still a member via a different team [12:25] it's ok, I'm on too many teams as it is :) [12:25] Keybuk: file it, assign to salgado [12:25] mdz: because the tech-board is marked as an approved for all the specs ... so his mail box is full of e-mail about every change we made :p [12:25] Keybuk: good catch ;-) [12:25] Keybuk: but he said he was going to sleep before we did that [12:25] Keybuk: why did you mark the tech-board an approver? [12:25] mdz: he woke up again [12:25] Keybuk: that was his excuse for ditching out on the discussion [12:25] I see [12:25] sabdfl: so we'd get e-mail about all the changes [12:26] mjg59: you're not coming to paris? [12:26] hmm... reduces the value of the approver slot, though [12:26] mdz: Correct [12:26] (And I'm supposed to be sleeping, damnit) [12:26] Keybuk: the scheduler will try to make sure the approver is in an early discussion session, to get things off on the right foot === mjg59 curses his sleep cycle [12:26] for edgy, since specs are sort of "self lead", folks will generally want to be their own approvers [12:27] sabdfl: right, the theory is to change that before the meeting when we assign real approvers [12:27] ok [12:27] jus' checkin' [12:27] night all. morning mjg59. [12:27] Keybuk: they all start as tech board and will get delegated from there as appropriate [12:27] mjg59: why aren't you coming? :( [12:28] but I appreciate getting mail about the changes [12:28] mjg59: yeah, shame on you [12:28] Keybuk: Work [12:28] 135 specs ?! [12:28] they're going up! [12:28] I didn't add one [12:29] not since the one I admitted to [12:29] drive-backports ? [12:29] uh, driver-backports [12:29] that's the one [12:30] hmm, then another one got added between me counting 133 and sabdfl counting 134 [12:30] aiiieee... it's too many, we'll need to do good prioritisation, try give everyone at least one essential, a couple of high, etc [12:30] stat: if each spec requires 3 sessions, and we have 6 sessions a day ... then we need 14 concurrent sessions to fit them all in [12:31] good specs require 6-9 sessions, from experience [12:31] edgy might be less, since it's self-inspired [12:31] the guy writing it up is the guy who dreamed it up, in more cases [12:31] so mostly, he gets to call for comments and feedback, and check interactions with other devs [12:31] but still [12:32] we could easily end up with lots of half-done or badly-done specs, if we try take on too much [12:32] it's a very tight cycle [12:32] mdz: do you want to ask guys to estimate dev time, for specs they are dreaming up? [12:33] sabdfl: I don't think we can reasonably expect that until the spec is fleshed out === didymo [n=ashley@CPE-61-9-197-223.nsw.bigpond.net.au] has joined #ubuntu-devel === jinty [n=jinty@242.Red-83-49-54.dynamicIP.rima-tde.net] has joined #ubuntu-devel [12:33] ah, #134 was ltsp-dhcpd-autogeneration [12:33] ok, night all, really === sabdfl [n=mark@ubuntu/member/pdpc.silver.sabdfl] has left #ubuntu-devel [] === zul [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-devel === chris38-home [n=Christia@mut38-4-82-233-119-151.fbx.proxad.net] has joined #ubuntu-devel [12:40] ah, good. === bluefoxicy takes screen shots of the dapper loading process, from install to boot. === shackan [n=shackan@host188-192.pool873.interbusiness.it] has joined #ubuntu-devel [12:47] bluefoxicy: osnews/osdir has them for you. === apokryphos [n=apokryph@host-87-74-109-20.bulldogdsl.com] has joined #ubuntu-devel === jinty [n=jinty@15.Red-83-50-220.dynamicIP.rima-tde.net] has joined #ubuntu-devel === Gman [n=gman@nwkea-socks-1.sun.com] has joined #ubuntu-devel [01:01] Keybuk: I'm actually erroring at trying to understand the meaning of the software appliance term, they were not using it a year a go IIRC [01:01] "our primary business plan failed, here's plan B" [01:02] hehe [01:02] anyway, I'm way past my bed time. laters all, night Keybuk [01:04] mako: ping [01:06] Keybuk: I'm just picking up major highlights on the install process. I'm planning on boot screen, live desktop, live desktop + firefox, install (with a GNU/FreeDOS partition resize), booting (skip G/FD in grub), and at the desktop. [01:07] bluefoxicy: hmm? [01:07] er. [01:07] I meant HiddenWolf [01:07] did you mean HiddenWolf ? :) [01:08] I mean the keys are practically the same [01:08] Key, Hid, you know. [01:08] bluefoxicy: ah, ok. === Arrogance [n=aks@ottawa-hs-209-217-110-17.d-ip.magma.ca] has joined #ubuntu-devel === j_ack [n=nico@p508D914D.dip0.t-ipconnect.de] has joined #ubuntu-devel [01:11] bluefoxicy: yes, I can see that === ozamosi [n=ozamosi@ubuntu/member/ozamosi] has joined #ubuntu-devel === shackan_ [n=shackan@host220-92.pool871.interbusiness.it] has joined #ubuntu-devel === Aegir [n=richard@C1500200.wl150.flinders.edu.au] has joined #ubuntu-devel === FunnyLookinHat [n=funnyloo@71.57.11.218] has joined #ubuntu-devel === elkbuntu [n=melissa@203-206-255-153.dyn.iinet.net.au] has joined #ubuntu-devel === licio [n=licio@ubuntu/member/licio] has joined #ubuntu-devel === Aegir_ [n=richard@C1500034.wl150.flinders.edu.au] has joined #ubuntu-devel === ozamosi [n=ozamosi@ubuntu/member/ozamosi] has joined #ubuntu-devel === robertj [n=robertj@66-188-77-153.dhcp.athn.ga.charter.com] has joined #ubuntu-devel === lakin [n=lakin@S01060013101832ce.cg.shawcable.net] has joined #ubuntu-devel === patwack_ [n=paddy@cpc3-blfs2-0-0-cust141.belf.cable.ntl.com] has joined #ubuntu-devel === bddebian [n=bdefrees@71.224.172.103] has joined #ubuntu-devel [02:09] Heya [02:09] anybody know what the default debconf interface is, Dialog? [02:09] and do individual package managers (like synaptic) override that? === bluefoxicy [n=bluefox@c-68-33-112-13.hsd1.md.comcast.net] has joined #ubuntu-devel [02:22] infinity: ping? === fimbulvetr [n=danv@host-74-28-220-24.midco.net] has joined #ubuntu-devel === Keybuk [n=scott@syndicate.netsplit.com] has joined #ubuntu-devel === FunnyLookinHat [n=funnyloo@71.57.11.218] has joined #ubuntu-devel === jinty [n=jinty@15.Red-83-50-220.dynamicIP.rima-tde.net] has left #ubuntu-devel ["Leaving"] [02:55] ajmitch: my approach for that is to do rm -rf *; tar xf ../new-tar.tar.gz --strip-components=1 [02:55] bzr add [02:55] (bzr notices the removed files automatically) [02:55] right [02:55] basically the same as "moving the .bzr" yes [02:56] it does work particularly well [02:56] so far most of mine just have debian/ in bzr [02:56] I did experiment awhile with keeping various branches, including upstream, around also [02:57] I've not really been enamoured about debian/ in bzr [02:57] it's handy for collaboration though I guess [02:58] I didn't really have useful tools for getting all the patch branches together, keeping everything in sync [02:58] it seemed like more work for less gain [02:58] I decided to drop debian/patches entirely [02:59] "emulating revision control" again [02:59] so I have a "release branch"/"integration branch" which I make releases from [02:59] Keybuk: how do you cope with rediffing your changes against a fresh upstream? [02:59] and I do feature work on separate branches (the old patches) [02:59] sladen: I have an excellent example right here [02:59] $ cd upstream [02:59] $ rm -rf * [02:59] $ tar xf ../udev-094.tar.gz --strip-components=1 [03:00] $ bzr add [03:00] $ bzr commit -m "import udev 094" [03:00] $ cd ../ubuntu [03:00] $ bzr merge ../upstream [03:00] (no conflicts this time) [03:00] $ bzr commit -m "update to udev 094" [03:00] $ uch -v094-0ubuntu1 [03:00] $ dpkg-buildpackage -rfakeroot -S [03:00] I see === ajmitch might as well try it out again [03:01] (the top lot is just one shell script I have, btw) [03:01] so I really just do [03:01] and presumely if launchpad is automatically pulling in upstream into bzr then the above means you can just merge from the launchpad copy [03:02] ubuntu$ new-upstream ../udev-094.tar.gz [03:02] sladen: exactly === sladen has forgotten what part of launchpad was doing this [03:02] sladen: harder when there's no tags [03:02] importd [03:02] ajmitch: just create branches where you would have created tags [03:02] main$ bzr push sftp://ajmitch@bazaar.launchpad.net/~ajmitch/foo/TAG [03:03] sure, I mean that launchpad doesn't have any tags or similar on the imported products [03:03] launchpad doesn't really _do_ imported products yet [03:03] it has the 0.1 branch of f-spot, for example [03:03] right [03:03] it's still alpha code [03:05] once all the relevant upstream products are imported, it will be quite useful [03:05] Keybuk: so once it's in that state, what's the easiest way of backing out individual patches that were applied several revisions back [03:08] sladen: well, what I do for patches is [03:08] (creating one) [03:08] $ cp upstream ubuntu.iftab [03:08] $ cd ubuntu.iftab [03:08] $ vi ... [03:08] $ bzr commit [03:08] $ cd ../ubuntu [03:08] $ bzr merge ../ubuntu.iftab [03:08] $ bzr commit -m "merge iftab patch" [03:09] was there a UTB meeting this morning? [03:09] so that's a patch _in_ [03:09] to update the patch is [03:09] $ cd ../ubuntu.iftab [03:09] $ bzr pull ../upstream [03:09] (or merge) [03:09] so the patch is actually based on upstream [03:09] to back out the patch is easy [03:09] hmm [03:10] $ bzr merge -r $(bzr revno ../ubuntu.iftab)..1 ../ubuntu.iftab [03:10] (ie merge it in reverse) [03:10] jmg: there was an extraordinary meeting of the Ubuntu Technical Board to discuss spec priorities -- the ordinary meeting was last week and will be again next week [03:11] Keybuk: ah ok, yes some of my specs were accepted [03:11] were some declined? [03:11] Keybuk: but there are no logs online yet [03:11] the log should in the usual ubuntu-meeting irclogs place [03:11] Keybuk: no [03:12] it's not very interesting reading [03:12] Keybuk: hasnt shown up yet === jmg wonders how he can word his ubuntu stuff for his CV [03:14] jmg: still doing the job hunt? :) [03:15] ajmitch: interview tomorrow, phone interview this afternoon [03:15] ajmitch: i've been relaxing :) [03:15] heh, good [03:15] potential job might still be using ubuntu? [03:16] debian [03:16] i'll convince them to switch to ubuntu-server :) [03:17] i think they would like to have an ubuntu contributor on board, even if he isnt a warthog === zul is the proccess of converting servers at work to ubuntu-server [03:17] yet :) [03:18] this meeting is confusing [03:19] which meeting? [03:21] Keybuk: so this means that you have to keep each of that branch directories around indefinately? [03:21] sladen: push them onto the supermirror and it can do that for you [03:22] ah ok, it was for paris [03:22] Keybuk: oh boy, that's alot of diskspace/bandwidth === zul [n=chuck@ubuntu/member/zul] has joined #ubuntu-devel [03:23] sladen: not so bad with repositories [03:23] sladen: not really, just one revision [03:23] Keybuk: this morning, my specs were approved without discussion [03:23] for some definition of "so bad" [03:23] sladen: another option is just to bzr log -v and grab the revision ids [03:23] Keybuk: what is Paris? is that the edgy planning event? [03:23] jmg: yes [03:24] hopefully i can attend via IRC :-) [03:24] Keybuk: then reverse-merge from the current directory? [03:24] right [03:24] I can grep "bzr log -v" for "branch nick: ubuntu.iftab" [03:24] Keybuk: eg. bzr merge -r x..x+1 . ? [03:24] and get the "merged: id" from it [03:25] that's a much better solution, as long as you don't want to keep modifying the patches [03:25] even if you modify the patches, you can just do it repeatedly for each one with that branch nick [03:26] all these neat little features that snuck into bzr when I wasn't watching [03:27] Keybuk: so if you're editing foo.patch you do mv ./packagename packagename.foo ; cd packagename.foo ... merge ; cd .. ; mv packagename{.foo,} [03:27] just to set the branch nick? [03:27] no, I'd cheat and do "bzr nick iftab" [03:28] this is starting to make more senes [03:28] (even if I'm not making senes) [03:29] admittedly, the "decide not to include a patch anymore" case is slightly harder with bzr [03:29] but I don't think that's a very common case [03:30] the common case is simply that the patch is merged upstream -- with bzr that's a no-op [03:30] very rarely is a patch abaonded [03:30] (I could be wrong) [03:30] it can happen when upstream won't take a patch and you decide it's just not worth carrying the delta [03:31] that would assume that the delta is expensive to maintain [03:31] so more likely to be the case in Universe [03:31] the theory of bzr says that deltas become cheap to maintain [03:31] yes [03:32] that could easily not be the case especially in rapidly changing projects, no? [03:32] true [03:32] a sync from Debian is the fast path; a scripted solution that attempted the import+merge would in theory be just as easy [03:33] it moment it fails to merge, you're back to a human though [03:34] that's always going to be the case [03:34] if two people change the same code in two different ways [03:34] only a human can resolve it [03:34] a revision control system at least gives you "A", "B" and "BASE" [03:34] rather than just A and B === imbrandon_ [n=brandon@ubuntu/member/imbrandon] has joined #ubuntu-devel === imbrandon_ [n=brandon@ubuntu/member/imbrandon] has joined #ubuntu-devel === stuNNed [n=lance@unaffiliated/stunned] has joined #ubuntu-devel === magicstorm [n=joel@200.213.44.20] has joined #ubuntu-devel === stuNNed [n=lance@unaffiliated/stunned] has joined #ubuntu-devel [04:27] ok so esd should be disabled by default and just rely on hw system beep and raw alsa support imho === fimbulvetr [n=danv@host-74-28-220-24.midco.net] has joined #ubuntu-devel === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-devel [04:42] threw crappy imitation flash at esd and it fried alsa [04:42] compiling gnash can't find X [04:42] or xlibs [04:43] one sec let me try the dev packages maybe [04:43] thn x [04:43] 18.4mb isn't too bad, crap [04:54] another 20mb of -dev packages to get gnash going :D === CarlFK [n=carl@c-67-163-39-124.hsd1.il.comcast.net] has joined #ubuntu-devel === imbrandon_ [n=brandon@CPE-72-135-8-5.kc.res.rr.com] has joined #ubuntu-devel === imbrandon_ [n=brandon@ubuntu/member/imbrandon] has joined #ubuntu-devel === imbrandon_ [n=brandon@ubuntu/member/imbrandon] has joined #ubuntu-devel [05:35] Ahh, it's nice when I wake up to an internet connection that doesn't suck... [05:35] Fetched 121MB in 2m0s (1005kB/s) === Hobbsee glares at the injustice of that. where are you, infinity? === freeflying|away [n=freeflyi@ubuntu/member/freeflying] has joined #ubuntu-devel === spine55 [n=erniee@c-69-180-53-201.hsd1.ga.comcast.net] has joined #ubuntu-devel === stub [n=stub@ppp-58.8.2.29.revip2.asianet.co.th] has joined #ubuntu-devel === Aegir [n=richard@C1500034.wl150.flinders.edu.au] has joined #ubuntu-devel === alchemist [n=alchemis@cpe-066-026-081-081.nc.res.rr.com] has joined #ubuntu-devel === alchemist [n=alchemis@cpe-066-026-081-081.nc.res.rr.com] has joined #ubuntu-devel === imbrandon_ [n=brandon@ubuntu/member/imbrandon] has joined #ubuntu-devel === Gloubiboulga [n=gauvain@ubuntu/member/gloubiboulga] has joined #ubuntu-devel === dholbach [n=daniel@i577B0091.versanet.de] has joined #ubuntu-devel [07:15] good morning === Amaranth [n=amaranth@ubuntu/member/amaranth] has joined #ubuntu-devel === dooglus [n=dooglus@82.67.28.79] has joined #ubuntu-devel === winkle [i=winkle@130.239.18.162] has joined #ubuntu-devel === Hadaka [i=naked@62.142.249.112] has joined #ubuntu-devel === Trewas [n=ilonen@157.24.184.131] has joined #ubuntu-devel === j^_ [n=j@e178053083.adsl.alicedsl.de] has joined #ubuntu-devel === maswan [i=maswan@kennedy.acc.umu.se] has joined #ubuntu-devel === CarlFK [n=carl@c-67-163-39-124.hsd1.il.comcast.net] has joined #ubuntu-devel === shenki [n=a1105806@pulteney-pix.border.net.adelaide.edu.au] has joined #ubuntu-devel === imbrandon_ [n=brandon@ubuntu/member/imbrandon] has joined #ubuntu-devel === dsas [n=dean@host86-129-9-151.range86-129.btcentralplus.com] has joined #ubuntu-devel === hendry [n=hendry@222.106.128.78] has joined #ubuntu-devel === alchemist [n=alchemis@cpe-066-026-081-081.nc.res.rr.com] has joined #ubuntu-devel === herzi [n=herzi@c180177.adsl.hansenet.de] has joined #ubuntu-devel === robitaille [n=daniel@ubuntu/member/robitaille] has joined #ubuntu-devel === alchemist [n=alchemis@cpe-066-026-081-081.nc.res.rr.com] has joined #ubuntu-devel === patwack__ [n=paddy@cpc3-blfs2-0-0-cust141.belf.cable.ntl.com] has joined #ubuntu-devel === alchemist [n=alchemis@cpe-066-026-081-081.nc.res.rr.com] has joined #ubuntu-devel === alchemist [n=alchemis@cpe-066-026-081-081.nc.res.rr.com] has joined #ubuntu-devel [08:12] fabbione: about the netboot failing here yesterday.. it still does, and the reason is that the installer is trying "http://localmirror/ubuntu dapper-security" which is quite impossible to create [08:13] tepsipakki: dapper-security is also on the normal mirrors [08:13] i have it on my localmirror as well [08:13] it is? ok.. will try [08:13] so probably you are victim of a wrong mirror pulse [08:13] there have been mirroring issues yesterday [08:13] well, it isn't mirrored here, yet :/ [08:13] i don't know if they have been fixed [08:14] it is here [08:14] but I think it should use s.u.c if a local mirror doesn't exitst [08:14] exist [08:14] but hold on === hendry_ [n=hendry@222.106.128.198] has joined #ubuntu-devel === pitti [n=pitti@ubuntu/member/pitti] has joined #ubuntu-devel [08:17] tepsipakki: i am not going anywhere for the next 10 minutes at least [08:18] Good morning [08:18] hey pitti [08:18] 195189630 bytes will be downloaded into archive. [08:18] hi pitti [08:18] fabbione: I'll report in a minute if that was it :) === robitaille [n=daniel@ubuntu/member/robitaille] has joined #ubuntu-devel === moberg_ [n=peter@c83-248-85-194.bredband.comhem.se] has joined #ubuntu-devel [08:23] bah, forgot to mirror main/debian-installer [08:24] hmm no, I'm lost now.. it didn't mirror the udeb, and I don't know what repo to use for that [08:25] oh wait.. === Etheri [n=Etheri@c220-237-37-48.brasd1.vic.optusnet.com.au] has joined #ubuntu-devel === Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-devel [08:28] trial-and-error, that's me [08:28] fabbione: it works now === Etheri [n=Etheri@c220-237-37-48.brasd1.vic.optusnet.com.au] has left #ubuntu-devel [] === Etheri [n=Etheri@c220-237-37-48.brasd1.vic.optusnet.com.au] has joined #ubuntu-devel === carlos [n=carlos@13.Red-88-15-198.dynamicIP.rima-tde.net] has joined #ubuntu-devel === olemke [n=olemke@iup.physik.uni-bremen.de] has joined #ubuntu-devel === R0cK3T [n=xp@S0106000fb0fcaa63.tb.shawcable.net] has joined #ubuntu-devel === viviersf [n=cain@196.44.1.98] has joined #ubuntu-devel === shenki [n=a1105806@pulteney-pix.border.net.adelaide.edu.au] has left #ubuntu-devel ["Leaving"] === ivoks [n=ivoks@ubuntu/member/ivoks] has joined #ubuntu-devel [08:53] hi ivoks [08:53] hi pitti [08:54] pitti: that patch for sharing printer should be droped :) [08:54] ivoks: which one? [08:54] since it doesn't share printer, but printers... and cups can share single printer [08:54] pitti: the one that didn't get into dapper [08:54] ivoks: oh, the g-cups-mgr UI one [08:54] yes [08:55] ivoks: for edgy we need a completely new UI infrastructure anyway (eggcups?), so we need a new patch [08:55] ivoks: so we should extend enable_sharing to specify a printer name, too? [08:55] right, but we should look how to implement "share this printer" [08:55] yes [08:55] ivoks: it would still open the port, and then set an ACL on the partiuclar printer [08:55] cups 1.2 supports that [08:55] right [08:56] it just needs additional instructions... === mvo [n=egon@p54A64E1D.dip.t-dialin.net] has joined #ubuntu-devel === tepsipakki [n=tjaalton@replicant.hut.fi] has joined #ubuntu-devel === Etheri [n=Etheri@c220-237-37-48.brasd1.vic.optusnet.com.au] has joined #ubuntu-devel === rpedro [n=rpedro@87-196-35-227.net.novis.pt] has joined #ubuntu-devel [09:05] pitti: looks like fedora has some development around eggcups [09:06] ivoks: yes, I think they wrote it in the first place [09:06] oh... [09:06] ivoks: however, last update was Februrary 2004 [09:07] not exactly up to date either [09:07] um... [09:07] not quite [09:07] http://rpmfind.net/linux/RPM/fedora/devel/ppc/desktop-printing-0.19-6.ppc.html [09:08] it's quite newer [09:08] actully, it's never than dapper :) [09:08] that url doesn't quite seem to work [09:08] ok, almost :) [09:08] pitti: ok, check this out ftp://download.fedora.redhat.com/pub/fedora/linux/core/development/source/SRPMS/desktop-printing-0.19-9.src.rpm [09:08] ivoks: however, eggcups is just a gnome-cups-icon replacement [09:09] ivoks: this one is a g-cups-mgr equivalent? [09:09] pitti: i see only eggcups in that archive [09:09] but version 0.19 [09:10] yup... last release in 2005. [09:10] jdub: ping === chmj [n=chmj@196.44.1.98] has joined #ubuntu-devel === seb128 [n=seb128@ubuntu/member/seb128] has joined #ubuntu-devel [09:13] pitti: yes, this is only icon, they use system-config-printer for printer managment [09:13] ivoks: what's that? [09:13] hey seb128! [09:13] hello pitti [09:14] pitti: redhat's tool [09:14] pitti: py program [09:14] there's really no current gnome-native printer management tool? [09:14] i searched and searched... but... === Harti [n=Harti@unaffiliated/harti] has joined #ubuntu-devel [09:15] didn't find anything _recent_ [09:15] gnome-cups-manager? [09:15] :D [09:15] seb128: recent :) [09:15] ivoks: it's recent [09:15] seb128: something that sucks less [09:16] or do you want to start a new software from scratch every months to get something "recent"? [09:16] seb128: no, but something that provides better hotplug support and dbus integration :) [09:16] seb128: and g-c-m is dead upstream [09:17] I think some Novell guys worked on thaty [09:17] CVS has probably some new feature over current tarball [09:17] oh, cool === pitti looks [09:17] seb128; how was the vacation? [09:18] seb128: it seems we should at least use eggcups instead of g-c-icon to get rid of the polling and 100% cpu usage problems, right? [09:19] desrt: really good ;) [09:19] pitti: yeah, I think so [09:19] desrt: nice to do something totally different and to enjoy the nice weather for a week ;) [09:20] seb128: at least we finally have nice weather here, too :) [09:20] now I've to catch up with mails and that's not going to be a lot of fun :p [09:20] seb128; lots of launchpad backlog, i'd imagine [09:21] i just had a friend leave my house. he's not a hacker, by far [09:21] but he's been using ubuntu for a bit over a year and gentoo before that [09:21] he stated something that he has observed -- [09:21] around 800 bug mails yep [09:22] in open source, nobody is really doing integration [09:22] and around 400 mails to my debian or ubuntu email (ie: not counting the mailing-list I'm subscribed to) [09:22] you get someone writing gnome power manager, and this other guy writing networkmanager [09:22] but nobody really makes sure that they work together properly [09:22] not always true [09:22] the only time people actually do this is when someone notices a problem, files a bug and makes the "other" maintainer aware of the issues [09:22] GNOME does try to do integration [09:22] i don't think we do very much [09:23] that's one of the reason why g-p-m didn't get accepted for desktop previous cycle no? [09:23] i'd say it can be done better [09:23] there were a lot of reasons for that [09:23] right, it can [09:23] g-p-m, wrt the rest of the desktop is pretty much a mess right now [09:23] our major problem, but also power is that our API's keep changing very very fast [09:23] but so is, say, networkmanager [09:24] they each have these wonderful (and sometimes overlapping) APIs/capabilities _that nobody uses_ [09:24] fabbione; own any apple laptop hardware? [09:24] desrt: ? [09:24] ibook, powerbook, macbook, anything? [09:25] desrt: i have a PB g4 now... [09:25] the latest one before Apple become an Intel company [09:25] the power brick came with a little plug that attaches directly to it and also came with a cord [09:25] s/company/reseller [09:25] does the cord feature a 2 or 3 prong plug? [09:25] desrt: still have problems with that? :) [09:25] pitti; i want to know if apple sells a 2-prong cord in any country on earth :) [09:26] desrt: the brick has 2 "holes" so even if the plug has ground, it's totally useless [09:26]