=== dendro-afk is now known as dendrobates [01:16] lamont: Around to talk a bit about fairly important buildd changes? [01:26] wgrant: fyi. he may answer anyway; but he eod' about 90 mins ago. [01:30] spm: Oops, I thought it was closer than that, but I forget that DST switched off a few days ago. [03:11] wgrant: heading out to dinner with my sister - catch me tomorrow PST work hours? [03:12] lamont: OK, I'll try to catch you late in that interval. [03:13] sounds good - when do you come online? (UTC fine) [03:14] lamont: I'm +11 at the moment, and am normally around from about 2100 UTC. [03:15] so yeah - I'm generally wrapping things up and getting ready to run by 2200-2300UTC [03:15] Right. [03:17] and this week, I'm -8, and trying to be done by 3PM local --> 2300... so not too bad === dendrobates is now known as dendro-afk === dendro-afk is now known as dendrobates [03:54] Just watched karmic boot cd fry a monitor [03:54] On first boot, i386 [03:56] fry a monitor? [03:56] that's pretty interesting. i wanna see too [03:57] Yep, booted until modesetting for 2nd splash [03:57] Flashing light now [03:57] Can't even display post [03:57] Dead [03:58] do you smell anything? =p [03:58] Not my pc either, after installing ubuntu for people for 4 years, I get to buy a monitor [03:58] No [03:58] No burning, nothing of the sort [03:59] heh [03:59] well, if it can burn from improper settings, it sure as hell has to be very old =p [03:59] about time, i'd say [03:59] I think that monitor is disobeying some fairly important common sense. [03:59] i agree [03:59] Yeah, Dell 15" , veery common [03:59] Scary how common actually [04:00] For legacy desktop stuff [04:00] About time? It's now on me to replace it, way to go [04:01] Just figured I'd tell you, but I guess it's just on everyone to upgrade [04:03] ScottK, around? [04:03] I really hope that isn't the stance shuttlesworth wants .com take [04:03] jcastro: Yep [04:03] ScottK, pretend I want to run -proposed to be a good citizen so I can find bugs before they hit -updates [04:03] exewmt: this isnt where bugs get reported [04:03] exewmt: I think it's worth a bug report, although I think it's unlikely it's anything other than coincidental. [04:04] There should be a big red banner until that gets fixed though, because Dell has sold millions of these models in the us [04:04] ScottK, is there a bug list or tag I can follow? [04:04] jcastro: There is. Let me find it. [04:04] "warning: using the wrong mode is bad for screens"? [04:04] jcastro: ;-) [04:04] Scott: I watched it, it booted to splash [04:04] jcastro: Did the OpenWeek PDF get fixed. [04:04] I don't think it did [04:04] MsMaco: It's Automaticc [04:04] MsMaco: The thing is, it hasn't been bad for them for like 15 years. [04:05] wgrant: wow [04:05] exewmt: I'm not saying it didn't fry when you booted it, I'm just saying I think it's unlikely it was caused by a bug. [04:05] ScottK, I can check it now [04:05] I still think it's worth filing, just in case. [04:05] ScottK: Thing is.... It won't even go to amber led [04:06] exewmt: I don't doubt it died. [04:06] Now just the same flashing green that first occurred when mode changes to grey screen w bar in boot seuence [04:06] like, right when the mode changes to 2nd booting splash [04:06] jcastro: http://people.canonical.com/~ubuntu-archive/pending-sru.html - I don't recommed 'running proposed' however. I recommend enabling it, installing just the package you want to test, and then disabling it. [04:07] That is why I don't think it was purely coincidence [04:07] I have a few more, should I fry another! [04:07] ? (sorry touchtyping$ [04:07] Oh, right, I forget about the DIEMONITORDIE command that xsplash sends on startup. [04:08] is debootstrap ready so i can set up a chroot for Lucid? I was looking at it and noticed its the same one as used in Karmic [04:08] wgrant: Just saying that between every other ver of xsplash used [04:09] Maybe t's a bug affecting the ver bundled in the cd [04:09] exewmt: What's in the CD and in the archive is the same. [04:09] serialorder: I think they added lucid to the karmic one before release. [04:10] ScottK, I've always just thought we're supposed to run -proposed and report bugs. [04:10] k, But should I test w an identical monitor and see if it bricks it? [04:10] exewmt: Your call. If it did, it would be pretty conclusive. I think it's unlikely to. [04:11] jcastro: I know people do that, but I don't recommend it nor do it myself. The point is that we put stuff in proposed to test it and it doesn't always work out well. [04:11] jcastro: That can cause problems when something is copied from -proposed to -updates, and all the testers use -proposed in its entirety. It could be broken with versions in -updates. [04:11] ScottK: We have a running bet then [04:11] I'll be back tomorrow to report [04:11] So it's important to get people to test each -proposed package with everything else in -updates. [04:12] jcastro: I've personally seen more problems with running -proposed than with -backports. [04:12] ScottK: that doesn't sound positive [04:12] i usually run with proposed enabled [04:12] ajmitch: Thus my recommendation. [04:12] wow [04:12] I've also almost never seen a problem with backports. [04:13] has anyone noticed any issue with the recent udev SRU? [04:13] ScottK: i can think of one problem with backports :P [04:13] I hadn't noticed there was a udev SRU [04:13] I remember that one. [04:13] ScottK, I only noticed this problem now when LaserJock told me his empathy was crashing and I asked him to enable -proposed and he was wary of enabling the whole thing [04:13] ScottK, thanks [04:14] ScottK, has someone talked about this with like pitti or something? [04:15] jcastro: It gets discussed every now and then. [04:15] well the point of proposed is to catch bugs... [04:15] it seems like we had some threads about this like a year ago [04:15] So far the "If we have people enable everything, we get more testers" has won the day. [04:15] LaserJock: We did. [04:15] something about when the desktop team was thinking of having a staging PPA or something [04:17] for me a lot of the -proposed vs -backports issue stems from a lot of -proposed packages being pretty core things [04:17] I don't often get a whole new kernel, Xorg, evolution, etc. from -backports [04:18] :-) [04:18] well, backports are new upstream releases [04:19] yep, but in my experience new upstream releases of low-risk packages [04:19] Or when we do backport risky stuff, we do actually test it a lot before putting it in. [04:19] Backports is often more tested than Proposed, but generally less tested than Updates. [04:20] proposed is supposed to be the staging area for updates afaik [04:20] Right. [04:20] And sometimes stuff gets in there with very, very little testing. [04:20] Which is why very few people should run -proposed. [04:20] right, there's no real check on what goes in to -proposed other than pitti's quick check [04:21] do you have examples of little tested things that hit proposed? [04:21] I sense that this is turning into that ML thread. [04:22] i thought the point of proposed was to do testing [04:23] jcastro: We had a bad svn regression in -proposed that I recall. [04:23] i mean, the uploader should test yeah, but...if it was perfectly tested before upload, we wouldnt need proposed [04:23] MsMaco, yeah but in some cases (like hardware stuff) there's only some testing an uploader can do [04:23] * ScottK recalls a MOTU who was unaware udpates should be tested before uploading to proposed. [04:24] I asked him how to test the fix and the response I got was, "I don't know". [04:24] b/i/r in pre... oh wait wrong process [04:24] jcastro: right so...proposed is for testing... [04:24] im confused by whats surprising about that [04:24] Which is why you should just install stuff from it you plan to test, IMO. [04:25] ok i should just shush since im obviously the weird one in this bunch [04:26] I don't think it's weird [04:26] if i run stable, its with proposed enabled. though i rarely run stable. [04:26] "production" system or not [04:27] (read "production" as "the only computer i have") [04:27] well IMO if you install a package from -proposed, it should be to contribute to the verification process [04:29] The theory last time we went around on this was more peole just running proposed would increase the odds of catching an odd regression. [04:30] there were a few odd evolution regressions on hardy-proposed, i remember [04:31] it worked the way it was supposed to? :) === vorian is now known as v === v is now known as vorian === jdong_ is now known as jdong === ArneGoet1e is now known as ArneGoetje [06:53] pitti: You might want to copy jaunty-updates' tzdata to karmic-updates and lucid. We're seeing a few people confused by bug #467165. [06:53] Launchpad bug 467165 in tzdata "karmic version is lower then jaunty-updates" [Undecided,New] https://launchpad.net/bugs/467165 [07:27] good morning [07:36] Hmm...am I supposed to be poking somebody to get lilo-installer accepted into hardy-proposed? [07:44] Morning Daniel [07:44] hi stooj [07:45] I feel sorry for you - 9.10 is awesome, and you have to move straight on to Lucid already! [07:45] But Slashdot and The Register say that 9.10 sucks. They must be right. [07:46] Grr @ elReg: "60% of people hate Karmic in a poll on ubuntuforums" == News [07:47] Yup. [07:50] stooj: karmic development slowed down a lot in the last weeks, so some of us got a bit of a break :) [07:51] Glad to hear it [07:51] Going home - later all [08:07] well they say there's no such thing as bad publicity [08:08] hi guys.. i'm manipulating init scripts on my machine - I want service 1 to be stopped only AFTER service 2 is stopped. Do I use "Should-Stop 2" for this ? === dholbach_ is now known as dholbach [08:17] apw: Hello, any news about this bug #446146? [08:17] Launchpad bug 446146 in linux "Several Huawei USB dongle don't work with kernel 2.6.31-12.40" [Medium,Fix committed] https://launchpad.net/bugs/446146 [08:17] hello sabdfl [08:50] primes2h, the fix for that is committed and will be rolled out in the first kernel SRU which is expected pretty soon. likely thursday currently [09:01] Good morning [09:03] wgrant: ah, because of the +repack thing [09:03] wgrant: yeah, will do; thanks [09:03] pitti: Thanks. [09:04] wgrant: ah, no, can't do; the packaging changed slightly, and it would be a regression to move the jaunty one to karmic [09:05] wgrant: what I'll do instead is to update the entire squad to 2009q, which was just released [09:05] pitti: Even better. === Tonio__ is now known as Tonio_ [09:16] apw: Oh, that's nice. At least users would stop changing status to "fix released" on their own. ;) [09:59] pitti: you marked bug #441638 as assigned to you; still working on it? it seems there are a fair number of users for whom having bulletproof-X available would be a particular help right after upgrade [09:59] Launchpad bug 441638 in gdm "upstart job keeps restarting a dying gdm" [High,In progress] https://launchpad.net/bugs/441638 [10:00] it's still on my list; although I didn't really intend to implement bulletproof X, just to stop the eternal auto-respawning [10:00] but if someone else wants to beat me to it, be my guest, of course :) [10:01] pitti: ah - then per https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/441638/comments/20, I'll take it if you won't [10:01] Ubuntu bug 441638 in gdm "upstart job keeps restarting a dying gdm" [High,In progress] [10:02] oh, thank you [10:08] siretart: hum, your cryptsetup apport hook change makes the package ftbfs in bzr [10:09] siretart: though I have yet to figure out why [10:10] slangasek: I thought keybuk uncommitted it? - anyway, I think there is just a 'mkdir' missing in debian/rules [10:10] well, or an entry missing from debian/dirs [10:10] (though why does this package not use dh_install, sigh) [10:10] ah, right. that'd be easier [10:10] anyway, no, not uncommittd === akgraner_ is now known as akgraner [11:22] superm1, ping? (I'd like to talk to you about recovery partitions if you have a moment soonish) === agateau is now known as agateau|lunch === thegodfather is now known as fabbione === ogra_ is now known as ogra [13:03] Could someone rescore https://launchpad.net/~laney/+archive/ppa/+build/1319012 for me, pretty please? [13:05] (testing an ftbfs fix for lucid) [13:12] never mind, someone else did it :) [13:13] cjwatson: could we have http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.lucid ? === agateau|lunch is now known as agateau [13:32] do we know when autosyncs should start? they are blocked on source format changes too? [13:32] doko, is the gcc in the archive already using ARMv7 and thumb2 ? or is that only the one in your ppa ? [13:32] seb128: The autosyncer will crash at the moment due to the new source formats. [13:32] seb128: the autosyncer is currently pointing at unstable [13:33] that will be fixed in the LP rollout scheduled for tomorrow morning I believe [13:33] is there anything stopping me to sync the desktop things I want if they are in good old source format still? [13:33] seb128: I have a LP branch waiting for RC approval which will stop it from crashing, however it will not be able to sync v3 packages until somebody from the distro world convinces LP that it is important. [13:33] seb128: no, that works fine [13:33] specific syncs in the old format are fine as far as I know [13:33] ok thanks [13:33] That will work fine, right. [13:33] I did several syncs and they work well [13:34] I just wanting to make sure before stepping where I should not ;-) [13:34] seb128: if Soyuz breaks, we'll blame you :) [13:34] I knew it! [13:34] ;-) [13:36] slangasek: is the ext4 corruption bug already fixed? LP says no so I'm wondering if it's the same issue linus closed with new -rc kernel. http://lkml.org/lkml/2009/11/3/377 === ingenius1 is now known as ingenius === marjomercado is now known as marjo [14:16] james_w: if some package branch is not available, does it make sense to report it as a bug, nag you on irc, or should I rather ignore it and just merge the package it in the "traditional" way? [14:20] does anyone know why ppa builds are taking so long ? https://launchpad.net/~smoser/+archive/ppa/+build/1318926 has been uploaded for 17 hours, it is to "start in 9 hours" [14:21] smoser: Look at the number of actively PPA buildds currently. [14:22] apparently they were taken out to be release mirrors [14:24] ScottK, where is that info? [14:25] ah. [14:25] but, just wondering, where can you see that? [14:25] smoser: https://launchpad.net/builders/ [14:26] siretart`: yes, yes and yes :-) [14:26] I'm still somewhat surprised that computing power is the bottleneck rather than bandwidth :) [14:26] thanks ScottK . [14:27] if you want me to take a look then I will, but it is often more than a 5 minute thing, so if it is urgent doing it another way would probably be wise [14:28] no, it is not urgent. I'm just experimenting with merging package with bzr and I am making great experiences [14:28] more wondering, if "Architecture: all" then it gets built on i386 ? [14:29] smoser: Yes [14:37] mathiaz: A few months ago, you reported a set of unused dependencies in the SSSD. I didn't have time to look into them until now. I saw that you guys pulled in 0.7.1 recently. Would it be possible for you to point me to the build log, so I can see the set of unused dependencies? [14:37] /set/updated set/ [14:38] sgallagh: sssd is still at 0.5.0 in the developement version (lucid) [14:38] sgallagh: there is a bug to update it to 0.7.1 though [14:39] mathiaz: Oh ok, so it hasn't been run yet. I was just trying to get the updated set of dependencies so I can fix them all in one go. [14:42] sgallagh: ok - I'll try to get a test build run [14:42] sgallagh: and file a bug report about it [14:44] mathiaz: That would be fantastic. Thank you. === dendrobates is now known as dendro-afk === dendro-afk is now known as dendrobates [14:55] pitti: I've done a bunch of upgrade tests and I can't reproduce the issues people are having with the kernel being the jaunty one. Also only issue I did come across was one on audio where the gfx card has hdmi out. But once I'd told pulse which card to use and unmuted it was fine. [14:56] davmor2: thanks; perhaps it's related to using apt-get dist-upgrade? [14:56] pitti: I can run one and see for you if you want? [14:57] if you want, would be interesting to see if we have a bug there; but it should all be covered by the metapackages, I'd think? [14:57] davmor2: it wouldn't work if they removed the linux meta packages, of course [14:58] the upgrader will take care of a linux meta-package automatically, only apt-get users can be hit by that [14:59] I'll try an apt-get upgrade and see how it does [14:59] dist-upgrade even [15:02] davmor2: thank you! [15:03] kees: online? === Sp4rKy is now known as Guest37492 === Guest37492 is now known as Sp4rKy === Sp4rKy is now known as Guest30894 [15:10] doko: I am now, hi! [15:20] pitti: oops, forgot about that. It'll generate next time the cron job fires [15:20] doko, could you unbreak python in lucid too for the -lssl issue? [15:20] cjwatson: thanks [15:21] seb128: no, please fix the apps [15:21] doko, there is a ton to do, could you be help having smooth transitions? [15:22] doko, that breaks a good part of GNOME [15:22] and I will not be able to look at those before uds [15:22] it's not breaking a running a system, so we should fix these during merges [15:22] between vac, travelling and sprint next week [15:23] I don't know how to fix those [15:23] could you send patches please? [15:24] doko, I guess I will just add libssl depends everywhere for now [15:24] not this week, and maybe not next week. if such a package is on my merge list, I'll fix it of course [15:24] seb128: don't do that, the bug report is concise about the exact fix [15:25] doko, could be clear to you but it's not to me and I said I don't want to get things blocked until after uds [15:25] seb128: what exactly is unclear? [15:25] the same packages is working in debian and those build fine in any other distro [15:26] I've no time to deal with autotools changes and convincing upstream of why ubuntu need that now [15:26] seb128: no, it's not in experimental [15:26] it's a compatibility breakage on your side imho [15:26] but whatever I don't want to argue now [15:27] I will add the depends so I get things to build [15:27] thanks [15:27] Riddell, pitti, you have scheduling powers in the summit system now [15:27] jcastro: thanks [15:27] jcastro: rickspencer3 as well? [15:27] yep === akgraner_ is now known as akgraner [15:32] seb128: I'm a bit pissed about your attitude to work around a known bug; it'll just be extra work later in the cycle [15:35] * Riddell feels the power [15:36] doko, looks like a compatibility breakage on your side and not a known bug to me but I don't think arguing will bring you somewhere [15:36] doko, so let's agree to disagree [15:36] seb128: no, it has nothing to do about "compatibility" [15:36] doko, the python package should not those public if they are not meant to be used and if they are public you should install enough to get it working [15:36] what is the actual issue? [15:36] it's like shipping a .pc and saying to not use it [15:37] pitti, some python flag bringing -lssl without depends on libssl-dev [15:37] pitti, let me look again to the exact build failure [15:39] pitti, /usr/lib/python2.6/config/Makefile: LOCALMODLIBS= -lssl -lcrypto -lssl -lcrypto -L$(exec_prefix)/lib -lz [15:40] pitti, that is shipping with python2.6 [15:40] and GNOME softwares use it [15:40] but python doesn't have the depends corresponding to the -l [15:41] seb128, doko: are LOCALMODLIBS meant to get linked to external softare? [15:41] it is wrong that an extension links with LOCALMODLIBS [15:41] what should be used instead? [15:41] I just feel that I understand the issue enough to argue upstream or open a bug there [15:41] +don't [15:42] can't we just stop the affected packages from including LOCALMODLIBS into their linkage list? [15:42] that would also avoid extra dependencies and make transitions easier [15:42] don't use LOCALMODLIBS at all [15:42] why did they start using it in the first place? [15:43] the jaunty and karmic behaviour always links these libs with -lz, which is wrong as well. just by chance, or because zlib-dev is installed, lets you get away with it [15:44] ok, let me try to just drop that from the configure [15:44] what was the bug number? [15:45] do you have any pointer saying why those should be used to use for upstream bug reference? [15:45] doko, bug #450355 [15:45] Launchpad bug 450355 in totem "python extensions must not link with LOCALMODLIBS" [High,Triaged] https://launchpad.net/bugs/450355 [16:03] seb128: at least for rhythmbox this is code which pre-dates distutils (i.e. python1.5). upstream is removing more and more of this old build stuff in every release, so an application/extension shouldn't rely on it. This code in gnome is really, really old. either distutils should be used, or at least python-config [16:05] PYTHON_CFLAGS="-I$PY_PREFIX/include/python$PYTHON_VERSION" [16:05] PYTHON_LOCALMODLIBS=`sed -n -e 's/^LOCALMODLIBS=$.*$/\1/p' $PYTHON_MAKEFILE` [16:05] PYTHON_BASEMODLIBS=`sed -n -e 's/^BASEMODLIBS=$.*$/\1/p' $PYTHON_MAKEFILE` [16:05] PYTHON_OTHER_LIBS=`sed -n -e 's/^LIBS=$.*$/\1/p' $PYTHON_MAKEFILE` [16:05] PYTHON_EXTRA_LIBS="$PYTHON_LOCALMODLIBS $PYTHON_BASEMODLIBS $PYTHON_OTHER_LIBS" [16:07] pitti, seb128: for a quick fix, just remove the lines about PYTHON_LOCALMODLIBS and PYTHON_BASEMODLIBS. PYTHON-CFLAGS should use the output of python-config --includes to pick up the correct headers for debug builds, but apparently is not necessary in that package [16:08] anyway, afk now [16:23] doko, ok thanks [16:41] doko: word reaches me that gdb 7.0 is broken for c++, do you know anything about it? [16:41] http://lists.trolltech.com/pipermail/qt-creator/2009-November/004963.html [16:41] pitti: apt-get dist-upgrade seems to be correct just confirming now [16:41] ScottK: what does your backports hat say to having a gdb-6.8 in backports and having qt-sdk depend on that? [16:41] pitti: it is in fact correct [16:43] Riddell: I don't understand. We already have 7.0 in Karmic? [16:44] ScottK: and I'm told it's broken [16:44] for c++ [16:45] Riddell: So you're thinking introduce a new gdb-6.8 package? [16:45] ScottK: yes [16:45] If so, I'd say get it into Lucid and a backport of a new package is no problem at all. [16:46] doko: got an opinion on that? [16:46] It might not be a bad idea to have a non-broken with C++ gdb in the development series either. [16:56] pitti: anything else you'd like me to try? === asac_ is now known as asac [17:03] davmor2: thanks; so I guess it's a customized /boot/grub/menu.list or something such [17:03] pitti: it certainly sounds it, that or a modded kernel [17:14] soren: is there a vmbuilder somewhere that let's me build a lucid vm? [17:14] soren: hi btw! [17:21] I've been having trouble with a segfault in libc since one of the Karmic beta releases and it has continued even on a fresh install of the official karmic release. [17:21] It appears to be related to catgets, now I'm not sure if it has anything to do with localization files somehow. === deryck is now known as deryck[lunch] [17:24] I know that's what catgets/catopen is used for. When javac segfaults: [17:24] or java, rather [17:24] # C [libc.so.6+0x31b08] catgets+0x18 [17:24] I'm having trouble with both swing apps and some SDL apps, but specifically *all* java swing apps and the fancy-terminal tilda. === Tarbo is now known as Guest58289 [17:37] I can't seem to recreate the segfault by simply exercising catgets() [17:47] robbiew: hi - are there any guidelines for naming blueprints for lucid uds? [17:47] robbiew: for karmic we used to have karmic-$track-foo as a template [17:48] robbiew: has this changed for Lucid UDS? [17:48] not that I know of [17:48] as long as you are consistent [17:49] it really doesn't matter [17:49] just helps with finding the blueprints quickly for scheduling [18:02] robbiew, is mvo's reply enough info for you to schedule UDS sessions on Ubuntu Software Center stuff? [18:03] yeah...I'll be doing the scheduling [18:03] this week [18:03] ok, thanks [18:18] sebner: no, it's completely unrelated to the problem Linus is seeing in 2.6.32. [18:19] slangasek: oh, I'm sorry than [18:34] https://bugs.launchpad.net/bugs/458549 <--- most entertaining bug report in a while [18:35] Ubuntu bug 458549 in ecryptfs "One Tin Platter (The Legend of Davey Jack)" [Critical,Incomplete] === ryu2 is now known as ryu [18:52] Unfortunately merge-o-matic is down due to Debian's change of source package format. [18:52] anyone knows for how long? unfortunately the PTS mails me every 6 hours when http://patches.ubuntu.com/PATCHES can't be downloaded [18:53] slangasek: ^ (ping someone random that I know :)) [18:53] buxy: until someone can update the merge-o-matic code to cope with the new packages; I think next week at the earliest [18:54] buxy: It's actually down due to Ubuntu not planning for the new source format. Debian didn't do this by suprise. === deryck[lunch] is now known as deryck === dpm is now known as dpm-afk === dendrobates is now known as dendro-afk [19:09] ScottK: bear in mind you are speaking to someone that is intimately familiar with how Debian did it ;-) [19:11] heh :) [19:21] pitti: hi there [19:21] pitti: around? procedure question for you [19:21] pitti: order of operations, really === dendro-afk is now known as dendrobates [19:35] sgallagh: hi - the current code in sssd trunk is supposed to be named 0.7.2 or 0.8.0? [19:35] sgallagh: making sure to have the right upstream version number in the snapshot I'm preparing [19:40] mathiaz: okay, i have *fixed* https://bugs.edge.launchpad.net/ubuntu/+source/kvm/+bug/404394 :-) [19:40] Ubuntu bug 404394 in kvm "qcow2 corruption regression" [High,In progress] [19:40] mathiaz: i just uploaded to -proposed for SRU ification [19:40] mathiaz: i also uploaded the fix to hardy-backports and intrepid-backports, as it needs to be fixed there too [19:40] kirkland: as in: a SRU for -backports? [19:41] mathiaz: right, sort of [19:41] kirkland: out of curiosity - do you plan to do a backport of karmic kvm to hardy? [19:41] bugfix on top of backports (tm) :) [19:41] mathiaz: no [19:41] kirkland: virtio doesn't work on hardy host + karmic guests [19:41] mathiaz: the kvm-84 backport took a *lot* of effort [19:41] kirkland: agreed. [19:41] mathiaz: how so? [19:41] mathiaz: i think this new upload might fix that for you... [19:42] mathiaz: you want a ppa package to test? [19:44] kirkland: hm - I don't find the bug right now :/ [19:44] kirkland: it had to do with disk errors [19:44] mathiaz: that's this [19:44] kirkland: you'd see them in the guest - like I/O errors [19:44] mathiaz: right [19:44] kirkland: ok - then it's good news :) [19:44] mathiaz: i believe this upload fixes your problem [19:44] mathiaz: you want to grab the patch and test, or you want a ppa build? [19:45] mathiaz: ppa build will take a while [19:45] kirkland: it will cut down iso testing from 4 hours to 2 h and 42 minutes [19:45] kirkland: I can wait for the PPA build [19:45] mathiaz: https://bugs.edge.launchpad.net/ubuntu/+source/kvm/+bug/404394/comments/16 [19:45] Ubuntu bug 404394 in kvm "qcow2 corruption regression" [High,In progress] [19:45] mathiaz: that's the hardy patch [19:45] kirkland: ok - I may have a look at it later [19:54] mathiaz: is your hardy kvm server amd64 or i386 ? [19:54] kirkland: amd64 [20:00] hi NCommander, what's up? [20:01] considering the new gnome features (gnome shell and gnome zeitgeist) will come september 2010, is it possible that 10.10 will be a lts version instead of 10.04? [20:01] because mabye the old gnome wont be supported a long time [20:01] 10.04 wasnt going to get gnome 3 anyway [20:03] popey: outstanding blog post on upgrading [20:03] thanks kirkland [20:06] popey++ [20:07] MsMaco: ah ok, because it might be to unstable? [20:07] like kde 4.0 [20:08] i guess so [20:08] lessons learned? [20:08] james_w: did you know why lp:ubuntu/hardy-security/firefox-3.0 is firefox 3.0.14 and not 3.0.15? [20:08] i mean the branch [20:08] james_w: isn't it updated automagically after upload? [20:08] yes [20:09] I've been working out some kinks that meant it sometimes fell over though === dendrobates is now known as dendro-afk [20:12] james_w: mm, so i just need to wait? [20:12] james_w: it has been 2 days [20:14] nxvl: forced a check of that package [20:15] james_w: thank you [20:16] nxvl: damn [20:16] hit a bzr bug [20:16] let me see if I can do anything about that [20:16] james_w: my problem isn't exactly now [20:17] james_w: i'm already late and doing some workarounds to make it work, so don't worry [20:17] james_w: what i'm worried is about it becaming my primary process [20:17] james_w: maybe we can discuss this better at UDS [20:17] yes [20:18] mathiaz: build done -> https://edge.launchpad.net/~kirkland/+archive/ppa/+build/1320609 [20:18]