=== asac_ is now known as asac [00:25] I don't understand the purpose of ubuntu-devel being moderated, if "please put a browser on the Linux kernel and call it Ubuntu" makes the cut [00:27] I guess it's psychological [00:28] many people don't probably mail -devel because it's moderated :) [00:28] perhaps [00:31] slangasek: Maybe someone should ask Barry Warsaw for a "No, send this to devel-discuss" button for the moderator in mailman. [00:55] slangasek: indeed [00:55] clearly a browser on top of the Linux kernel should be called "ChromeOS" [01:50] Keybuk: that's *GNU*/ChromeOS [02:02] Back will it have emacs? [02:02] Back/But [02:12] ScottK, *insert tasteless yet topical joke involving emacs virgins here*? [02:12] Yeah, well I figured people would get that without me having to actually say it. [02:42] are we going to end up with packagekit in karmic? [02:46] i never got the jumping up & down people do about packagekit [02:47] * ScottK neither. We're using kpackagekit in Kubuntu and it's really unsuitable. [02:48] oh yeah? [02:48] Yeah. [02:48] ScottK: How does that work with debconf? [02:49] wgrant: It doesn't. That's one chunk of the unsuitableness. [02:49] ScottK: It's not the primary package manager, then? [02:49] wgrant: It is. [02:49] .... huh? [02:50] Our choices were Adept which was still beta and only barely being developed, kpackagekit which had some people behind it, or no GUI package management. [02:51] Personally, I'd have gone with choice 1 or choice 3, but it wasn't my decision. [02:54] It doesn't do any cryptographic verification of packages either (this may get fixed in Karmic). [02:54] It crashes a lot. [02:54] It doesn't notify about new packages reliably. [02:55] There's no way to do the equivalent of dist-upgrade. [02:55] Other than that, it's not too bad. [02:57] Um, how did it get away with not verifying signatures? [02:57] That sounds like about the worst possible kind of bug. [02:57] Well Adept 3 didn't do it either, so it wasn't a regression. [02:58] (Adept 2, the KDE3 one we had in Hardy did do this) [02:58] If it sounds like I'm grumpy about it, then your on track. [02:58] I'm very scared now. [02:59] Yeah, well except for this netbook that I'm about to reinstall, I've never installed a package using it. [04:03] slangasek: i don't think new subscriptions get moderated :( perhaps they should === WelshDragon is now known as YDdraigGoch [08:08] I'm looking for help to create a custom Ubuntu installer, that will create 3 partitions by default root swap home instead of the standard root swap that is the default Ubuntu install [09:06] (I answered tracyanne's question on #ubuntu-installer) === tkamppeter_ is now known as tkamppeter [09:29] jdstrand: thanks for merging it :) [10:23] q. i am building livecd, building the md5sum.txt consumes time, can i skip it if i am ready to give up the possibility to check the cd [11:03] slangasek: GNU/kLinux/ChromeOS [11:54] geez ... upstart fails totally random places if i try to build it [12:11] hmm and gcc-snapshot ftbfs on armel too ... bad [12:11] * ogra tries to build it himself [12:20] see you in 48 hours :) [12:20] oh just snapshot [12:21] well, 4.4 definately has issues, i want to see if they go away with snapshot [12:21] and my armel build system here is as fast as the buildds ... [12:23] is it failing making the lzma debs, or during the build/test runs? [12:24] its segfaulting during builds, sometimes it spills "internal error" during the tests ... totally random [12:24] bug 398403 [12:24] Launchpad bug 398403 in gcc-4.4 "gcc-4.4 fails to build upstart 0.6 on armel due to an internal compiler error" [High,New] https://launchpad.net/bugs/398403 [12:24] how much memory do those builders have? [12:24] 512M [12:24] (just curious) [12:25] i get random failures compiling gcc in 512MB on my OpenVZ VPS [12:26] well, i didnt get failures compiling gcc :) [12:26] i did get failures compiling upstart [12:26] gcc segfaulting or dying with internal error [12:26] never could figure out why, can compile it from upstream source fine but rebuilding the packages fails in random spots [12:27] jetienne: yes [12:27] cjwatson: thanks [12:28] thats exactly the error it fails out with too not that it says alot [12:29] gcc: Internal error: Killed (program cc1) that is, not failing in that specific spot.. some kind of ulimit problem maybe? [12:29] we'll see if it goes away if building with -snapshot [12:29] (once i have built that :) ) [12:30] well, i doubt that since i also get random segfaults [13:01] grr [13:01] gcc -c -g -fkeep-inline-functions -DIN_GCC -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wc++-compat -fno-common -DHAVE_CONFIG_H -I. -I. -I../../src/gcc -I../../src/gcc/. -I../../src/gcc/../include -I../../src/gcc/../libcpp/include -I../../src/g [13:01] cc/../libdecnumber -I../../src/gcc/../libdecnumber/dpd -I../libdecnumber genrtl.c -o genrtl.o [13:01] cc1: internal compiler error: Segmentation fault [13:01] Please submit a full bug report, [13:02] isn't that basically classic gcc FAQ symptoms of bad RAM? [13:03] particularly when intermittently reproducible [13:04] or I suppose that you're short on memory === Omegamoon is now known as Omegamoon|away [13:04] http://www.bitwizard.nl/sig11/ [13:05] I mean, obviously segfaults are often programming errors. But intermittent random-appearing segfaults in something like gcc that has known input and processes it in a deterministic way ... well, go figure [13:05] a gcc bug would not be the first thing I'd suspect for that, myself [13:29] pitti: hi, what space do you need for the ddebs archive? ISTR it was around 5GB/arch/release, counting main+restricted+universe+multiverse? [13:41] Hello [13:42] I want to interview with Ubuntu developer [13:42] for e-magazine [13:48] pitti: hmm, seems to be 12GB for main+universe on karmic/i386 ? === azeem_ is now known as azeem === Sarvatt__ is now known as Sarvatt_ [15:44] jdstrand: re bug 398445: it's already fixed but the fix didn't land yet on edge [15:44] Launchpad bug 398445 in soyuz "getPublishedSources dies with Internal Server Error on karmic distro_series (dup-of: 397732)" [Undecided,New] https://launchpad.net/bugs/398445 [15:44] Launchpad bug 397732 in soyuz "Getting an SPPH through the API crashes if the SPR is unsigned" [High,Fix committed] https://launchpad.net/bugs/397732 [15:44] jdstrand: getPublishedSources() OOPSes currently for every synced package === Rocket2DMn is now known as Guest3270 === Rocket2DMn_deskt is now known as Rocket2DMn [18:19] geser: ok, cool. thanks :) [18:26] is it normal for an Ubuntu server to ask me to reboot the system juist when I logged in? [18:26] do I have to worry? :| [18:39] <|Baby|> anyone with a Nvidia graphic card might want to help me test a game package? === |Baby| is now known as Baby [18:39] Carroarmato0: wrong channel [18:39] try ubuntu-server or something [18:40] tgpraveen2, sorry about that === thekorn is now known as THEKORN === THEKORN is now known as thekorn === MobileMyles6o7 is now known as TwoToneSpirit === |Baby| is now known as Baby [20:33] ping pitti - hey. do you know if devicekit-power is already used in karmic? i'm wondering because i don't see support for quirks in the code [20:35] i ubuntu-desktop Depends gnome-power-manager, i A gnome-power-manager Depends devicekit-power (>= 009) [20:36] ion: yeah. but i think HAL is still used for some stuff (or at least it can be used by devicekit-power.. from what i read on their mailing list). so i'm not sure if the quirks are available or not === WelshDragon is now known as YDdraigGoch === evanrmurphy is now known as evanr === evanr is now known as evanrmurphy [22:24] hiho [22:25] we develop http://dooble.sf.net --- currently making the linux release [22:26] the idea is, to maybe later add an linux kernel, so to have the browser as the gui [22:26] anyone insterested to join or help to create a deb. file for the linux release? [22:28] a browser on top of a kernel? that sounds familiar :) [22:28] realo: no one here right now, probably better to post a message to udd [22:29] uud? [22:30] yes a browser on top of a kernel [22:30] dooble has a desktop integrated for that [22:30] What is the best way to work on a merge issue when a package is assigned to Ubuntu Core Developers? (to check we are not duplicating work) [22:31] pam, contact last uploader [22:31] mok0: ok. Thanks [22:43] realo: 'udd' == 'ubuntu distro development' list, I think [22:44] ubuntu-devel-discuss [22:44] cjwatson: Do you know if anyone is looking at the gfxboot patches for syslinux (merge issue)? Not sure https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/270822 is the official bug. Otherwise, I'd be happy to give it a shot (we already talked a bit about it with hpa). [22:44] Ubuntu bug 270822 in syslinux "please upgrade syslinux from debian to 3.80" [Low,Triaged] [22:44] (offtopic) realo: Dooble seems to contain RetroMessenger, which seems to be based on RetroShare. The last time i looked, RetroShare was horribly insecure. It used an ancient version OpenSSL (∴ many unpatched security holes) with a RetroShare-specific patch (that appears to be a pain to rebase against a newer version of OpenSSL). [22:45] Laney: ah thanks [22:47] pam: probably not for karmic [22:47] pam: seems like a heck of a lot of work in a critical component, would rather do it at the start of a release [22:48] pam: if somebody wants to do it, I guess I can review it, although I expect that reviewing it might actually be as much work as just doing it myself ;-) [22:48] heh [22:48] pam: although it *is* good news that the gfxboot patches are merged upstream [22:48] is it possible to upgrade the kernel + intel drivers to jaunty without all the other upgrades? [22:49] oops maybe i'm in the wrong channel :( [22:49] pam: so, I don't have time, but feel free to suggest patches in the form of a diff against the current package in Debian unstable. Please test them with current CD images [22:49] cjwatson: getting rid of the old suse patch would be great [22:49] okay [22:49] cjwatson: Just wanted to double check you are not actively working on it right now ;) [22:50] I am not [22:50] I've commented on the bug. Depressed as usual about bugabundo's rather direct attitude [22:51] is there a mini iso for karmic yet? [22:51] Thanks for the comment. Will ping hpa about it as soon as he is back. [22:51] maco: always was [22:51] apparently cdimage is not the right place to look...got a hint for me? [22:51] pam: why hpa? I know he's upstream, but I wouldn't expect him to be involved in Ubuntu packaging [22:52] oh, no links on cdimage/netboot/, bah [22:52] maco: look at /netboot/jaunty/ on cdimage, do the obvious URL substitution :-) [22:52] I'll sort out cdimage now [22:52] ok [22:53] oh, actually [22:53] maco: http://cdimage.ubuntu.com/netboot/karmic/ does exist, it's just not linked from /netboot/ [22:53] yeah, i see that [22:53] cjwatson: we talked about reducing the amount of changes between distro and upstream a while ago. Just want his take again. [22:53] (fixeD) [22:53] i keep trying to look in cdimage.ubuntu.com/karmic/ [22:53] thanks [22:53] pam: that's usually best done by forwarding patches :-) [22:54] Forwarding? Meaning forward-porting your patches or submitting them upstram? [22:54] +e [22:55] the latter [22:55] what I mean is, there's little point in agreeing some kind of joint position statement with upstream that we think we should be shipping the same thing :-P [22:55] developers are practical people - just send patches around if you want to get things in sync [22:56] Yeah, IIRC he didn't like the overall approach and had ideas about improving that. [22:56] anyhow, I think the only patches we have against syslinux aside from gfxboot are pure packaging, not anything to do with upstream [22:57] That should be easy. [22:57] so if gfxboot exists upstream as a module now then there's nothing else to be done with hpa [22:57] Anyway, there is a lot of work being done with gsoc this summer (ext4, hdt, ...) and upgrading ubuntu package would really benefit the distro [22:57] but it *does* need to be smoke-tested (preferably in at least isolinux and syslinux modes) before just dropping it into Ubuntu [22:58] definitively [22:58] that should be fairly straightforward for somebody with time who more or less knows their way around; have at it ;-) [22:58] heh [23:05] bug created: https://bugs.launchpad.net/ubuntu/+bug/398575 [23:05] Ubuntu bug 398575 in ubuntu "[needs packaging] Dooble Web Browser" [Undecided,New] [23:06] pam: (oh, and thanks in advance. not enough hours in the day ...) [23:07] cjwatson: You're very welcome.