/srv/irclogs.ubuntu.com/2013/11/20/#ubuntu-uds-core-2.txt

=== ChanServ changed the topic of #ubuntu-uds-core-2 to: Currently no events are active in this room - http://summit.ubuntu.com/uds-1311/core-2/ - http://irclogs.ubuntu.com/2013/11/20/%23ubuntu-uds-core-2.html
=== ChanServ changed the topic of #ubuntu-uds-core-2 to: Track: Core | Improve the cross-compilation story for Ubuntu Touch by 14.04 | Url: http://summit.ubuntu.com/uds-1311/meeting/21991/core-1311-cross-compilation/
slangasekhttps://plus.google.com/hangouts/_/7ecpj1uhgvnl346mfisfouopu013:58
dholbachdid anyone press the "go live" button already? :)14:02
slangasekno14:02
apwfeels like not here14:02
slangasekwe're missing doko, trying to decide if it's worth having the session for :)14:02
pittislangasek: he pinged me half an hour ago, he's on crappy mobile network14:02
slangasekok14:02
pittinot good enough for hangouts14:03
slangaseknot even audio?14:03
pittiI don't know14:03
pittihe said "let's see.."14:03
apwslangasek, we can see you14:05
pmcgowanhear you14:05
Saviq\o/14:05
pbasswe see you14:05
* xnox runs off to find my 2fa token.14:06
dokoslangasek, I'm online, lets see how this works out ...14:06
slangasekdoko: ok - https://plus.google.com/hangouts/_/7ecpj1uhgvnl346mfisfouopu0 if you can; I was looking to see if we could call you to bridge you in, but hangouts have hidden the button again14:07
apwxnox, is there any reason mako cannot use v4.6 as well if that is what is upstream14:10
apwxnox, we probabally only use that because v4.8 didn't work, and v4.7 did14:10
cjwatsonThere's already a 4.7 cross stack in the archive, so no reason to take that backward14:11
apwok14:11
cjwatsongcc-4.7-arm-linux-gnueabihf - GNU C compiler14:11
asacdo we know why they kept going with 4.6 on kernels?14:12
asac(dont need to address in hangout, just question for channel)14:12
xnoxasac: e.g. goldfish gives kernel panic before it completes boot, when compiled with 4.7 or 4.8.14:12
ogra_i think maguro too14:13
asacright. but i am sure google could have fixed that easily if there were no other reasons for staying on 4.614:13
apwslangasek, can you add a WI for me to make that switch where needed14:13
xnoxat the moment: all nexus kernels use 4.6, mako uses 4.7.14:13
xnoxapw: done.14:13
asace.g. i believe there might be good reasons... in particular if they use 4.7 for the userspace14:13
slangasekapw: which switch? to libiberty14:13
asacxnox: do they use 4.7 in userspace? or even 4.4?14:13
ogra_asac, 4.614:14
xnoxasac: haven't checked recently, I believe there was a newer toolchain for kitkat, in user-space only.14:14
xnoxasac: pre-kitkat is 4.614:14
cjwatsondoko: (repeating from the hangout) binutils-dev already ships libiberty.a, so I don't quite get how it's an extra maintenance burden to just ship that as a separate binary package instead rather than duplicating the source - I guess I'm missing something?14:14
asaccjwatson: slangasek: talking about cross compiling kernels... any thoughts about allowing to cross compile kernels in PPAs?14:14
ogra_asac, for what ? to save 20min ?14:15
loolwhy dont I get a live stream of this session14:15
cjwatsonCross-PPA support is interesting - the trick is (maybe) limiting it to only things that would actually work so that people don't get a profoundly disappointing experience14:15
asacright14:15
ogra_lool, i do14:15
loolodd14:15
cjwatsonMy thoughts on this to date have been that it's better to focus on expanding the scope of things that we can cross-build so that it's less disappointing14:15
loolmaybe I have too many streams open14:16
dokois there a way to turn off video in hangouts?14:16
cjwatsonyes, there's a camera icon at the top that you can click14:16
ogra_doko, click the camera icon14:16
cjwatsonor do you mean everyone else's video?14:16
dokothe latter14:16
pittiturn bandwith usage down14:16
ogra_yeah14:16
asaclool: your computer doesnt like anything related to video streams... no hangouts, no yuoutube :)14:16
pittiin the "signal strenght" like slider14:16
asacetc.14:16
ogra_cjwatson, cant highbank do proper virtualization ? i thought it could ... i would rather see all PPAs get faster than having a list of püackages that can cross build in a PPA14:17
loolasac: :-)  actually it was due to too many streams open (was trying to follow two other sessions)14:21
* asac wonders how lool can listen to multiple streams14:21
asaci can imagine two ... one for each ear14:21
asaceverything else must also be hard for you to process14:21
asachehe14:21
ogra_asac, 5:1 dolby surround ...14:22
ogra_6 channels ;)14:22
cjwatsonogra_: I don't think highbank can, I think we're waiting for next-gen (A57 or similar)14:22
ogra_ah, ok14:22
ogra_i still think we should wait14:22
ogra_instead of having to maintain an artificially made up list14:22
loolasac: mute everything and listen i n2 minutes chunks  :-)14:23
rsalvetixnox: I believe kitkat should be using 4.7/4.814:23
cjwatsonI indeed don't think that a whitelist (or even blacklist) is a scaleable approach14:23
rsalvetibut the kernel is still using that very old toolchain14:23
ogra_rsalveti, even the N5 one ?14:24
rsalvetiogra_: sorry, was thinking about the goldfish target (the one requiring 4.6)14:27
ogra_ah, good14:27
ogra_would be odd if hammerhead still used such an old kernel14:27
pmcgowansounds good14:32
mzanettiI think app development would be mostly qmake14:36
apwdid we just lose the feed, or si that me14:36
mzanettiapw: works here14:36
mardyand QBS! :-)14:37
sergiusensshouldn't the sdk should default to cmake for ubutnu touch projects?14:37
mzanettithing is, qtcreator generates everything qmake for you. cmake is completely manually14:37
cjwatsonqtcreator's under our control, at least partially14:38
apwfirefox crashage, yay ...14:38
mzanetticjwatson: well, we could extend qtcreator to properly support cmake, which sounds a lot to me tbh14:38
mzanettifine with me personally. but it's more complex for app developers.14:39
cjwatsonIt might be more complex for the SDK team14:39
slangasekright14:40
cjwatsonIt should surely be invisible to app developers14:40
slangasekthe SDK should DTRT14:40
mardyfor app development QBS is easier, and it's probably going to be the build system better supported by QtCreator in the long term14:40
cjwatson(Unless they poke around at their build system)14:40
mzanetticjwatson: no. it's never completely visible to the developer.14:40
cjwatsonIs qmake == QBS?14:40
mzanettierr. completely invisible14:40
mzanettiQBS == QMake Build System14:40
mzanettithe new thing to come soonish14:40
mardycjwatson: no, it's a new stuff, with a JSON/QML-like syntax14:40
mzanettierr.. QML Build system14:41
cjwatsonWell, the reality is that right now we know how to make cmake support cross-building and we know that there are significant difficulties with qmake14:41
cjwatsonLong-term I'd like to have all build systems cross-build-capable, but there's the matter of which we can do first14:41
Saviqhttps://bugreports.qt-project.org/browse/QTBUG-2998714:41
mardycjwatson: makes sense14:41
cjwatson(And upstream cross-build-capability isn't necessarily the same as it working properly for Ubuntu - non-multiarch cross-building can be significantly different if done badly)14:42
dholbach(qt4) and checkbox I think, but AFAIK that's being rewritten14:45
Saviqqbs == Qt Build Suite apparently14:46
Saviqhttp://qt-project.org/doc/qbs-1.1/index.html14:46
mardycjwatson: but not all the stack is built with cmake14:49
loolcjwatson: and similarly we should start by cross-compiling the clicks that we include I guess14:49
cjwatsonmardy: not all the stack is built with any one system :-)14:49
cjwatsonmardy: so yes, I expect that fixing the whole stack will involve fixing multiple build systems14:50
cjwatsonlool: perhaps, yeah14:50
mardycjwatson: yep :-)14:50
loolsergiusens: ^ FYI on cross-compilation topic, we're thinking of testing/dogfooding the cross-compilation story with the builds of the preinstalled click14:50
lools14:50
cjwatsonwhich of those are arch-dep right now?14:51
loolat the moment we pull some prebuilt files from .debs14:51
loolso the actual builds are not arch-specific, except for the armhf debs they download14:51
mzanettio/14:52
sergiusenscjwatson, lool notes-app is the only one building that way14:52
sergiusensit's cmake based14:52
loolgreat14:52
=== ChanServ changed the topic of #ubuntu-uds-core-2 to: Track: Core | Upstart Roadmap for 14.04 LTS release | Url: http://summit.ubuntu.com/uds-1311/meeting/21977/core-1311-upstart-roadmap/
slangasekhttps://plus.google.com/hangouts/_/7acpj036tlifqsdqh2tcf8997015:04
slangasekjodh: ^^15:05
stgraberxnox: coming?15:08
zygalive15:09
* slangasek waves15:09
zygajodh: what are the small projects?15:09
* xnox o/15:10
slangasekhttps://plus.google.com/hangouts/_/7acpj036tlifqsdqh2tcf8997015:10
slangasekI'm gonna keep repeating that until people join ;)15:10
zygaslangasek: topic it15:11
zygawhat is the goal of using cgroups in upstart?15:11
xnoxzyga: resource control.15:12
slangasekzyga: just like we support ulimits / chroot primitives, we should support cgroups15:13
* zyga needs to learn more about cgroups15:14
apwwhy can we not move the process to the cgroups after, i thought you could shift runnign things15:16
apwand if we have upstart running we have enough disk to make the cgroup mamanger startable directly rather than via a job15:16
slangasekapw: what do you mean, "directly"?15:18
apwslangasek, fork/exec it directly before parsing jobs15:18
slangasekhmm15:19
apwso it is part of upstart, but not killing upstart if it explodes15:19
zygathere is one more case to consider, what it there are no cgroups at all (or they are disabled for any reason)15:20
zygathe way cgroups are tied to jobs starting needs to address that15:20
apwyeah what if the kernel has no cgroup support ...15:20
apwslangasek, ^^15:20
zygabut I agree that cgroup helper should be special so that state is consistent15:20
zygaand that there are no arbitrary periods of time after a jobi started before its cgroup profile is applied15:21
zygas/i / is /15:21
zygatime bridge would be fantastic15:22
zyga"start 10 minutes after system-booted"15:23
zygasystem-booted is just a job name15:23
marruslkilling stuck jobs. is that part of "refining ptrace handling" ?15:25
slangasekzyga: "arbitrary periods of time" - well, the only way to do that is to delay the boot until the cgroup manager is started15:25
slangasekmarrusl: yes15:25
marruslI am so happy.15:25
zygaslangasek: indeed15:26
zygaslangasek: my point is that that arbitrary period feels bad from a design perspective15:26
gQuigsand it would actually fix a bug that we don't know when to kill dbus which the X app exits over ssh15:26
gQuigsthis bug: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/59243415:28
udsbotuLaunchpad bug 592434 in dbus (Ubuntu) "ssh -X user@machine hangs when using exit to terminate" [Low,Triaged]15:28
gQuigsre: track user SSH sessions ^15:28
zygaslangasek: perhaps the alternative is to have a stanza that controls this15:28
zygaslangasek: so for most jobs, that would be immediate, and blocking15:28
zygaslangasek: but for certain early jobs we can relax that to 'when possible' and perhaps send some signal to communicate the fact (or tie that requirement to SIGSTOP support)15:29
zygaslangasek: like startup-SIGSTOP-cgroups-SIGCONT15:29
zyga^^ :D15:29
zygasocket bridge is not optional15:30
zygacgropus can or can not be available and the job should not differ15:30
* zyga might join the session but doesn't feel like a system level engineer to speak up really15:31
zygajodh, slangasek, stgraber: ^^15:33
slangasekzyga: please join ;)15:33
beidlit has to be special cased because it provides the infrastructure for jobs15:36
apwslangasek, i think i liked your statement there "it backs a stanza implementation"15:36
apw"start on using_stanza_cgroups"15:37
apwxnox, i think you want upstrart syntax for that  different words for optional and not15:39
apwcgroup <stuff>15:39
apwcgroup optional <stuff>15:39
mdeslaurit's not something we need, it's something we'd be interested in looking at if it was available15:50
gQuigswhy ever depend on having swap?15:53
apwjodh, could you do something like hte kernel does, and have the cgroup stanza actually start the job, like a modprobe for a protocol family in the kernel15:58
apwjodh, limits, can there not be a wrapper which applies those and used as an exec script prefix ?15:59
=== ChanServ changed the topic of #ubuntu-uds-core-2 to: Track: Core | Secure Boot work for 14.04 | Url: http://summit.ubuntu.com/uds-1311/meeting/21978/core-1311-secure-boot/
roadmroh that's today! yay16:02
cjwatsonHangout URL?16:05
cjwatson(Who's running the video?  slangasek I assume)16:05
slangasekhttps://plus.google.com/hangouts/_/72cpj2k5dn4bjr053d5ehn1lpo16:06
slangasekcjwatson: ^^16:06
apwdo we have a stream yet ?16:10
slangasekyes16:10
rtgnot that we can see16:10
slangasekhmm16:10
apwwhite space for me16:10
slangasekchecking16:11
slangasekoops, got the URLs backwards :P16:11
slangasekfixed16:11
apwslangasek, have it now16:12
slangasekalso, why are you people not joining the hangout ;)16:12
apwis there any kernel work :)16:12
rtghaven't combed my hair yet16:12
* apw has no hair16:12
cjwatsonthat's what video-off is for16:12
apw:)16:12
cjwatson(actually I just don't want to deal with bw awfulness)16:12
slangasekapw: do you want there to be?16:12
apwslangasek, i normally listen till it sounds like one needs kernel input16:13
josephtlower thirds please16:13
apw"sitting in the second row"16:13
smoserslangasek, link?16:38
apwslangasek, often to do with clocks yes16:55
slangasekhum16:55
apwslangasek, i don't thnk it was ubiquitus or anything16:55
rtgslangasek, yeah, that'll get important pretty quick16:55
apwstgraber, we will be interested in those, get us the bug #'s16:56
stgraberNov 12 12:58:48 castiana kernel: [213981.764426] Request for unknown module key 'Magrathea: Glacier signing key: f440a253eb498df923d438caa09b3b5d99308405' err -1116:56
apwslangasek, keys have valid date ranges on them, a bad system clock can break the key load16:56
rtgslangasek, certificate authority date is related to the clock (I think)16:56
slangasekapw: hmm; so I don't think that was the cause for me16:57
slangasek[    2.523405] video: module verification failed: signature and/or required key missing - tainting kernel16:57
slangasekthat's here on the most recent boot, and my system clock isn't dodgy16:58
apwslangasek, hmmm, yeah, i've added a WI to investigate them, if you could file a bug on that and get me the number, stgraber also16:58
apwslangasek, i can only assume it is an ordering issue, we boot too quick or something helpful16:59
rtgapw, there are plenty of bugs mentioning this problem. maybe jsalisbury would know one .16:59
stgraberslangasek: ah yeah, I see that one too16:59
apwrtg, good idea, will engage him16:59
stgraberslangasek: I'll file a bug16:59
slangasekstgraber: ta17:00
* apw bets you both use somethign which gets graphics into your initrd17:00
stgraberwe both use cryptsetup17:00
apwthat ... see17:00
apwi bet that is why i don't see it17:00
=== ChanServ changed the topic of #ubuntu-uds-core-2 to: Currently no events are active in this room - http://summit.ubuntu.com/uds-1311/core-2/ - http://irclogs.ubuntu.com/2013/11/20/%23ubuntu-uds-core-2.html
slangasekok17:01
stgraberhttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/125315517:07
udsbotuLaunchpad bug 1253155 in linux (Ubuntu) "Failure to validate module signature at boot time" [Undecided,New]17:07
=== ChanServ changed the topic of #ubuntu-uds-core-2 to: Track: Core | Foundations for app developer workflow | Url: http://summit.ubuntu.com/uds-1311/meeting/21989/core-1311-foundations-for-app-developer-workflow/
dholbachxnox, I'm leading another session at the same time :-/17:56
dholbacherr, slangasek: ^17:56
slangasekdholbach: ok.  Do you need this rescheduled?17:57
slangasekI just sent the hangout invite to everyone subscribed to the session17:57
dholbachno, I don't think I need to be there, I'll watch the video later on17:57
slangasekok, cool17:58
karnislangasek: Thanks for the invite Steve. For this session I'll be mostly a listener.17:59
cjwatsonslangasek: I didn't get it AFAICS18:03
slangasekhttps://plus.google.com/hangouts/_/7acpje7f3dnktlourn64tm45kg18:03
cjwatsonoh, maybe on my phone, which is no use to me :)18:03
slangasekcjwatson: I guess I sent it to the wrong you, sorry :)18:03
slangasekshould've gone to the canonical-you18:03
cjwatsonok - I'll be there in a sec, I'm just finishing updating my local emulator with some rapid use of 3G18:03
cjwatson:-)18:03
zygahi18:05
* rsalveti waves18:05
karnio/18:05
* ogra_ shores18:06
ogra_video !18:09
karniYou're live18:09
rickspencer3o/18:09
xnoxand it's live!18:09
ogra_oh, and colin made his hair ... (he switched the cam on)18:09
asac:)18:10
karnithe whole browser, yes18:10
xnoxyes.18:10
asacyes18:10
xnoxcjwatson: still browser.18:11
loolcjwatson: works well18:11
zygacjwatson: it's hard to share that one18:11
zygaorks18:11
zygaworks18:11
xnoxcjwatson: awesome.18:11
karnigood18:11
loolI see the browser18:11
loolI see my browser window with cjwatson inside18:11
slangasekit's working now - we sorted it out on the hangout rather than waiting for the IRC round-trip :)18:11
slangaseklool: you must be desynced18:12
loolI am, but I was trying to make a silly joke too18:12
loolit's all good now  :-)18:12
karnihehe18:12
rsalvetiand graphics should be working with latest emulator :D18:12
loolhehe18:12
karnirsalveti: \o/18:13
loolrsalveti: is that with passthrough?18:13
slangasekyes18:13
rsalvetilool: yes, because we need opengles v218:14
ogra_we do !!18:14
zygais the child one can hear behind the scenes coming from the current speaker?18:20
ogra_yes18:20
zygaah, ok18:20
karniyes, shell18:21
zygayes18:21
ogra_yes18:21
zygabut very small18:21
zygatoo small to be readable18:21
xnoxcjwatson: yes, we do, but it's small font =))))18:21
zygaor un-maximize the window18:21
rsalvetistill small?18:21
karnimuch better18:21
rsalvetidon't know if it's the delay18:22
xnoxcjwatson: awesome.18:22
ogra_yeah18:22
zygacjwatson: google gives you roughly the same texture for any size of your screen18:22
rsalvetithere's a huge delay18:22
zygacool demo!18:24
xnoxfingers crossed.18:25
ogra_cjwatson, it takes 10min18:25
sergiusensjust be patient!18:25
xnoxcjwatson: very slow emulated processor.18:26
ogra_400MHz ... 512M18:26
ogra_single core18:26
zygaogra_: what is that emulated with? qemu?18:26
ogra_yep18:26
ogra_a very old version18:26
zygaogra_: graphics patches holding it back?18:27
ogra_well, its heavily patched for goldfish18:27
zygaI see18:27
ogra_not just graphics18:27
zygaah, I see18:28
* zyga mutters something about tizen / bada emulator ;)18:28
zygacan we run the emulator with a prebuilt image18:29
zygathat we can download from somewhere?18:29
zygaI tried it today in trusty but the package was broken18:29
janimozyga, it worked for me in trusty today18:29
sergiusensif it confuses people, just don't launch with -shell18:29
janimozyga, I used the build image script as documented18:29
zygajanimo: the script for building the image is broken18:29
ogra_worked fine for me18:30
zygajanimo: it references stuff that's not in the package18:30
zygaI was following the wiki basically18:30
sergiusenszyga, you might of downloaded an older wrong package18:30
zygaI can take it offline if you want to know what I did18:30
ogra_zyga, then you got the broken package18:30
sergiusenszyga, you need -0ubuntu218:30
janimozyga, I was lucky I guess :) I did not check what it actually does, but it made a working sd.img18:30
zygasergiusens: nope, never installed that before18:30
ogra_which also breaks your host18:30
loolI was asking on teh wrong chanel blah18:30
loolQUESTION: do we need separate chroots for native builds and cross-builds due to multiarch deps still?18:30
ogra_(if it is amd64)18:30
loolI mean if I'm on trusty/amd64 and I want to a) cross-build to saucy/armhf and b) build for saucy/amd64, can I use a single chroot?18:30
zygaoh18:30
* zyga checks18:30
ogra_lool, cjwatson cant see his IRC18:30
zygadarn18:30
xnoxslangasek: ^ relay question to cjwatson from lool18:30
zygayeah I have 218:30
zygaer18:30
zyga118:30
ogra_probably someone can forward the question to the hangout18:30
zygacan I just upgrade now? I recall scary recovery instructions18:31
rsalvetizyga: yes, latest should be safe18:31
zygaok18:31
ogra_zyga, just never ever remove libc6-amd6418:31
sergiusenscjwatson, rsalveti check if it's processing a crash18:31
* zyga reboots rarely so proably breaks-on-boot would be a bad thing to do now18:31
ogra_(which the broken package pulled in)18:31
zygaogra_: heh, ok :)18:31
zygaogra_: oh18:32
rsalvetisergiusens: I disabled whoopsie for now18:32
zygaogra_: -amd64 vs :amd64?18:32
ogra_zyga, right18:32
sergiusensrsalveti, yay :-)18:32
ogra_rsalveti, evil you ! how are we getting all these crach reports now18:32
zygaogra_: is there a way to safely get rid of that somehow?18:32
ogra_zyga, once the bug in libc is fixed perhaps18:32
ogra_for now, just dont touch it18:33
slangasekzyga: to fix it, just boot with break=bottom, and copy your ld.so/libc back from the initramfs to the rootfs ;P18:33
slangasekpiece of cake18:33
rsalvetiogra_: well, otherwise you're basically unable to use it18:33
ogra_lol18:33
cjwatsonzyga: sorry, my children can be a bit noisy at times indeed ...18:33
ogra_rsalveti, details :P18:33
loolcjwatson: ok, thanks18:33
slangasek(this happened to me a few weeks ago while sprinting, but sadly I did not link this in any way to the emulator package)18:33
zygathanks!18:33
loolcjwatson: it was no strong reason except limiting the number of chroots people needed (space, ability to download them etc.)18:34
looltime to update them etc.18:34
* cjwatson nods18:34
loolI feel the pressure for fixing the content-hub hook is increasing18:35
zygathanks, interesting demo18:35
zygacjwatson: could you record a video with start-to-end (till it boots) and publish that sometime later? I would think many people would be interested18:35
sergiusenscjwatson, do you have a link to the chroot setup/building? I might have missed it if you did mention it18:36
xnoxcjwatson: don't hit ctrl-c18:36
xnox=)18:36
ogra_lol18:36
xnoxcjwatson: you can open adb shell18:36
zygacool, sounds good for me18:37
cjwatsonclick chroot -aarmhf create (from lp:click at present, soon from the click-dev package)18:37
zygacjwatson: don't disregard the tutorial nature of a complete video though18:37
cjwatsonzyga: agreed18:37
cjwatsonwould need a bit more prep than this got :-)18:37
zyga:-)18:37
sergiusensgreat18:38
cjwatsonthanks all18:39
cjwatsonsorry for the not-quite-fully-in-place demo, but I hope you'll agree it was close :-)18:40
karnithanks all!18:40
sergiusensthanks18:40
karnicjwatson: it was close! :)18:40
cjwatsonand thanks as ever to rsalveti for tireless work on the emulator18:40
ogra_++18:40
rsalvetistill a lot to do, but we're getting there :-)18:40
cjwatsonand to xnox18:40
ogra_++ too18:40
karniyes we are!18:40
ogra_:)18:40
ogra_it is intresting though, for me the emulator worked on first try and a lot sooner than yours18:41
* cjwatson tries ctrl-c and re-running18:41
cjwatsonoh, I forgot one thing, instructions on the emulator18:41
* ogra_ thinks the graphics HW you use has also some impact 18:41
cjwatsonhttps://wiki.ubuntu.com/Touch/Emulator18:41
cjwatsonjust make sure to use the very latest version in trusty18:42
cjwatsonone thing this really highlights is the need to rewrite click in C, as all that Python is slow on first boot :-/18:43
ogra_yeah18:44
cjwatsonha!  unity is up now18:44
ogra_and there is whoopsie (which is currently disabled) and apparmor creating profiles on first nboot18:44
rsalveti\o/18:44
ogra_yay18:44
cjwatsonI should have ctrl-ced during the presentation :-)18:44
karnicjwatson: :D18:45
ogra_ureadahead too ... we might want to disable that18:45
cjwatsonor fix ... cf earlier discussions18:45
cjwatsonhttp://people.canonical.com/~cjwatson/tmp/emulator-yay.png18:47
cjwatson(sorry, import -window root is a bit odd with multi-monitor)18:47
rsalvetiyay18:47
sergiusenscjwatson, write it in go :-)18:48
sergiusensthat's just a pun ;-)18:48
karnicjwatson: thanks for the screenshot!18:51
=== ChanServ changed the topic of #ubuntu-uds-core-2 to: Track: Core | Planning the hardware enablement strategy for 14.04 LTS | Url: http://summit.ubuntu.com/uds-1311/meeting/22029/core-1311-hwe-plans/
slangasekhttps://plus.google.com/hangouts/_/72cpi5mshd3mujd9pk5te8c50s19:01
slangasekhttps://plus.google.com/hangouts/_/72cpi5mshd3mujd9pk5te8c50s19:03
slangasekmore people please join the hangout, this should be a discussion19:04
slangasekdon't leave me all alone in here with the kernel guys19:04
diwicslangasek, ok, I'll try :-)19:05
tjaaltoni'm thinking about it19:06
tjaaltonbut my wife has the laptop now :P19:06
tjaaltonyup19:07
tjaaltonmaarten didn't reply to my pings19:08
tjaaltonok got the laptop, will take a while to set things up..19:10
xnoxogasawara: well at the moment upgrade fails, so one will fail to upgrade from -lts-saucy to quantal.19:11
xnoxinfinity: ^19:11
xnoxare upgrades ever tested from all enablements to trusty?19:12
xnoxincluding -lts-trusty -> trusty19:12
slangasekcurrently, none are tested19:13
infinityxnox: No, but we need to.19:14
argesdo we test LTS dkms packages against all hwe-kernels?19:14
slangasekarges: are there any dkms packages that are in main?19:14
ogasawarahttps://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/124443819:14
udsbotuLaunchpad bug 1244438 in linux (Ubuntu) "EOL notification system required for HWE kernels in LTSs" [Medium,Triaged] - Assigned to Ubuntu Kernel Team (ubuntu-kernel-team)19:15
geofftat some point I'd like to ask about OpenAFS, which is in universe and broke with the most recent HWE kernel19:15
apwgeofft, what broke with it ?  did it fail to install or fail to work19:16
argesslangasek: or maybe more general do we have a good way for dkms packages to support multiple kernels? Is it just #ifdef'ing properly or doing things like this: https://launchpad.net/ubuntu/precise/+package/openvswitch-datapath-lts-raring-dkms19:16
geofftapw: The DKMS modules failed to compile, and we're not really sure about the process for getting fixes19:17
apwgeofft, cirtainly filing a bug, if that is a universe package it is then best efforts19:17
marruslI had a large customer opt-in to HWE kernels accidentally because when they moved forward with the project they grabbed "the latest iso"19:18
marruslthey were ok with it in the end, but they weren't clearly aware of what they were doing.19:18
apwmarrusl, messaging could be better yes19:18
slangasekgeofft: it's a suitable target for SRU19:18
xnoxmarrusl: 12.04.0 images are out there. the messaging on the ubuntu.com website is clear about hardware and non-hardware ennablement stacks.19:18
geofftapw, slangasek: LP #120638719:18
udsbotuLaunchpad bug 1206387 in openafs (Ubuntu Precise) "openafs-modules-dkms 1.6.1-1+ubuntu0.2: module FTBFS on 3.8.0" [High,Confirmed] https://launchpad.net/bugs/120638719:18
slangasekgeofft: we would welcome community SRUs for such issues, but Canonical won't own the update of those packages as part of the HWE stack19:19
geofftI think one thing is we're not sure if we did the SRU process right -- who should be subscribed to these things, what do we need to do to push it forward?19:19
marruslhey I understand, but it's still very confusing to end users.  this is a very large corp that we would have assumed "knew better" but they didn't.19:19
slangasekeffectively, you need to get a package uploaded to the queue19:19
geofftAlso it would be _wonderful_ if this didn't break on the day of the upload of a new point release19:19
slangaseksponsored or otherwise19:20
geofftbecause we have users who will grab the new ISO, install, and then complain at us :-(19:20
bjfxnox, i don't know how you can claim that the messaging is clear .. http://www.ubuntu.com/download/server19:20
geofftand downgrading their enablement stack is a pain.19:20
xnoxwell on the bottom of "http://www.ubuntu.com/download/alternative-downloads" there mentioned about downloading image with "Precise stack" but that's not very clean =/19:21
xnoxbjf: i don't think there was any on server pages.19:21
xnoxslangasek: infinity: in the pool/*.deb19:21
xnox?19:22
bjfxnox, so, you are assuming people know to go to the alternative downloads page and even on that page it is not clear19:22
xnoxbjf: true. i somehow thought it was better explained, but i can't find it any more.19:23
bjfxnox, yes, you can go to "past releases and other flavours"19:23
xnoxbjf: i think we need more explanation text right next to "download" button.19:23
xnox... and on cdimage.u.c19:24
bjfxnox, i agree with that19:24
xnox..19:24
xnoxcannot hear bryan.19:24
apwhe was asking if we will upgrade people at the end of life for the pre-trusty lts-19:25
apwbackport stacks, and that was a no, we would message them19:25
xnoxthanks.19:25
marruslI have a feeling this won't be a popular idea... but I have multiple customers that would LOVE to see the HWE stack extended to networking.  specifically:  network-manager, modemmanager, wpasupplicant, and usb-modeswitch.19:29
marrusl(I have a feeling that NM deps will make this a big pain)19:30
diwicseems nobody wanted to hear about the audio stack perspective, or my mic was muted?19:30
slangasekmarrusl: I don't see why we would make that part of the HWE stack, instead of simple standalone SRUs that nobody gets19:30
infinitymarrusl: Too late, session over.  La la.19:30
slangasekdiwic: oh - yes, you were muted!19:30
slangasekdiwic: sorry :/19:30
argesdiwic: your mic was muted19:30
marruslmeh19:30
slangasekdiwic: wondered why you were so quiet the whole time... :)19:31
diwicanyway; so for PulseAudio we decided not to try to do enablement stack stuff19:31
infinityslangasek: s/that nobody gets/that everybody gets/?19:31
slangasekinfinity: yes, the inverse nobody19:31
diwicand I think this has been working well enough to continue that for the next two years19:31
slangasekok19:31
diwiccompared to trying to backport PulseAudio19:31
slangasekso you agree with the "it worked last time, let's keep doing it"19:32
marruslslangasek, ok interesting.  wpa and usbmodeswitch backport cleanly (iirc) to precise, but I gave up on NM (was way over my head)19:32
diwicI've had one or two patches I had to SRU into PulseAudio to make it benefit from newer kernels, but that's it19:32
infinitymarrusl: Does NM actually provide new hardware support, or just shiny new features?19:32
slangasekmarrusl: ah, I think I missed NM in your list.  Yeah, I don't think we would take that, in *either* kind of update19:32
infinitymarrusl: The point of HWE isn't to backport the world to the LTS.19:32
tjaaltonguess I missed the important bits while stealing my laptop :)19:32
* slangasek nods19:32
diwicslangasek, so yes, I think we can continue with "cautious SRUing" for PulseAudio 14.04 too19:33
apwsounds has been pretty good in precise i think, so that sounds like a sane plan19:33
marruslinfinity, in effect it does...  mobile broadband cards are poorly standardized and one customer has found (working with upstream) that:19:33
infinitytjaalton:  [adconrad] delegate someone in X to do meta packages for X stack if possible19:33
marruslsometimes they need to make a fix in modemmanager, sometimes it's in NM.19:33
infinitytjaalton: Can I delegate that to you after explaining what it means? :P19:33
tjaaltoninfinity: yeah I got that part19:33
tjaaltonand understand what it means19:34
marruslin the case of WPA you may be using new network geat/features that work flawlessly on wpa 1.0 (for example) and quite poorly on 0.7.3.19:34
infinitytjaalton: Excellent.  tjaalton on launchpad too?19:34
tjaaltonyes19:34
diwicand the other point, tjaalton et al, we should probably sit down on our HWE sprint and have a meeting about how this will affect all our pre-installs when their kernels go out of scope. See what we can do if they're running OSP1 and/or OSP219:34
marrusls/geat/gear19:34
tjaaltondiwic: migrating machines from stack-to-stack?19:35
tjaaltonoh19:35
diwictjaalton, essentially; everything we've been enabling this year, e g all the Haswell machines, what will happen when the kernel team stops supporting 3.519:36
gQuigsxnox: heh.. on another note;  did we ever get data to know if we made right call re:64 bitdefault19:36
tjaaltondiwic: yeah, falls under the third paragraph of the notes19:37
tjaaltonactually19:37
xnoxgQuigs: not yet, no. At release day, there was more people downloading 64-bit images. And i'm yet to hear a failure case "64-bit one didn't work on my machine"19:37
tjaaltonI remember they should be migrated to the next LTS stack, ie. one that'll be in 12.04.519:38
tjaaltonso that 12.10 will be maintained three extra monts until this is available19:38
tjaaltonrtg: ^ am I right?19:38
gQuigsxnox: yea I haven't seen any complaints either19:38
diwictjaalton, given the user base I guess that's better than starting to ask questions19:39
tjaaltonthis was discussed in oakland and/or copenhagen19:39
slangasekgeofft: so https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1206387 does not have the ubuntu-sponsors team subscribed; would you like me to subscribe them?19:39
udsbotuLaunchpad bug 1206387 in openafs (Ubuntu Precise) "openafs-modules-dkms 1.6.1-1+ubuntu0.2: module FTBFS on 3.8.0" [High,Confirmed]19:39
infinitytjaalton: No one will be automatically migrated, but we'll be telling them all about their support status in motd/update-manager/lists/etc.19:39
slangasekgeofft: also, can I suggest that you coordinate directly with infinity and/or the kernel team for pre-release testing of the hwe stacks for dkms compatibility?19:40
tjaaltoninfinity: ok, works for me19:40
diwicinfinity, so I typically think that's a bad thing to do for a lot of pre-installs, but the question if the regression risk of moving along will be a worse thing19:40
geofftslangasek: if that's the next step, yes please! I didn't file this bug but I _thought_ we'd followed the SRU wiki page; if we missed a step, sure and apologies19:41
infinitydiwic: I think it's a bad thing too, as does the kernel team, but we've pretty much been told we can't forcefully upgrade people.19:41
gQuigswait how much time will people have to upgrade from a HWE kernel?19:41
bjftjaalton, yes we will support the kernels until 14.04.119:41
tjaaltonright this can't be just a thing baked in update-manager19:41
diwicinfinity, just FTR, told by who?19:41
infinityogasawara: ^19:41
tjaaltonthere needs to be some apt-get'ty way to migrate19:41
infinityogasawara: Who told us we can't force people to migrate?19:41
bjfinfinity, mark19:42
tjaaltonbjf: good19:42
infinitytjaalton: The apt-gety way to migrate is simple.19:42
ogasawarainfinity: sabdfl19:42
tjaaltoninfinity: ok then19:42
diwicok19:42
geofftslangasek: hm, or, is that the upload lfaraone already did?19:42
diwicquestion is if sabdfl's statement applies to preinstalls too, and the reasoning behind it19:42
slangasekgeofft: oh, yes, it's in the queue as of 44 hours ago ;)19:43
diwictjaalton, but anyway I'll write to YK and tell him to have this as a topic during the hwe sprint19:43
infinitydiwic: I don't see why we'd treat preinstalls as unique snowflakes compared to end-user installs.19:43
infinitydiwic: The end result is the same if you preinstalled or user-installed with a 3.5/3.8/3.11 kernel, after all.19:44
tjaaltonyeah osp1 is 12.04.2+steroids, osp2 will be 12.04.3+viagra.. still the same tooling applies19:44
geofftslangasek: It seems like we didn't get any feedback here, so I'm curious what could have been done to get this bug a response better -- it was ready for action 3 months ago, I think.19:45
diwictjaalton, osp2 = 12.04.4 based19:45
ogasawaradiwic: so I did have follow on conversations w/smagoun and jonm where they voiced they had cases where they would want to automatically roll forward when a stack EOL's, so my team created meta packages which could be installed to do so19:45
slangasekgeofft: response from whom?19:45
tjaaltondiwic: oh right19:45
slangasekgeofft: as I said, Canonical isn't going to own updates for universe dkms packages that break - but we welcome community involvement in vetting those19:46
diwicogasawara, and so the question is if these are the packages we use in osp1/osp2 ?19:46
geofftI... don't actually know. What would have been the right steps for we-the-community to take after andersk's 2013-08-26 posting of a debdiff?19:46
tjaaltondiwic: it's an extra package, the oem is free to install it aiui19:46
tjaaltonif they wish auto-migration19:46
ogasawaradiwic: I unfortunately don't know.  I'm not aware of what's in those osp1/osp2 deliverables19:47
geofft(Partly this is a special case because there was a question of, can we just take the latest upstream point release instead of backporting patches)19:47
infinitygeofft: subscribing ubuntu-sponsors (or finding someone to review and upload) would have helped.19:47
tjaaltonjust a bunch of dkms backports..19:47
diwicogasawara, I don't know either, but I know who can figure out at least19:47
geofftslangasek, infinity: Re pre-release testing for dkms in universe, let me see if I can try to find someone current from MIT to have this conversation19:51
slangasekok19:51
geofftI graduated and don't personally care as much about OpenAFS any more, so I'll try to find someone better-placed to do it, but if not, I guess I'll email infinity + the kernel mailing list?19:51
geofftinfinity: wasn't ubuntu-sponsors subscribed right after the debdiff was posted?19:52
infinitygeofft: Oh, so it was, according to the bug log.  I was just going by what slangasek said above.19:53
geofftI think lfaraone unsubscribed ubuntu-sponsors last week after uploading19:54
anderskHi guys, I wrote and posted the debdiff in question.19:54
geofftI'd like to know how to make this go better in the future, since this is not the last time OpenAFS will fail to compile on a new kernel.19:55
geofft(should we move to another channel?)19:55
anderskAnd yeah, I subscribed ubuntu-sponsors, updated the bug description with SRU information, and eventually found and poked lfaraone to make a (still unapproved) upload.If there’s anything else I can do to help, I’d like to know.19:56
infinityRight, this session's officially ended, I'm jumping ship from this channel...19:57
=== ChanServ changed the topic of #ubuntu-uds-core-2 to: Currently no events are active in this room - http://summit.ubuntu.com/uds-1311/core-2/ - http://irclogs.ubuntu.com/2013/11/20/%23ubuntu-uds-core-2.html
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== jack is now known as Guest11163

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!