[05:55] Hi, I am planning to create a custom Amazon image from Ubuntu Minimal CD. [05:56] After going through a few forums, I am under the impression that the kernel needs to have certain modules compiled, so that it runs in Amzon EC2. [05:57] Is the kernel in the Ubuntu Minimal CD, capable of runningin an Amazon EC2 instance? [06:13] Is the regular Ubuntu kernel capable of running in an Amazon EC2 instance? === smb` is now known as smb [07:23] hashken, It varies depending on release. But in general all of them should. The only thing to check is whether xen-blkfront is built in or that the module is requested to be in the initrd. [07:27] hashken, If you pull in the linux-virtual meta-package that gives you the same kernel as in the cloud-images. [07:43] thanks smb === apachelogger_ is now known as apachelogger [07:48] * apw yawns ... [07:48] it is very hot here [07:49] apw: How are the bees finding it? [07:49] They probably have been replaced by real-fire flies [07:49] if they have any sense they are in the cup, hiding from the sun [07:50] smb, turned into by the sun more like [07:52] apw, You should get rid of that sun thing completely. [07:55] The Daystar? [07:57] Just place a huge solar panel over the UK... above cloud level so they can enjoy their rain still [07:57] smb, good plan === fmasi_afk is now known as fmasi [08:14] * apw hs being promised some rain over the next two days, thats something === fmasi is now known as fmasi_afk === fmasi_afk is now known as fmasi [08:56] is this verification testing week for the -proposed kernels? [09:08] "14-Jul - 20-Jul Bug verification." (from the email everyone gets) === fmasi is now known as fmasi_afk === fmasi_afk is now known as fmasi [09:16] Can we get https://wiki.ubuntu.com/Kernel/LTSEnablementStack linked from https://wiki.ubuntu.com/Kernel/FAQ somewhere? === Guest46086 is now known as jpds [12:34] I've rebased saucy against v3.10.1 and ready to push. are you still looking at those arm dtb patches ? [12:34] apw, ^^ [13:03] rtg, i have them applied here indeed, but push away and i'll sort it out [13:03] are you gonna worry about 3.10 ? or just do it for 3.11 ? [13:04] i was assuming i'd apply them to both once i had build tested them on both [13:04] they seem sane if my chat with infinity is anytyhing to go by [13:04] ok [13:06] Oh dear. I shouldn't be the yard stick for sanity. [13:06] apw, saucy pushed. still testing armhf build, but I expect it to be OK [13:07] infinity, hey i am comparing to me === cmagina-away is now known as cmagina [13:24] rtg, don't we have a per kernel directory already [13:24] apw, for firmware in the kernel package [13:24] for firmware, could we perhaps drop the linux-firmware-lts contents into those as if they were part of the kernel [13:24] but each one is ABI specific [13:24] bah [13:25] apw, sounds like a sprint topic [13:25] yeah shove it in, a plan indeed [13:25] as we'll have infinity to poke too [13:26] apw, lemme know when you've pushed those arm patches. everything else is ready to go. [13:26] rtg ack, just checking the udebs builds [13:32] apw, pushed saucy unstable rebase onto v3.11-rc1 [13:37] rtg, ack [13:37] not far behind, just rebased and doing final checks [13:37] missing some ?'s which i've added and fingers crossed [13:53] ogasawara, apw, there is a first iteration of dkms testing ready for review http://10.98.0.1:8080/view/DKMS/view/All/ [13:53] It covers precise, precise+hwe kernels, saucy+proposed, saucy+prerelease ppa [13:53] This a build/install test but I disabled modprobing for the moment. [13:54] ogasawara, Could your team review the results, then we can schedule a call ? [13:54] jibel: awesome, thanks! yes, we'll review. lets go ahead and schedule a call on the calendar for later this week? [13:55] ogasawara, this week is fine, I'll let you schedule it, your time will be mine. [13:55] jibel: ack [14:13] rtg, ok i also need to fix linux-signed before you do your do on this one [14:14] apw, no problem, am pursuing an __udivdi3 issue on unstable i386 === fmasi is now known as fmasi_afk [14:46] rtg, ok saucy master-next is pushed, off to un-f*ck -signed [14:46] apw, ack === fmasi_afk is now known as fmasi [15:07] rtg, ok i have pushed signed, but once you have linux in the pipe for upload i would like to do the update to ensure the update-versions is going to handle this situation, we have never had to test this before [15:07] (do the update for linux-signed) [15:08] apw, If you want, then go ahead and package saucy master-next. I'm still messing with unstable. [15:08] (and upload) [15:09] rtg ok will do [15:10] rtg, you did a rebase on this right ? [15:10] yeah, to v3.10.1 [15:10] i don't see it in the changelog [15:10] apw, oh shit, forgot [15:10] did you miss it (then i can add it) or do i have the wrong brnach [15:10] if you missed it i can retrofit for you [15:11] apw, yeah, go ahead and run insert-mainline-changes [15:11] will do === rtg is now known as rtg-afk === fmasi is now known as fmasi_afk === fmasi_afk is now known as fmasi [16:14] * _bjf -> dr. appt. === _bjf is now known as bjf === fmasi is now known as fmasi_afk [16:15] bjf - i noticed a couple of the kernels went to confirmed today, that doesn't imply a change in schedule does it? [16:16] bjf, the raring and quantal backports kernels were the ones === chrisccoulson_ is now known as chrisccoulson === fmasi_afk is now known as fmasi [17:14] brendand, those normally lag don't they, as in wait on their parent branches to build before being done (but i'll let bjf say for sure) [17:16] apw, i would have expected then for the raring and quantal proposed kernels to be confirmed prior then, rather than the other way around [17:18] sbeattie: We are seeing https://jenkins.qa.ubuntu.com/view/All/job/sru_kernel-quantal_lts_hwe-generic_i386-intel_64-mga_g200ew/39/testReport/junit/autotest/ubuntu_qrt_apparmor/test_apparmor_py/ in regression testing. [17:19] sbeattie: guess you are the one to talk to? [17:20] psivaa, if it is apparmor i expect jjohansen will be interested as well [17:20] apw: ack, thanks :) [17:23] psivaa: thanks, this regression is known about and temporary [17:23] psivaa: its due to work item scheduling [17:24] jjohansen, so we'll get some more bits in the mail :) [17:24] apw: oh yes, there will be at least two more syncs [17:25] jjohansen, thanks [17:26] * bjf -> back [17:27] brendand, would be nice if you'd have stuck around :-( [17:27] jjohansen: ack, not sure what i should do with the workflow task, (fix-release with qa-testing-passed ?) [17:30] psivaa: err just a sec, this is the quantal backport? [17:30] jjohansen: yes [17:31] psivaa: on i386? [17:32] jjohansen: yes, on amd64 hardware i think [17:32] psivaa: sorry ignore what I said before, this just looks like a known bug. It is not. The quantal backport should be good here [17:33] psivaa: okay, we will poke at it [17:33] jjohansen: ack, ill report a bug then [17:33] sbeattie: we have a regression on the quantal backport to investigate [17:35] jjohansen: looking at that output, it seems to be the tcp tests that failed? [17:35] sbeattie: yep [17:54] jjohansen: sbeattie: reported bug #1201530 for the above failure. [17:54] Launchpad bug 1201530 in ubuntu-kernel-tests "Failure in apparmor tests with quantal lts-hwe 3.5.0-37.58~precise1-generic 3.5.7.16" [Undecided,New] https://launchpad.net/bugs/1201530 [17:54] psivaa: okay, thanks [17:57] * sbeattie is trying to reproduce the issue === rtg-afk is now known as rtg === fmasi is now known as fmasi_afk === cmagina is now known as cmagina-away [19:51] apw, pushed Ubuntu-3.10.0-3.12 on to saucy master [19:51] rtg, how is it i keep forgetting to do that, spack [19:51] apw, I didn't notice until I went to do the LTS version === cmagina-away is now known as cmagina === cmagina is now known as cmagina-away === cmagina-away is now known as cmagina [21:30] * rtg -> EOD