=== WelshDragon is now known as YDdraigGoch [00:28] The link at the end of the topic is broken, probably because you seem to have hit the limit. :) === cjwatson changed the topic of #ubuntu-devel to: gdm breakage: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2009-July/000586.html | Archive: open | DebianImportFreeze in effect | karmic alpha-2 released | Development of Ubuntu (not support, not app development on Ubuntu) | #ubuntu for support and general discussion for dapper-jaunty | #ubuntu-motu for getting involved in development | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu. [00:31] blink, pitti's client obviously allows a longer length than mine === cjwatson changed the topic of #ubuntu-devel to: gdm breakage: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2009-July/000586.html | Archive: open | DebianImportFreeze in effect | Development of Ubuntu (not support, not app development on Ubuntu) | #ubuntu for support and general discussion for dapper-jaunty | #ubuntu-motu for getting involved in development | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs [00:31] hopefully gdm won't be an issue by the time alpha-3's released [00:32] any bug numbers for that which ought to get milestoned? [04:57] hello team if nobody has any objections I ll prepare diffs for some packages affected by https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/391165 [04:57] Ubuntu bug 391165 in dpkg "Dpkg::Deps mishandles newlines in Build-Dependencies" [Undecided,Fix released] [05:08] how do you choose login language now? [05:12] Down the bottom of the GDM screen there's a listview. [05:12] A _dreaded_ listview :). Maybe we can make gdm crash :) [05:14] This only appears when you've selected a user to log in as, though. [05:20] not with todays gdm :P [05:20] OTOH I'm getting other errors all over the place [05:22] Heh. I think I might still have gdm -ubuntu3 here, so... [05:55] RAOF: Do you know of a bug about the listview crasher? [05:56] wgrant: Yeah; it's... [05:56] bug #391398 [05:56] Launchpad bug 391398 in gtk+2.0 "Applications segfault with gtk+ version 2.17.2 when selecting listbox values" [High,Confirmed] https://launchpad.net/bugs/391398 [05:56] RAOF: Thanks. [05:56] It's apparently gtk using deprecated APIs internally, and missing the crucial difference between an int and a pointer. [05:57] Haha. [05:57] It's also incredibly annoying. [05:57] Yes. [05:57] I can't *quite* work out how to trigger it. [05:58] There are some git commits referenced in that report, and, of course, sizeof(int) == sizeof(void *) for IA32. [05:59] wgrant: Evolution is the best way of triggering it that I've found. [05:59] RAOF: Some listboxes only do it when you manipulate them in a particular way. [06:00] The OS selector in virt-manager, for example. [06:00] Yeah. [06:00] It's usable unless you use it wrong. [06:00] Which is why I haven't rolled a local gtk package with those git commits added; it's insufficiently annoying. [06:00] It's _just_ easy enough to work around :) [06:01] Yep. [06:02] There'd be a PPA one by now, if the buildds weren't supersaturade [06:02] *supersaturated [06:03] Yes... [06:03] All those daily builds, and only three guaranteed buildds per arch... [06:04] wgrant: be glad it's not daily builds of bigger packages [06:04] ajmitch: They are pretty big... [06:08] it shouldn't be so easy to cause a permanent backlog [06:15] I suppose it could be worse. It could be dailies of OOo :-) [06:17] maxb: I was thinking of that one, as well as ooo-l10n :) [06:17] just hoping noone is trying to build 3 gcc's in there or else we'll be out another entire day :D [06:18] Or a Linux or three. [06:18] * maxb wishes for bug 155758 [06:18] Launchpad bug 155758 in soyuz "Global PPA +builds would be useful" [Medium,Triaged] https://launchpad.net/bugs/155758 [06:19] Unfortunately that wouldn't be reliable now. [06:19] i'd put $10 on theres at least 10 linuxes lined up in that i386 queue [06:19] As there are lots of P3As. [06:19] its the new fad :D [06:19] That bug has a nice activity log. [06:21] Unless P3A builds just vanish the builder from the builders page, there don't seem to be that many P3A builds [06:22] maxb: The builders appear with a red X next to them. Sometimes there are lots, but sometimes there are none. [06:24] ok - I've not seen that for PPA builders very often [06:24] So I think a PPA +builds would still be adequately useful [06:24] Maybe I just look at it at bad times. [06:24] It would certainly still be useful. === fddfoo is now known as fdd [07:02] good morning [07:03] pitti: can you merge ~chrisccoulson/gnome-power/2.27.2-update into ~gnome-power-manager-team/gnome-power/trunk ? [07:04] (I should have checked before, but I thought "it's going to be a ~ubuntu-desktop branch I can push to") [07:07] Good morning [07:08] cjwatson: hm, /topic looks fine for me indeed [07:09] but I think we can remove the gdm link tomorrowish [07:17] dholbach: pulled, and debcommit -r'ed; thanks! [07:17] pitti: thank chrisccoulson :) [07:17] I will (and did yesterday), but not online ATM :) [07:18] * TheMuso sees that keyboard backlight devices/ambient light sensor support was removed, and wonders why, since the git log doesn't go into any detail. [07:18] from gnome-power-manager that is [07:19] TheMuso: this is currently a bit in flux [07:19] TheMuso: we don't use hal any more, and devkit-power doesn't have/isn't supposed to have that [07:19] the correct solution is to have this in X itself (XBACKLIGHT) [07:19] ah ok [07:19] http://lists.freedesktop.org/archives/devkit-devel/2009-July/000268.html FYI [07:20] tah [07:21] asac: did you see the "also introduces a bug" report in bug 220628 ? [07:21] Launchpad bug 220628 in libxcb "[MASTER] firefox-3.0b5 received an X Window System error: 'BadIDChoice'" [Medium,Fix committed] https://launchpad.net/bugs/220628 [07:22] sbeattie: thanks for all the vm-builder tests! I think it's good enough to move to -updates now [07:23] * mvo hugs sbeattie too [07:24] pitti|mvo: thanks, and I agree, it should go to -updates. [07:26] nice, 335 days in -proposed [07:30] ...oh and wow, what an argument. :) [07:33] <\sh> moins [07:33] TheMuso: was pretty heated indeed :/ [07:35] <\sh> dear devs, please get rid of klibcs ipconfig for kernel nfs root mounts...it's really a pain in the a** *gnarf* [07:37] <\sh> ipconfig + low cost table switches == works like a charm, but using cisco switches with spanning trees and portfast configs etc. it gives you really nightmares [07:39] <\sh> the timeframe between bringing the NIC up and the first dhcp request from ipconfig is too fast and then it failes mostly with a kernel error: can't mount nfs rootfs , setting the timeout up to 180 secs (which should be more then enough to have ipconfig retry it's request) is not even enough...-t 240 to -t 360 is the only way to force ipconfig to redo the request...but that's far too long [07:54] jcastro: who is in charge of the web server? there's a bug with videos.ubuntu.com [07:54] (it's showing wrong MIME type, labeling the videos as text/plain, so this happens (except in Firefox): http://i41.tinypic.com/14ub8xz.png [07:57] YokoZar, You might try a bug against ubuntu-website (although it may be different) [07:57] persia: yeah i just had that thought [07:57] thanks [08:30] are there bugs open for gdm-login-twice and gdm-gnome-session-can't-remember-bla? [08:45] dholbach: for the latter, yes [08:45] dholbach: for the former, what do you mean? [08:45] the popup I get after logging in [08:46] gnome-session couldn't save your bla something gdm-simple-greeter [08:46] hiya chrisccoulson [08:46] dholbach: right, that's "the latter", and has a bug [08:46] dholbach: I mean "login-twice"? [08:46] ah sorry :) [08:46] hi dholbach [08:46] hey chrisccoulson [08:46] when I log in, it starts doing something, then I get the login window again [08:46] hi pitti [08:46] so I have to log in twice [08:47] dholbach, I had that, and TheMuso had that. I had a hw failure when reproducing, and haven't filed. If you do file, please subscribe me. [08:48] hm, no /var/log/gdm? [08:49] pitti: clearer now? [08:49] I’m sorry, but i snickered at “I had a hw failure when reproducing”. [08:49] dholbach: ah, bug 396226 [08:49] Launchpad bug 396226 in gdm "GDM logs out after some minutes of typing on the keyboard" [Critical,Triaged] https://launchpad.net/bugs/396226 [08:50] dholbach: that was extensively discussed, and the problem is understood, but not quite trivial to solve [08:50] dholbach: workaround: disable "splash" [08:50] pitti: I'm not sure I have that problem - it's not several minutes [08:50] well, it depends what you are doing [08:50] I boot, get gdm, log in, it does something for 1-2 seconds, then gives me the login window again [08:51] dholbach: and then it never crashes again? [08:51] no, then I can go ahead and do my stuff [08:51] ok, sounds like that bug then [08:51] dholbach: try booting without splash, that should fix it [08:51] ok, I'll try with the next reboot [08:51] thanks pitti [08:51] * pitti hugs dholbach [08:51] more power to the pitti! [08:52] dholbach: is your other problem bug #395324? [08:52] Launchpad bug 395324 in gdm "'These windows do not support "save current setup"....' metacity warning when logging in with gdm 2.26" [Medium,Triaged] https://launchpad.net/bugs/395324 [08:52] geser: yes, I guess so [08:52] pitti, just with nosplash on the kernel cmdline? [08:53] persia: drop "splash" [08:54] OK. Booting with "nosplash" fixed it for me. Trying again without any mention. [09:00] pitti: interesting, which gdm versions does that problem affect? [09:00] ajmitch: >= 2.26 [09:01] I'm guessing it only affects some people, since I haven't had a problem since rebooting [09:02] Booting without any mention of splash fixes it as well. [09:02] ajmitch: check on which tty you currently are on: tty1 or tty7 [09:03] persia: I know I have splash set, I had to wait through a fsck of 450GB [09:03] geser: X reports being on tty7 [09:03] ajmitch: then you are lucky [09:04] ajmitch, Dunno then. Just started happening to me yesterday on karmic. Doesn't happen anymore without splash. [09:04] it only happens when gdm and getty fight for tty1 and gdm loses [09:04] sounds like a fun bug to solve [09:06] geser, Amusingly, I have X on tty7, once it works. [09:07] Well, easy way to fix it is just to get the boot fast enough that we don't need splash, which I understood to be the goal. [09:07] yes, it only happens to the first gdm, after one gets kicked gdm takes tty7 [09:34] pitti - would you like to review the changes in https://code.edge.launchpad.net/~chrisccoulson/gnome-session/ubuntu ? It splits gnome-session in to 2 packages now. With the current single package, the new GDM dependency on gnome-session causes a broken gnome to be started on Xubuntu instead of xfce [09:36] chrisccoulson: right, this was discussed yesterday; is this a Debian merge? (they did the split) [09:36] the split is basically taken from debian, with a couple of minor changes. they also moved all the autostart files from /etc/xdg/autostart to /usr/share/autostart, which hasn't been copied across [09:38] and i put the helpers in gnome-session instead of gnome-session-bin, although these need splitting some more, as GDM requires the g-s-d helper it seems [09:39] and i've just noticed the gnome-settings-daemon dependency needs to move from gnome-session to gnome-session-bin, as that seems to be required by GDM too [10:02] cjwatson, please merge (once again) https://code.launchpad.net/~ogra/debian-cd/ubuntu ... for the armel kernel version bump === asac_ is now known as asac [10:04] i'D really like to find a way to automate that ... even if its only screen scraping the d-i changelog [10:08] mr_pouit - i merged your changes on the gnome-session split last night [10:08] this would still leave you with 2 session managers on the default install though wouldn't it? [10:10] mvo: btw, did you see my reply in bug 392074? [10:10] Launchpad bug 392074 in apport "better client side apport_kernelcrash support" [Low,Incomplete] https://launchpad.net/bugs/392074 [10:12] pitti: confirmed (gdm-login-twice) [10:13] pitti: I had this spec on hold until some linux-meta fixes, sorry - I will answer in the report, but the summary is that its (or seems to be) useful if the user wants to do a local retrace [10:14] mvo: it shouldn't; well, let's discuss it in the bug repor [10:14] t [10:15] pitti: maybe I don't understand apport well enough, but its seems to me that adding the information right away is cheap and useful. it shouldn't means that it should not include this information? [10:16] we can as well talk here, its probably quicker :) [10:16] mvo: no, but the information you want (and more) is already collected [10:16] so fater a reboot the vmcore is converted to a crash file. at this point not a lot of info is there [10:17] right, you need to process it through apport [10:17] now if the user wants to run apport-retrace on this that will fail until it got processed further [10:17] (... UI) [10:17] so this should not be a supported use-case? or should apport-retrace add the info? or should it be first go through the UI and then do a local retrace? [10:17] mvo: phone, bbl [10:18] dholbach, happens to me too [10:18] is there a bug report for gdm-login-twice? [10:18] bug 396226? [10:18] Launchpad bug 396226 in gdm "GDM logs out after some minutes of typing on the keyboard" [Critical,Triaged] https://launchpad.net/bugs/396226 [10:19] mdz: the workaround is to disable 'splash' [10:19] Laney, That's not the same bug. [10:20] persia: pitti said it was [10:20] * persia rereads the bug again [10:22] Hrm. I'm not sure how the race could persist for minutes, but perhaps. [10:37] hmm, isnt gdm supposed to run on tty1 with the latest upgrade ? [10:37] * ogra still has it on tty7 [10:37] ogra: merged that debian-cd branch, thanks. The way to automate it is to get the kernel fixed so that we don't need it [10:37] cjwatson, indeed, but i was looking for an interim solution [10:38] the prob is that i only notice it a day after the builds failed [10:38] damn gotto love flash :( NOT :( [10:38] and i dont want to trigger .1 builds ... just because i forgot once again to notice the d-i upload on -changes [10:39] though i'm starting to care for armel builds again, shouldnt be that often anymore if i'm really caring [10:43] ogra: ok, I've killed off the hardcoding [10:43] (though haven't tested the new code straight-through) [10:44] oh ! [10:44] wow, thanks [10:44] i also noticed that someone already added the subarchitecture (armel+imx51) code to make-web-indicies :) [11:02] wow, switching between a VT and X on karmic is super fast. [11:03] And that's one reason KMS is win [11:08] StevenK: totally :) [11:13] re [11:13] ogra: no, it's not really supposed to run on vt1, since it conflicts with getty there [11:13] mdz: ^ [11:13] mvo: re [11:14] sorry, that was a long phone call [11:14] i though getty was gone in favour [11:15] mvo: any news on pdiff? Did you test the curret git of a-x-i? Can I just go ahead and upload? [11:17] mvo: (answered) [11:23] Keybuk: I have a udevd here which appears to be refusing connections from udevadm - I don't know if I'll be able to reproduce this, so is there anything I can do to debug things before I reboot? [11:23] (this is in d-i) === yofel_ is now known as yofel [11:25] Keybuk: actually, they don't even seem to be getting the message from udevadm at all, judging from strace [11:25] it's like they've fallen off the Unix socket namespace or something [11:28] pitti, hmm? [11:29] ah, a udevd segfaulted somewhere ... [11:30] cjwatson: that's odd, normally it tends to go away on a segfault ;) [11:32] I guess some bit of it did but the rest hung around in a broken state [11:35] Keybuk: well, bug 396957, I don't know if there's anything useful that can be done with that but just in case [11:35] Launchpad bug 396957 in udev "udevd segfault after "worker did not accept message" and "worker unexpectedly returned with 0"" [Undecided,New] https://launchpad.net/bugs/396957 [11:36] cjwatson: I wonder whether the daemon died and left some workers? [11:36] yes, it looks like it [11:36] do you have a copy of "ps" at the time? [11:36] at which time? [11:36] at the time you thought "oh, this has died" [11:36] also, no core dump? [11:36] have you looked in /var/crash? [11:37] it's got four "udevd --daemon --resolve-names=never" processes [11:37] do you need the whole thing? [11:37] sure, but the details of those four would be quite interesting [11:37] no /var/crash in d-i [11:37] ah, in d-i [11:37] damn [11:37] no /core ? :) [11:37] no, sorry :-/ [11:37] can you attach dmesg to that bug report (not dmesg log) [11:38] oh, it's ok [11:38] done, and ps output too [11:38] I think dmesg all just goes to syslog though [11:39] yeah looks like it [11:43] Keybuk: if it's relevant, it's possible that udevadm trigger may be involved here, since the point where it failed is shortly after d-i installs extra udebs into memory which may contain new kernel modules [11:43] that may just be coincidental though [11:44] hmm, I don't suppose we keep separated debugging symbols for udebs anywhere ... [11:45] we do! bloody hell [11:46] pitti++ [11:51] pitti: is there any way to get back from "udevd[663]: segfault at 4 ip 00959fbc sp bfbe7b78 error 6 in udevd[94f000+1c000]" to a line of source, assuming that I have the corresponding udevd with debugging symbols loaded in gdb? [11:52] * pitti scratches head [11:52] I assume relocation is going to screw me over somehow [11:54] yeah you need a core file [11:55] of course, "segfault at 4" is a bit damning in of itself ;) [11:55] oh, is that an address? :) [11:55] yes [11:55] well [11:55] it's _supposed_ to be the address ;) [11:56] "info symbol" might help [11:56] so it is [11:56] I assume it's karmic? [11:56] yes [11:56] udev-udeb 143-8 [11:56] (i386) [11:56] list *(address) could also help [11:56] info symbol what? [11:57] would the IP be a valid address? [11:57] it doesn't like either 0x00959fbc or 0x1c000 [11:57] list *(00959fbc) ? [11:57] cjwatson: i386 or amd64? [11:57] 11:56 (i386) [11:57] pitti: nope [11:58] I used that for kernel panics and traces === tkamppeter_ is now known as tkamppeter [11:58] 0x00959fbc - 0x0094F000 == 0xAFBC [11:58] which is apparently udev_list_node_remove + 11 [11:59] that being 0x0000afbc : mov %edx,0x4(%ecx) [11:59] and udevd.c:handle_signal calls udev_list_node_remove right after the last error message from udevd in the log [12:00] that sounds totally plausible [12:01] where did you get the 94f00 from? [12:01] udevd[94f000+1c000] [12:01] interesting [12:01] I guessed that that was a relocation base address [12:02] indeed it's vma->vm_start in the kernel [12:02] the next one being the size, I assume? [12:02] vma->vm_end - vma->vm_start [12:02] so yes [12:03] (this is print_vma_addr in mm/memory.c) [12:06] next->prev = prev; [12:06] would be the crashing line then [12:06] or prev->next = next; ? [12:06] no, that one [12:06] info line *0xafbc [12:06] Line 76 of "../../udev/libudev/libudev-list.c" ... [12:07] ah, good call [12:10] Keybuk: is there anything more that might be extractable from the running image, or can I reboot it? [12:13] cjwatson: I don't think so :-/ [12:14] bit of an exercise in telepathy [12:14] ok, let's see if it happens again ... [12:16] mvo, python-apt is deprecating some stuff; is there a transition guide to convert them to new stuff? [12:24] Keybuk: oho, it happened again [12:25] let me see if I can make it happen a third time but this time with a core dump [12:26] cjwatson: neat [12:29] hmm. lots of workers unexpectedly exiting, but the daemon isn't crashing after ulimit -c unlimited ... [12:41] damn! I reproduced it and then alt-f4'ed kvm by accident [12:41] hate that keybinding [12:42] doofus [12:43] while :; do update-dev; kill -HUP $udevd_pid; done # seems to trigger it eventually [12:43] pkill -HUP udevd? :-) [12:43] d-i [12:43] Alright [12:43] thanks but there's no need to educate me in tools that I know about and also know are not available in this context ;-) [12:44] and in any case I explicitly don't want to kill the udevd children, only the parent [12:44] Right [12:44] enrico: no news on pdiffs, sorry. but I tested it and it looks fine [12:44] gotcha [12:45] liw: no formal one afaik, but julianK may be preperaring one. its bascily "installVersion" -> install.version [12:47] mvo, ok, I'll how that works for me [12:48] Keybuk: core dump on the bug now, though I'm having no luck at getting gdb to take it here [12:52] mvo: ok, then I'll just upload it as it is, and we can do an extra improvement step if the pdiff way is viable [12:53] cjwatson: Do you not use -no-quit? [12:53] in KVM, that is [12:55] enrico: excellent [12:57] evand1: I may do from now on :) [12:57] I didn't know about that [12:57] I think we all find out about it the hard way [13:11] * Keybuk weeps about how needlessly hard utmp/wtmp is [13:13] Yeah [13:13] at least I finally figured out why "last" thinks all rebooted Upstart-based machines "crashed" :-) [13:17] cjwatson: mind applying http://people.ubuntu.com/~scott/d-i-udev-crash.patch and trying again? [13:22] is it ok to rebase an SRU candidate with the stable debian version, if the packages are derived from the same version? [13:23] Keybuk: thanks - rebuilding [13:23] tjaalton: not usually - keep the change minimal [13:24] cjwatson: ok, I [13:24] hrm [13:24] I'll just snatch the patches then [13:26] cjwatson: at the very least, this will add a message saying why it's about to crash :p [13:48] pitti: ping [13:48] hey djsiegel_ [13:52] pitti: sorry, as soon as I contact you I get interrupted... [13:52] 2 minutes... [13:52] pitti: ok [13:53] pitti: openSUSE, Jolicloud, and now moblin are integrating Do [13:53] pitti: I have a lot of feedback from UNR users who installed Do and put it to great use [13:53] I think it's even being considered for UNR already [13:54] Mark asked me 8 months back about putting in main, and I said -1 because it's kind of an advanced user app [13:54] but I am getting a lot of pressure from GNOME at GCDS to put it in GNOME (I think they are determined to) [13:54] so, I think we should talk about shipping it with karmic [13:55] djsiegel_: hm, I haven't used it myself, but it seems to me that gnome-shell does a lot of this as well? [13:56] pitti: no, it's very different [13:56] pitti: and are we shipping gnome-shell in Karmic? [13:56] djsiegel_: not by default, but it'll be available [13:56] we would if upstream did [13:56] Do is tested, translated, and has millions of installs [13:56] gnome-shell will not be on in 2.28 [13:57] it indexes your online contacts, docs, twitter friends, etc etc etc [13:57] using tracker? [13:57] no, its own indexer [13:57] uh [13:57] Mark said he was for it, and to talk to you, Keybuk and Ivanka [13:57] we made lots of bad experience with tracker and beagle [13:58] is gnome-do more lightweight in indexing all your files? [13:58] Tracker doesn't index your online life [13:58] how do we make do discoverable to new users? [13:58] (and it seems utterly hard to get file indexing right) [13:58] pitti: it's not file search [13:58] djsiegel_: right, I know; does gnome-do index your local files? [13:58] ah, ok [13:58] pitti: yes, you can set it to [13:58] for example, index just your desktop, or your docs folder 2 levels deep [13:58] djsiegel_: my main concern is how long it'd take to start [13:58] pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com [13:58] dpkg-deb: warning: 'debian/libgl1-mesa-dri-dbg/DEBIAN/control' contains user-defined field 'Original-Maintainer' [13:58] dpkg-deb: ignoring 1 warnings about the control file(s) [13:59] Keybuk: I don't suggest turning it on by default [13:59] hrm, whats that ? [13:59] just putting it in Accessories [13:59] djsiegel_: I'm pretty much against indexing your files by default, but anything other than that I'm open (CD space constraints apply, of course) [13:59] pitti: it doesn't index by default [13:59] djsiegel_: if you start it from Accessories, how do you configure it to start on startup if you like it? [13:59] just your apps [13:59] by default [13:59] Keybuk: in the Do prefs, you check the "Start at login" checkbox [14:00] djsiegel_: ok, easy enough then :) [14:00] I'm all for it [14:00] Session terminated, killing shell...make: *** [binary-arch] Terminated [14:00] ...killed. [14:00] Build killed with signal 15 after 150 minutes of inactivity [14:00] mumble === robbiew-afk is now known as robbiew [14:00] ogra: why did your build have a terminal session open? :) [14:01] Keybuk, ask infinity :P he maintains the armel buildds ... [14:01] I am not crazy about it, I don't think it's the future of the desktop or the perfect app or great for all users, but EVERYONE seems to be shipping it and making at least some of their users happy, so it seems like we should have it too. === akgraner__ is now known as akgraner [14:02] Keybuk, i was always suspecting he secretly sits in the DC and plays nethack on the armel builder consoles to interfere with the builds :) [14:02] I mean, if GNOME Do is being used to make any linux offering more attractive, it should be the linux offering of the company I work for and believe in. [14:02] djsiegel_: ok, then it seems the remaining question is to find a maintainer for it [14:02] pitti: find a maintainer? [14:02] djsiegel_: for the packaging [14:02] pitti: Chris Halse Rogers [14:02] no, but honestly, why does pkgmaintainermangler hang for 150 min [14:03] pitti: RAOF on freenode [14:03] djsiegel_: for keeping up with the bugs, packaging, testing in Ubuntu, etc. [14:03] yes, basically our entire project targets ubuntu [14:03] it's maintained in the CLI apps team :) [14:03] RAOF does Ubuntu stuff [14:03] we have 5 core contributors, all use ubuntu, and we target all of our releases to land in ubuntu [14:05] ok, easy next step then [14:05] one of them should write a MainInclusionReport for it [14:05] that sounds good [14:06] and they should talk with Colin or Steve about CD sizes requirements [14:06] apt-get install gnome-do pulls in 6.7 MB [14:06] that's very heavy [14:06] *choke* [14:06] yeah, that may need to be addressed [14:06] gnome-do-plugins is 5.7 [14:06] perhaps drop gnome-do-plugins to Suggests? [14:07] half a megabyte for gnome-do itself still probably means one fewer language on the CD, but is a bit more tolerable [14:07] (one MB) [14:08] pitti: really, what else is it depending on that f-spot and tomboy don't already? [14:08] libevolution5.0-cil libgdata1.4-cil libgnomedesktop2.20-cil librsvg2-2.18-cil libwnck2.20-cil [14:08] we could drop some plugins [14:08] in the gnome 3 work flow. do might not be required just my 2 cents [14:08] libgnomedesktop2.20-cil should disappear anyway [14:08] it's deprecated [14:08] split out the community plugins should drop 3-4mb [14:09] djsiegel_: even 3MB is a lot of ask for the CD [14:09]