/srv/irclogs.ubuntu.com/2015/07/08/#snappy.txt

elopioum, scratch that.00:08
elopiodownloaded again and now it works.00:08
elopiounping.00:08
Saviqjdstrand, when you have a sec, I had to upload a new version of emonhub-pi, the review tools did not get an update yet01:04
jdstrandSaviq: accepted02:34
=== chihchun_afk is now known as chihchun
=== wolfeidau_ is now known as wolfeidau
dholbachgood morning06:44
fgimenezgood morning07:01
ogra_Saviq, heh, yeah, thats a fake key (--developer-mode needs it) ... next image i'll edit my name out :)07:12
ogra_Saviq, for installing packages ubuntu-device-flash has the --install option ;)07:22
ogra_(that's how webdm gets into my image)07:23
Saviqogra_, yup, learned that, too, but oem/software works after all07:51
Saviqis there (will there be) a way to hw-assign from an OEM snap? or a gadget snap?07:52
Saviqheh and why does unity-settings-daemon die when building an image :D07:54
ogra_you mean to ship a config with an app snap that enables certain hw access by default ?07:54
Saviqogra_, not sure if an app snap, but maybe an oem/gadget snap?07:54
Saviqogra_, but well, sure, app would work, too07:55
ogra_i think you wont be able to upload that to the store, but for sideloading there should be an ability07:55
ogra_an oem or gadget snap has full HW access07:55
ogra_and access to hwe from a framework or app snap needs to be defined for that snap07:55
ogra_*hw07:56
Saviqogra_, didn't find anything re: hw-assign in https://developer.ubuntu.com/en/snappy/guides/oem/ - that's where I'd expect to put it? under /oem/hardware07:58
ogra_what exactly would you do with it ?07:59
Saviqogra_, I want for an app to have access to /dev/ttyAMA0 straight after flashing07:59
ogra_right, so that app snap needs to define it, not the oem snap08:00
Saviqbut it won't be accepted to the store?08:00
ogra_it wouldnt be accepted with a default that silently enables access to the device08:00
ogra_the requirement is that the admin runs the hw-assign command for the snap to switch on the access08:01
ogra_after installing it08:01
Saviqhmm so how do we plan to support these kind of usecases, say, a managed switch app08:01
Saviqif you want to sell a managed switch, you can't leave the hw-assign to the end user08:01
ogra_well, for you as developer there will be a way to sideload08:02
Saviqsure, I'm thinking end-user08:02
Saviq[...] or expect for the factory line to boot and run hw-assign on every unit?08:02
ogra_if you sell a managed switch with a branded and preinstalled image you will likely also have your own store namespace08:02
ogra_in which you will be able to put such a snap08:02
Saviqhmm08:03
ogra_(for details better ask the store people :) )08:03
Saviqppisati, hi, do you know of a way to disable serial in u-boot for the raspi2? I tried changing std{in,out,err}, but that didn't help, only thing that worked was to set bootdelay to 0 so that it ignores any input (I've an expansion board that talks on ttyAMA0 and interrupts the boot process)08:49
SaviqI thought changing std... should work, but u-boot still reads from the serial port and interrupts auto-boot because the board sends stuff through08:51
ppisatiSaviq: disabling uboot from reading the serial...08:51
ppisatiSaviq: no idea08:52
ppisatiSaviq: you probably need to build your own uboot08:52
ogra_well, on the Rpi a lot of the initialization is done via the binary blob ...08:54
ogra_so even building your own uboot might not help08:54
ppisatiright, i forgot about thir binary blob08:56
ppisatiogra_: deos it emit anything on the console? i don't remember...08:57
ppisatiuhm08:57
ogra_i dont think it does08:57
ogra_but i think it initializes it08:57
ogra_there might be a way to manage that via config.txt08:58
Saviqwell, bootdelay=0 it is :P08:59
Saviqit's not like the usb keyboard works anyway ;P08:59
ogra_bootdelay=0 in config.txt ?08:59
ogra_as a uboot param it only disables the ability to stop the autoboot09:00
ogra_wouldnt change anything in console usage09:00
Saviqogra_, no, setenv09:24
Saviqogra_, and my problem is exactly that - autoboot is stopped because serial is talking09:25
ogra_but udev always talks to serial ... it just doesnt wait for input when autoboot is off09:27
ogra_err09:27
ogra_"autoboot interception"09:27
ppisatiSaviq: i don't see any option to disable the serial output09:31
ppisatiSaviq: you can try to change the baud/serial clock09:31
ppisatiSaviq: and hope that it doesn't interfer09:31
ppisatialbeit it's a crappy solution. i know :)09:31
* ogra_ just notes what he wrote above :P09:33
ogra_s/udev/uboot/09:33
Saviqogra_, sure, and that's exactly it - I just need it to boot, and it doesn't if I leave it - because the board I have is talking on serial on boot, so interrupts u-boot09:50
Saviqppisati, it's not about output, input rather09:51
ppisatiSaviq: same logic applies09:51
ogra_Saviq, well, thats a matter of luck then09:51
ppisatiSaviq: since you don't have any option to not init the serial, wreak it09:51
ppisatiSaviq: or better09:51
ppisatiSaviq: write an email to the raspy2/broadcom people09:51
ppisatiSaviq: and ask for that feature09:52
ppisatiSaviq: btw, how did you make it work with the original broadcom img?09:52
Saviqogra_, sure, I'm not saying bootdelay is the right solution09:52
Saviqppisati, it Just Works with https://wiki.ubuntu.com/ARM/RaspberryPi and Raspbian09:52
Saviqppisati, afaict the bootloader there (not u-boot) isn't talking on serial by default?09:52
ppisatiSaviq: then patch our uboot09:53
ppisatiSaviq: and rip out the serial input part09:53
Saviqppisati, yeah, need to dig into u-boot for that, there's no obvious configs for that, the only relevant thing I found was SILENT... but that won't help with input I don't think09:54
SaviqI was really expecting setenv stdin "usbkbd" to work09:55
Saviqbecause it was serial,usbkbd by default09:55
Saviqbut that didn't change anything09:55
Saviqso yeah, still looking for the right solution, am ok with the interim one though09:56
RlyehHi all10:18
RlyehIs there any GUI for snappy?10:18
dholbachRlyeh, https://developer.ubuntu.com/en/snappy/guides/webdm/?10:19
ogra_only web currently10:19
RlyehI'm using it now10:19
RlyehThank you10:19
seb128bah, I don't understand10:36
seb128upgrading that snappy install, mounting /boot/efi fails10:37
seb128"FAT-fs (vda2): IO charset iso8859-1 not found"10:37
seb128but the same partition mounts fine booting the old / on system-b10:37
=== greyback__ is now known as greyback
ogra_shouldnt it be mounted all the time ?10:40
seb128ogra_, I don't think so, it's in fstab10:43
seb128the mount target fails and sends systemd in debug mode10:43
ogra_sounds like a module mistmatch or so10:48
ogra_can you check lsmod between the two boots ?10:48
seb128ogra_, yeah, on the failed boot lsmod lists only psmouse and pata_acpi10:55
ogra_do you see modules in /lib/modules/* ?10:56
seb128hum10:56
seb128only a /lib/modiles/4.0.0-4-generic10:57
ogra_and nothin underneat ?10:57
seb128but the kernel in use is 3.19.0-2210:57
ogra_ah10:57
seb128yes, they are there10:57
seb128but modproble looks for a 3.1910:57
ogra_right10:57
seb128wth10:57
seb128 /boot has 4.010:58
ogra_sounds like an issue with the grub stuff again ?10:58
seb128where is the booted 3.19 kernel coming from?10:58
seb128I guess10:58
ogra_Chipaca, ^^^ ?10:58
seb128mvo_, sergiusens, Chipaca, ^10:58
ogra_i wonder if we hardcode 3.* soemwhere for the version :P10:59
seb128could be...10:59
Chipacawhasup?11:01
Chipacaseb128: is this on personal?11:01
seb128yes11:02
seb128Chipaca, I installed personal 28 yesterday11:03
seb128and upgraded to 30 with "snappy update"11:03
seb128the new version fails to boot, it load a kernel 3.19 but the /boot version is 4.011:03
seb128which makes it fail to load modules11:03
Chipacaseb128: what gadget snap does personal use?11:06
seb128no idea, how do I tell?11:06
seb128amd64_generic iirc11:06
seb128if that's one11:06
Chipacaseb128: rolling , yes?11:10
seb128yes11:10
seb128Chipaca, http://system-image.ubuntu.com/ubuntu-personal/rolling/edge/generic_amd64/11:10
seb128Chipaca, looks like $prefix/a and /b both have the 3.19 kernel11:11
seb128where today's image /boot has 4.011:11
Chipacawhy does /boot have a kernel, and why are you booting that instead if $prefix/a or /b?11:11
seb128so unsure what is supposed to update the boot kernels but that went wrong11:12
seb128Chipaca, well, it's booting $prefix/a /b11:12
seb128which is what creates the issue11:12
Chipacasounds to me like personal is broken11:12
seb128the system-b partition has /lib/modules/4.011:12
seb128which is the current wily kernel11:12
seb128$prefix/b should have a 4.0 kernel11:13
seb128that matches the installed os11:13
seb128Chipaca, could be, but the issue is that the $prefix/b kernel is the old one and not matching the current image kernel11:13
seb128new image work fine11:13
seb128it's just a snappy updated one that has that issue11:14
Chipacaseb128: the kernel should not be on /boot11:14
Chipacait should be on /boot/a/etc11:14
seb128right11:14
Chipacaboot/grub/a/ or whatever it is11:14
seb128it loads (gd0,gp2)/EFI/ubuntu/grub/a11:14
seb128that is 3.1911:14
seb128but then it tries to boot11:14
Chipacawhich is why i say it sounds like personal is broken11:14
seb128and disk has /lib/modules/411:15
seb128no 3.1911:15
seb128so it fails to load modules11:15
seb128sorry if what I wrote is confusing11:15
seb128it does boot the a/b vmlinuz versions11:15
seb128the issue is that personal 30, which is today image has /lib/modules/411:16
seb128new kernel major11:16
seb128and for some reason the b partition from the upgrade has an old kernel11:16
seb128so boot fails because it doesn't find modules matching the kernel11:16
Chipacayes, yes, i understand11:16
Chipacait was not confusing11:16
ogra_Chipaca, how would personal be able to break an underlying mechanism ?11:16
Chipacai mean, your description wasn't11:16
seb128k11:17
ogra_snappy should work distinct from that11:17
seb128but it's not personal which includes the boot/grub/b11:17
seb128that was generated/build at the upgrade time11:17
seb128new image don't have that issue11:17
seb128Chipaca, the b partition kernel is somehow copied when updating the image I guess? do you know what code does that?11:19
Chipacaseb128: snappy copies it11:20
seb128from where?11:20
Chipacaseb128: the new version might not include a kernel, in which case it gets copied11:21
seb128is that coming from the device tarball?11:22
seb128well the "new version" has a kernel, if you meant the image11:23
Chipacai don't know where and if the device tarball comes into it :)11:23
seb128since a fresh image builds fine11:23
seb128boots fine11:23
Chipacai expect sergiusens will take one look at the symptoms and know what's going on11:23
seb128k11:23
Chipacaso better wait for him than waste time guessing now11:24
seb128let's wait for him then11:24
seb128thanks11:24
Chipacaif he comes in and doesn't, then let's sleuth around11:24
sergiusensseb128: Chipaca ogra_ the livecdrootfs "kernel" and "initrd" entries are all that matter now11:25
ogra_sergiusens, and seb128 got that one installed ... but the old one was completelly removed (so no modules)11:26
Chipacasergiusens: mo'in :)11:26
sergiusensso /boot/grub/[a|b]/vmlinuz11:26
sergiusensogra_: oh nice, how did that happen?11:26
seb128sergiusens, hey11:26
seb128sergiusens, install snappy personal 28 from yesterday11:27
seb128snappy update11:27
seb128reboot11:27
seb128get a system-b boot11:27
seb128kernel loaded is 3.1911:27
seb128disk / files are 4.011:27
seb128boots fail to load any module11:27
seb128sergiusens, that's the summary11:27
sergiusensseb128: lib/modules/ only for 4 as well?11:27
seb128yes11:27
seb128which is basically what fails the boot11:27
sergiusensstrange11:28
ogra_do you have another kernel in /boot directly or some such ?11:28
seb128modprobe something gives a "fails to load /lib/modules/3.19..."11:28
seb128no11:28
sergiusensogra_: there is, I didn't clean those up either in the 500-.*kernel.* task11:28
ogra_sergiusens, perhaps grub falls back to that ... lbut if seb128 says there isnt one ...11:28
sergiusensthere should be in /boot (system-[ab])11:28
sergiusensogra_: our grub.cfg doesn't look for one there11:29
seb128sergiusens, ogra_, http://picpaste.com/grub-9EyGcmUy.png11:30
seb128if that helps11:30
seb128http://picpaste.com/pics/grub-9EyGcmUy.1436355024.png11:30
seb128the vmlinuz size on those matches the 3.19 from hd0,411:31
sergiusensseb128: right, that /boot is system-a/boot/11:32
seb128sergiusens, well, in any case $prefix/a|b shouldn't be identical11:33
sergiusensseb128: what's in (hd0,2)/[a|b] ?11:33
sergiusensoh, sorry it's above11:33
seb128right11:34
seb128neither matches the system kernel11:34
seb128they both match the old image 3.19 one11:34
sergiusensseb128: I need to see the system-image delta because this would make them look the same: http://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk/view/head:/live-build/ubuntu-desktop-next/hooks/500-move-kernel-to-device-tar.binary11:37
seb128sergiusens, where is the delta?11:37
sergiusensseb128: /pool/device-c06d05a678026547b8d48d99556b24281164724e7bffd61c95c261c6e9e3ab70.delta-device-4c246a16efc5ecf0c5f861394250cd68147710376c24d533939365c748939449.tar.xz11:38
seb128sergiusens, do you need that from my system or...?11:39
sergiusensseb128: oh no, I'm downloading for s-i, you don't have it in it's original form anymore ;-)11:40
seb128k11:40
seb128let me know if you need more info from me11:40
seb128but you can probably reproduce by installed personal 2911:40
seb128then doing a snappy update11:40
seb128installing*11:41
sergiusensseb128: I bet core has the same problem11:41
sergiusensfgimenez: ^11:41
seb128yeah, I'm doing an install now to see11:41
seb128but I would bet the same11:41
* ogra_ thinks seb128 should just have used the stable personal image ... there also lightdm and the session would work :P11:48
seb128:-)11:48
utlemmingsergiusens, rsalveti: I am happy to report that with 118, we have a working 15.04 edge for Azure.11:49
rsalvetiutlemming: \o/11:49
rsalvetielopio: fgimenez: I published another image yesterday with a minor fix for azure, and hopefully that should be the last known bug we have11:50
ogra_utlemming, yay11:50
fgimenezrsalveti, ok thx 118 then right?11:52
sergiusensutlemming: \o/11:52
rsalvetifgimenez: yeah, and 119 for armhf11:52
rsalvetithey are out of sync11:52
fgimenezrsalveti, ok11:52
fgimenezsergiusens, sorry wasn't connected :) which problem on core?11:53
utlemmingsergiusens, rsalveti: thank you guys for the help in getting this cleared. You guys were great :)11:53
sergiusensnp11:54
sergiusensseb128: ogra_ mvo_ Chipaca these are the system image delivered files in the delta: http://paste.ubuntu.com/11841020/11:59
sergiusensseb128: ogra_ mvo_ Chipaca assets/vmlinuz and system/boot/vmlinuz-4...11:59
sergiusensthis is a livecd-rootfs/s-i problem and not a snappy update one I think12:00
sergiusensand 'removed' basically removes 3.1912:00
ogra_sergiusens, eparse ? (for your last line)12:05
mvo_sergiusens: hm, it should be possible to reproduce this on core too - let me try that12:05
sergiusensogra_: the s-i 'removed' file has 3.19 listed as a remove target12:07
sergiusensmvo_: yeah, that is the suspicion12:07
ogra_ah12:08
sergiusensmvo_: I'm not sure how to make livecd-rootfs and/or s-i do what we want though12:08
ogra_hmm12:09
ogra_how often do we actually copy the azure tarball around ?12:09
ogra_there seems to be a cp in live-build/auto/build and there is a hook as well where the same cp gets called12:09
sergiusensogra_: for rolling we shouldn't be needing it soon-ish12:10
ogra_well, and even then i guess once would be enough :)12:11
ogra_i dont see where livecd-rootfs could be wrong here12:12
ogra_the code seems all fine12:13
sergiusensogra_: yeah, I don't either12:15
sergiusensogra_: but how would a different kernel than the one copied end up there?12:16
ogra_bug in s-i ?12:16
sergiusensogra_: hmmm, maybe .signed is != than the unsigned one12:17
ogra_yeah12:17
ogra_well, we dont ship .signed12:17
ogra_we copy/move it to be plain vmlinuz, no ?12:17
sergiusensogra_: yes we do, vmlinuz-4.0.0-4-generic.efi.signed12:18
sergiusensogra_: yeah, there's an if in the 500 task that prefers the .signed one12:18
sergiusensogra_: mvo_ that's it12:18
ogra_but we should have the signed 4.0 one there at that point12:19
sergiusensogra_: mvo_ I mean, that is the reason for the different sig http://paste.ubuntu.com/11841115/12:19
ogra_why would we end up with a 3.x signed one during build12:19
ogra_ah12:19
sergiusensseb128: can you md5sum the kernels?12:20
sergiusensogra_: they are all 4.0 delivered in the delta12:22
sergiusensmvo_: this makes me thing the SyncBootAssets stuff runs after the upgrader logic and it is overwritting12:22
sergiusensthink*12:22
seb128sergiusens, what kernels? the a/b vmlinuz?12:27
sergiusensseb128: yeah12:28
seb128that's going to match the 3.19 kernel I guess12:28
seb128since they are byte identical in size12:28
rsalvetiSaviq: ogra_: you'll be able to assign hardware to snaps at the gadget snap later on, the spec for that is still in progress12:28
seb128from the ls earlier12:29
ogra_rsalveti, that still wont enable it in your app snap12:29
Saviqrsalveti, ah, /me just wrote a nice post to the snappy-devel  ML ;)12:29
sergiusensseb128: right, then no worries12:29
ogra_rsalveti, for that you still need to either call hw-assign or have a sideloaded snap that has it enabled12:29
Saviqhmm?12:30
sergiusensSaviq: rsalveti dev nodes are assignable through the oem snap today12:32
Saviqd'oh12:32
rsalvetiif just hw-assign yeah, you can do that12:32
rsalvetibut for the gadget snap there is also the idea of abstracting hardware and assigning a special piece of hardware to an app or framework12:32
sergiusensSaviq: https://developer.ubuntu.com/en/snappy/guides/appliance-builder-guide-webcam/12:33
Saviqogra_, ppisati, btw, I just grokked what you guys were talking about "the raspi blob and config.txt", I don't think that's a problem as when not using U-Boot (and IIUC booting straight into the kernel) there's no such problems12:33
Saviqsergiusens, right, I was sure I read about that somewhere, but it's not there in the oem guide, or in the packaging reference12:33
sergiusensSaviq: no it's not :-/12:34
* sergiusens blames mvo ;-)12:34
rsalvetiguess we can make an mr for that doc :-)12:34
ogra_Saviq, RPi can not boot without the binary blob ...12:34
mvo_sergiusens: hm?12:34
=== mvo_ is now known as mvo
ogra_Saviq, it is: blob -> u-boot -> kernel12:35
Saviqogra_, yes12:35
sergiusensmvo: not documenting the oem hw-assign work :-)12:35
mvo*cough*12:35
mvolalalala12:35
Saviqogra_, others go blob -> kernel directly12:35
ogra_yes12:35
ogra_and dont use an initrd12:35
Saviqogra_, so disabling console=ttyAMA0 there is enough12:35
ogra_in the config.txt you mean ?12:35
Saviqogra_, yes12:35
Saviqogra_, but when u-boot comes into play, u-boot itself talks serial, too, so changing uEnv.txt is not enough12:36
Saviqogra_, so all in all I still just need to disable serial in u-boot, and bootdelay 0 gets it done, while obviously not a good solution12:36
ogra_well, i fear there is no good solution :)12:37
ogra_as long as there is that binary blob ...12:37
Saviqthat's why I thought dropping "serial" from u-boot's env std{in,out,err} would work, but it didn't (sounds like a bug)12:37
ogra_well, sounds like an upstream bug then12:38
Saviqogra_, well, it's u-boot that's problematic in my case, blob isn't great for sure, but isn't a problem atm12:38
Saviqogra_, totally, will go to them to find out12:39
=== erkules_ is now known as erkules
seb128sergiusens, mvo, do you want a bug report/more info from me on that upgrade/kernel issue?13:00
mvoseb128: I think that would be good, with the exact image versions13:01
Saviqbeuno, hey, sorry to bug you, could I ask you to remove emonhub-pi.saviq from the store? I had to rename it (if you could ack emonhub.saviq please - it passes click-review with tools-proposed PPA) and it ended up under phone for some reason, as well as snappy13:05
ogra_Saviq, isnt there an option in the store UI for you to do it yourself ?13:06
Saviqogra_, can't see it, it's there for drafts, otherwise I can only unpublish13:06
ogra_yeah, unpublish was what i meant13:07
ogra_unpublish and publish again13:07
Saviqogra_, don't think I can rename this way, can I? and I don't want it under Phone, either, not sure how it ended up there13:07
ogra_you can not rename13:08
kyrofaseb128, so I created an Ubuntu Personal image with u-d-f and got it in KVM, but I only get the unity8 greeter with the QXL video model, and then my mouse pointer is strangely offset from my actual mouse so I can't possibly get through the edge demo, haha13:08
ogra_you need a new submission and delete the old one from the store13:08
Saviqogra_, yeah, which is what I asked for, I can't delete myself it seems13:08
ogra_kyrofa, wow, thats more than i get !13:08
seb128kyrofa, use virt-manager rather than kvm maybe?13:08
ogra_Saviq, you can unpublish13:08
seb128kyrofa, I don't get those issues with it13:08
Saviqogra_, that I did13:08
ogra_that should delete everything13:08
Saviqogra_, well, it's still there, just not published ;)13:09
ogra_and then create a new app in the store under the new name13:09
ogra_you can not use the old bits anyway13:09
kyrofaseb128, I used virt-manager... thought that was still kvm?13:09
Saviqogra_, that still leaves me with the original in the list, my OCD can't deal with that ;)13:09
ogra_heh13:09
kyrofaogra_, what's happening for you?13:10
ogra_kyrofa, lightdm with guest account ... if i hit enter it logs into a black screen13:10
kyrofaseb128, initially I tried it with regular-old kvm, but them I get the lightdm13:10
kyrofaogra_, try QXL video model13:10
* ogra_ will ty that later after we released 15.04 :)13:11
kyrofaogra_, that's exactly what I get if I DON'T use QXL13:11
seb128kyrofa, k, unsure about the mouse ofset, you should be able to focus the password entry by clicking around no?13:11
ogra_(currently my bandwith is used for other images)13:11
kyrofaseb128, that's correct, but the edge demo is hopeless haha13:11
seb128ogra_, when did you try that? those issues are resolved since friday13:11
seb128kyrofa, oh :-/13:11
kyrofaseb128, and I don't get a mouse offset with a regular ubuntu image13:11
seb128it's just one dnd from the left13:11
ogra_seb128, thursday ;)13:12
seb128ogra_, k, try again then!13:12
ogra_yeah13:12
ogra_takes a century to download that image :P13:12
ogra_you carry so much bloat13:12
seb128lol13:12
* Chipaca ~> late lunch13:13
seb128yeah, what's up with those people installing softwares so you can actually do something with your system13:13
seb128rather than watching a blinking cursor13:13
ogra_my phone doesnt need all that !13:13
ogra_:P13:13
seb128no unity8 on your phone, right ;-)13:13
kyrofaseb128, talking to kgunn it sounded like when he was testing it earlier lightdm was on vt7 and unity8 was on vt8. I couldn't verify that-- is that still how it's supposed to be working?13:14
seb128kyrofa, we activated autologin now so no13:14
seb128what kgunn described was when you were getting the greeter at boot13:14
kyrofaseb128, when you run the image, do you see a unity8 login or lightdm?13:14
kyrofaseb128, ah, okay13:14
seb128unity813:14
kyrofaseb128,  but you didn't have to mess with the video model settings at all?13:15
seb128you have to use qlx/spice13:15
seb128otherwise unity8 doesn't work13:15
seb128and you get a session which fails to start and send you back to the lightdm greete13:15
seb128greeter13:15
kyrofaseb128, ah, okay so that makes sense. Definitely what ogra_ is running into then13:15
kgunnunless you install VMM13:15
kgunnthen it's magic13:16
seb128right13:16
kyrofakgunn, haha man, you guys must have a cooler VMM than I do13:16
kyrofakgunn, although I'm running mine on trusty. Too old?13:17
kgunnoh may be13:17
ogra_hopefully not13:17
kgunnkyrofa: curious, what's your desktop gpu13:17
ogra_if it is it should be updated via an SRU13:17
kyrofakgunn, I have one of those wonky dual-GPU things. Right now I'm running on intel, but I also have an nvidia auadro K1100M13:18
kyrofakgunn, s/auadro/quadro/13:18
kgunnmmm13:20
kyrofakgunn, yeah, if I fire up an VM using the personal.img I made without modifying the config at all, I get lightdm13:20
kgunnoh ok13:20
kgunnkyrofa: but from scrollback, you're seeing mouse offset being an issue as well ?13:21
kyrofakgunn, if I fire it up and modify the explicitly use QXL, I get unity8 but my mouse is offset enough I can't make it through the demo13:21
kyrofakgunn, yeah13:21
kgunnyeah, edge demo was really tricky for me, but got thru13:21
kgunnstill not tried yet on wily, am going to as soon as i get off this hangout i'm on :)13:22
kgunnHO + vmm at once is bad :)13:22
kyrofakgunn, haha13:22
sergiusensseb128: mvo I'm going through the code now, but I have a feeling13:29
kyrofaseb128, I switched from VPN to spice in VMM and now I can't seem to click on anything at all13:35
kyrofaseb128, ugh... VNC. Been dealing with the VPN lately13:35
kyrofaI wonder if bregma has played with this at all yet. Get it running on any hardware?13:36
mvosergiusens: the s-i code? or snappy? sorry, was in a meeting13:39
kyrofaseb128, ah, I got it working!13:40
sergiusensmvo: I think SyncBootloader files is being done after applying the updates13:41
mvosergiusens: ohhh13:42
kyrofaseb128, this is cool man, awesome job!13:42
mvosergiusens: that rings a bell, it might be me who broke that :(13:42
sergiusensmvo: essentially stepping over13:42
kyrofaogra_, kgunn I had to explicitly set QXL and spice in VMM, and make sure there were no tablet devices in the hardware list (I added one messing around with trying to get VNC to work). VNC worked, but gave me a mouse offset. Spice seems to work great13:44
mvosergiusens: I think you are spot on13:47
sergiusensmvo: I wish I were; but it seems it is not the case13:48
kyrofaseb128, other than that trouble (which was really my own fault), the only thing I ran into was SSH. There's an SSH server, but it has no host keys. Is that a feature?13:49
mvosergiusens: meh, ok13:49
sergiusensmvo: systemimage.go:180 shows me a sync first and then an applying updates from the server13:49
sergiusensseb128: in your grub you had a hardware.yaml inside a/b, right?13:54
kyrofasergiusens, what conclusions can I make if `snappy search webdm` gives me nothing?14:00
sergiusenskyrofa: that's it's not available for the released image you are using14:01
kyrofasergiusens, ah, so when it was uploaded to the store it was specifically targeting ubuntu-core?14:01
sergiusenskyrofa: maybe14:01
kyrofasergiusens, any chance we could get it targeting ubuntu-personal as well?14:02
sergiusenskyrofa: and this says yes http://search.apps.ubuntu.com/api/v1/package/webdm14:02
sergiusenskyrofa: sure, if in a hurry just download from the anondownload link there14:02
kyrofasergiusens, ah, good idea. No rush then :) . The snappy scope just needs it until the snappy service has the API. Then webdm can stop targeting ubuntu-personal14:03
seb128sergiusens, yaml, yes14:19
sergiusensseb128: mvo I found the issue; "HandleAssets" is ignored because it can't find the hardware.yaml in writable/cache/system during the upgrade14:21
elopiogood morning.14:23
ogra_schnaaapiee14:24
elopiohttp://paste.ubuntu.com/11839856/14:28
elopiocan somebody give me a hand here? This happens on beagle the second time we fake an update ^14:28
elopioany idea what could cause it? Works alright on kvm.14:28
sergiusensmvo: and I know why the hardware.yaml is not coming through in the update... it doesn't change14:30
sergiusensmvo: ogra_ https://code.launchpad.net/~sergiusens/livecd-rootfs/snappyDevicePart/+merge/264158 if that works, we should get it in for seb128's personal14:47
* ogra_ goes to check his wine cave to see what kind of bribes tro accept14:48
sergiusenslol14:48
sergiusensrsalveti: elopio mvo fgimenez Chipaca btw ^ should be affecting 15.04 and bbb; luckily we now have the same codepath in rolling so it's faster to detect14:49
sergiusensI'll explain during standup14:49
* rsalveti looks14:49
seb128sergiusens, changes in livecd-rootfs impact the image build, do they also impact the upgrades?14:54
rsalveticool, will wait you to explain the issue during the standup14:54
seb128sergiusens, because a fresh image boots fine14:54
sergiusensseb128: yeah, hmm14:56
* sergiusens notices he'll have to explain twice14:56
seb128sergiusens, don't bother explaining it to me if I just don't get how the snappy details14:57
seb128as long as you are sure it's going to do the trick ;-)14:57
sergiusensseb128: what happens is snappy ignores the new kernel and initrd if there is no hardware.yaml, the s-i doesn't not provide the hw.yaml because it is always the same, so it is essentially ignored and you do't get the new kernel14:57
sergiusensseb128: adding versioned kernel's and initrd's to the hardware.yaml effectively changes the file and triggers s-i to provide it14:58
seb128I see14:58
sergiusensthat's it in a nutshell14:58
seb128sergiusens, thanks for the explanation14:58
sergiusensoh, and the important part is that it is ogra_'s fault!14:58
sergiusens:-D14:58
ogra_yeah, sorry14:59
ogra_:P14:59
seb128he better makes up for it by reviewing the fix then! :-)15:00
ogra_you just want to keep your wine !15:00
ogra_the fix looks fine :)15:00
=== chihchun is now known as chihchun_afk
ogra_ppisati, http://paste.ubuntu.com/11839856/ any idea what that means ?15:24
ogra_seems elopio gets that on upgrades15:25
elopioogra_, ppisati: more precisely, on the second fake update. We change the channel cfg to have version -1 to test snappy update on the latest image.15:26
elopiothe first time we do that, it works. The second time, the board doesn't boot.15:26
ogra_elopio, right, that shouldnt really matter ... though what i dont get is that it is the second upgrade but it boots from the b partition15:27
ogra_if it is the second it should boot from a15:27
ppisatisame kernel and same dt? weird15:27
ogra_not sure it is the same15:28
ppisatiFDT_ERR_BADLAYOUT15:29
ogra_yeah15:29
ppisatisounds like a malformed dtb15:29
ppisatiif these are not the same, try to switch to the old one15:29
ppisatiif they are the same, can you check with md5sum?15:30
ppisatiand report the version if they are different15:30
ogra_elopio, ^^ can you try that ... alos check if there is actually a dtb15:30
ogra_on the b dir15:30
ppisatiit seems there is15:30
ppisatibecause it's loading it15:30
ppisatireading b/dtbs/am335x-boneblack.dtb15:30
ppisati30025 bytes read in 9 ms (3.2 MiB/s)15:30
ogra_oh, right15:30
ppisatii wonder if it's intact and sound15:31
* elopio checks some things.15:33
seb128hum15:35
ogra_dont say that !15:36
seb128so in snappy list, upgrade, etc the system refers to "ubuntu-core" versions15:36
ogra_(that usually means something bad)15:36
seb128even on personal15:36
seb128lol15:36
seb128that one is a detail :-)15:36
ogra_haha15:36
seb128I wonder if there is a valid wishlist there15:36
seb128or if we see personal as a temporary thing/don't want to abstract the name15:36
ogra_definitely worth a bu, though i guess once ubuntu-* are snaps it will fix itself15:37
ogra_*a bug15:37
seb128https://launchpad.net/ubuntu/+source/ubuntu-snappy/+bugs15:40
seb1283 bugs reported only15:40
seb128I've a feeling snappy is one of those projects with unsynced buglists :p15:40
* ogra_ quietly points to the channel topic :)15:40
seb128yeah15:41
sergiusensseb128: create a bug please, that's an easy fix15:42
sergiusensseb128: goes back to the hardcoded days (but I haven't been able to remove all)15:42
seb128sergiusens, https://bugs.launchpad.net/snappy/+bug/147267615:42
ubottuUbuntu bug 1472676 in Snappy "refers to "ubuntu-core" even for "ubuntu-personal" images" [Undecided,New]15:42
sergiusensseb128: thanks15:42
seb128yw!15:42
sergiusensogra_: hmm, mvo seems to be MIA, can you validate this? http://paste.ubuntu.com/11842157/ (I can upload)15:43
ogra_sergiusens, ACK., go ahead15:43
sergiusensogra_: thanks15:43
seb128ogra_, sergiusens, should the same be done to desktop-next?15:44
sergiusensseb128: doing it differently on desktop next, this is just for 15.0415:44
seb128k15:44
sergiusensseb128: the other MP, if it works, we will use for desktop-next as well15:44
seb128great15:44
ogra_sergiusens, well, but seb128 surely wants https://code.launchpad.net/~sergiusens/livecd-rootfs/snappyDevicePart/+merge/264158 for that15:44
sergiusensogra_: yup15:45
sergiusensafter we know it works15:45
=== vmayoral|pc is now known as vmayoral
ogra_sergiusens, merged and uploaded15:48
sergiusensyuppie15:49
sergiusensrsalveti: elopio fgimenez ogra_ I'm going to trigger a 15.04 image build in a bit which might solve the hardware.yaml on upgrades issue for bbb15:50
ogra_yay15:50
sergiusensoh, stuck waiting on arm6415:51
sergiusensogra_: do you just cancel the build?15:51
ogra_yep15:51
fgimenezsergiusens, ack thanks15:52
kyrofasergiusens, the anon download link for webdm is giving me a 503. Any ideas?15:56
elopiokyrofa: here too.15:56
kyrofaelopio, oh. Maybe it actually IS temporarily unavailable, eh?15:57
elopiokyrofa: maybe. beuno do you know something?15:57
beunoyes15:58
beunoit's down15:58
ogra_there is a bunch of stuff down atm15:58
ogra_phones cant install apps either currently15:58
sergiusenskyrofa: store is down15:58
rsalvetilovely15:58
rsalvetiright time for lunch15:58
ogra_heh15:58
kyrofasergiusens, beuno thanks guys. Is there a status page I can keep an eye on?15:59
beunokyrofa, not at the moment, no16:00
beunosorry16:00
kyrofabeuno, that's alright. Any estimate?16:00
beunokyrofa, minutes, 5-3016:01
kyrofabeuno, great, thank you :)16:01
seb128ogra_, thanks for the merge/upload16:01
ogra_np16:01
ogra_i'll trigger a core build too so it can be tested16:01
kgunnseb128: i updated to wily, just tried personal image....works like a champ! \o/16:09
seb128kgunn, excellent!16:09
kgunnbregma: willcooke ^16:11
bschaeferogra_, hello, so i've my raspi2 image set up with snappy, but it seems to be missing the /dev/dri/card*? This will seem to be problematic for running a mir server16:13
bschaeferi was told possibly something is missing from the kernel in that image?16:14
ogra_bschaefer, well, that will need a lot more extra work to make the binary blob work to actually drive the graphics HW16:14
bschaeferogra_, shoots16:14
bschaeferbregma, kgunn ^16:14
bschaeferogra_, is this the same with the BBB? (besides not being able to flash the eMMC)16:15
ogra_the upcoming 15.04 image will have some raw support to hack overlay dtb's and graphical options into the kernel commandline16:15
ogra_the BBB isnt suitable for graphical stuff16:15
bschaeferi see, thats what i heard but wasnt sure :)16:15
bschaeferogra_, do you know when that image would be released?16:16
ogra_dont bother with it ... it is fine for a single app for mmanaging some relais on an attached touchscreen or some such16:16
bregmaogra_, what's the expecxted delivery date for the PI image?16:16
ogra_but you wont be running a desktop on a BBB16:16
bschaeferogra_, right, yeah just trying to figure out whats possible and not16:16
ogra_bregma, for the 15.04 uupdate ? this week i think16:16
bschaeferogra_, awesome thank you!16:16
bregmaogra_, and we'll be able to run Mir on the PI then?16:17
ogra_i'll also start providing buuilds of the edge channel with that hw tarball and oem snap16:17
ogra_bregma, well, it is 15.0416:17
ogra_not sure how much you can do on that base ... i would assume you want to wait for the edge image (on my plan for next week)16:17
kgunn15.04 prollly ok to start with16:18
ogra_ah, fine then16:18
kgunnogra_: why is BBB not good for gfx ?16:18
* kgunn has no history16:18
bregmano binary blob graphic driver support for gles, I assume16:18
ogra_kgunn, single core-industirl-embedded CPU ... while it has a GPU it is really not a powerful one16:19
kgunnogra_: it has like a sgx530 or some such i thot16:19
ogra_i think there is an SGX driver for it but that likely needs a specific (and likely very old) kernel and patches16:19
kgunnwhich is enough for kiosk type thingy16:19
ogra_right16:20
bregmaMir support for software rendering should fix that, as I understand it16:20
ogra_thats what i meant above16:20
bschaeferit would still need to support running the server16:20
ogra_enough to run a UI for your heating controller as single purpose UI16:20
bschaeferwhich from what i understand you need at lease the /dev/dri/card0*16:20
beunodownloads should be back16:20
bregmathat is definitely what we're aiming for here16:20
kgunnogra_: ok, so it's possible, "we" 're just not investing in it (bbb gfx)16:20
ogra_bschaefer, i thought dri is dead ? and it is all kms nowadays16:21
ogra_kgunn, it isnt suitable for desktop ... if you want to build a kiosk thingie, go ahead :)16:21
kgunnk16:21
bschaeferogra_, err i suppose i could be looking for that as well... that was just waht i got when i was talking to #mir yesterday :)16:21
bregmaall we really need for kiosk should be good 2D acceleration16:21
* bschaefer hopes it works outside of that16:21
ogra_(though the price you pay for BBB plus LCD cape will likely be more expensive than a cheap tablet)16:22
kgunnhehe16:22
bschaeferogra_, pfft it has a mini HDMI16:22
ogra_heh16:22
bschaeferbut yeah still more expensive16:22
bschaefer(if you get a small screen)16:22
kgunnok, gonna run/lunch bbiab16:23
bregmaa BBB, and old cast-off monitor, a carboard box and some duct tape is all I need to build my info-kiosk for my front door16:23
bschaeferhaha16:23
ogra_thnen you just need to learn to use directfb16:23
ogra_that should work already :)16:23
ogra_without any drivers16:24
bregmaI don't think that's yet available in Mir16:24
ogra_no, that is something lower than Mir16:24
ogra_talking directly to /dev/fb0 via a lib16:25
ogra_(unaccelerated 2D)16:25
elopiokyrofa: udf works for me now, maybe your server is up too.16:33
kyrofaelopio, yeah, all good here. Thanks beuno!16:36
kyrofasergiusens, do you know anything about the snappy examples?16:42
kyrofasergiusens, lp:~snappy-dev/snappy-hub/snappy-examples16:42
kyrofasergiusens, the hello-dbus example puts the service into a framework and the client into an app. Is there a good reason to do that instead of including both in the same snap?16:47
kyrofaLooks like jdstrand initially wrote it. jdstrand ^^ any input?16:48
sergiusenskyrofa: because the app depends on the framework, it's the only dependency chain allowed17:09
sergiusenskyrofa: and it's just an example, so maybe useless for a real case17:10
kyrofasergiusens, but couldn't a single snap include both the dbus service and the client?17:11
sergiusenskyrofa: yes they can17:14
sergiusenskyrofa: I had that in one of my apps from before the release17:14
sergiusenselopio: rsalveti do you have a revno for 15.04 on edge handy with an older kernel?17:15
rsalvetisergiusens: hm, not handy17:15
rsalvetisergiusens: we landed a new kernel on monday17:15
kyrofasergiusens, is there a reason to do one over the other? I understand that this is just an example, I'm just curious. Obviously a framework can be relied upon by multiple snaps, and it decouples the service and the client. Would that really be the only reason to do it that way?17:15
rsalvetisince then, I believe we did 2,3 new builds17:15
elopiosergiusens: no sir. Just old 15.04 stable here.17:16
sergiusensrsalveti: k, will check some dates in the index; I wish this process weren't so manual :-)17:16
sergiusenskyrofa: different vendors providing extensions17:16
sergiusenskyrofa: just like docker17:16
sergiusenskyrofa: docker framework and runtimes/dockerapps in apps17:17
sergiusenskyrofa: I don't know how to make it clearer :-)17:17
kyrofasergiusens, alright, makes sense. Thanks :)17:17
rsalvetisergiusens: well, you own the tool that interacts with that server :P17:18
sergiusensrsalveti: but not the one that does the s-i->cdimage part17:19
kyrofabeuno, how do manual snap upload reviews occur? How long does it typically take?17:19
sergiusensrsalveti: do you see a problem with this? http://paste.ubuntu.com/11842157/17:19
rsalvetisergiusens: looks fine17:20
sergiusensrsalveti: I get 'hashes: -\n' after building17:20
beunokyrofa, as a rule, if something is manual it will likely get rejected17:21
sergiusensrsalveti: oh, ic the problem :-/17:21
sergiusensI think17:21
rsalvetisergiusens: either the var is not protected or we got nothing with md5sum17:21
sergiusensrsalveti: yeah, I don't see the problem, damn shell scripts17:22
ogra_whats the issue17:22
kyrofabeuno, hmm. I'm referring to the last paragraph on this page: https://developer.ubuntu.com/en/snappy/tutorials/build-snaps/17:22
sergiusenslol17:22
kyrofabeuno, it implies that all snap reviews are manual?17:22
* sergiusens thinks ogra_ has a highlight for shell script blasfemy17:23
rsalvetilol17:23
ogra_shhh17:23
sergiusensogra_: I get 'hashes: -\n' after building17:23
sergiusensogra_: with http://paste.ubuntu.com/11842157/17:23
beunokyrofa, they are not. They are automatic and get approved within seconds (if they pass automatic review scripts_17:24
beunokyrofa, that's outdated, I guess17:24
ogra_sergiusens, hmm, i think thats a bashism17:24
beunoasac, who maintains this?  https://developer.ubuntu.com/en/snappy/tutorials/build-snaps/17:24
ogra_cut -f1 -d' '17:25
ogra_instead of cut -f1 -d\17:25
kyrofabeuno, ah! Okay good deal17:25
sergiusensogra_: ok17:25
sergiusensogra_: is that the only thing? I want to avoid another 30 cycle :P17:26
rsalvetibeuno: our team I guess, why?17:26
ogra_sergiusens, not sure, do you have any log ?17:26
beunorsalveti, it says all submissions are manual17:27
rsalvetisergiusens: guess you can easily test that logic locally first17:27
beunothey are not17:27
ogra_quotes wouldnt be abd either i guess17:27
ogra_*bad17:27
sergiusensrsalveti: I have17:27
rsalvetibeuno: yeah, we can update that17:27
beunorsalveti, thanks17:28
ogra_sergiusens, in any case make sure to have a "set -ex" at the top of the script, then we get more detailed logs ... log space is cheap17:28
sergiusensrsalveti: ogra_ ... md5sum: /tmp/tmp.csXhKqYL59/assets/vmlinuz: No such file or directory17:28
sergiusensthere we go17:28
ogra_aha17:28
jdstrandkyrofa: I did it as an example of writing a framework that another snap would depend on. it is fine for a framework to ship other services or binaries17:30
kyrofajdstrand, thank you17:31
kyrofajdstrand, hey, thanks for the email about the QHD stuff too. Nice to have crisp notifications again, haha17:32
jdstrandkyrofa: I know, right? that was annoying17:33
jdstrandglad it helped :)17:33
ogra_sergiusens, hmm, where do you see that ? the build log properly has http://paste.ubuntu.com/11842705/17:33
sergiusensogra_: it's set17:33
ogra_yeah, just noticed17:33
sergiusensogra_: https://launchpadlibrarian.net/211113785/buildlog_ubuntu_vivid_amd64_ubuntu-core-system-image_BUILDING.txt.gz17:33
kyrofajdstrand, it's just such a beautiful, crisp screen... and then... yeah17:33
ogra_cat'ing hardware..yaml at the end would be helpful17:33
ogra_sergiusens, LOL17:34
ogra_sergiusens, vmlinux != vmlinuz ;)17:34
ogra_(your patch has a typo)17:34
sergiusensogra_: yeah, fixed17:35
sergiusensogra_: still won't fix the issue ;-)17:35
ogra_yeah17:35
* ogra_ looks at the full code ...17:35
ogra_who wrote that code originally ?17:38
ogra_(why are there all these brackets ?)17:38
sergiusensogra_: mvo did17:38
Saviqjdstrand, I know you'll hate me, but I'll need an ACK for emonhub.saviq please, same old same old (but I renamed the app...)17:38
sergiusensogra_: interesting, hashes thing seems to be fine for armhf builds17:38
sergiusensogra_: I just need to fix that type; on 15.04, hardware.yaml is only used by the bbb17:40
ogra_well, i think the brackets cause all that stuff between them to be executed in a subshell (which seems a bit ppointless but doesnt explain why you end up with empty vars in the here doc)17:40
sergiusensogra_: the parens you mean?17:41
ogra_yeah17:41
sergiusensunspecific germans, sigh :-P17:41
ogra_i dont really get why mvo used them17:41
jdstrandSaviq: no worries. I think pindonga said the store would be updated today17:42
sergiusensogra_: http://paste.ubuntu.com/11842767/17:45
jdstrandSaviq: it isn't downloading right17:46
sergiusensogra_: I think I prefer that17:46
jdstrandSaviq: I get just an empty file17:46
ogra_sergiusens, yeah ... and add quotes around the $()17:46
sergiusensogra_: ok17:46
jdstrandbeuno: looking at https://myapps.developer.ubuntu.com/dev/click-apps/3029/review/, if I try to download I only get an empty file17:46
beunojdstrand, yes, slight issue atm17:47
jdstrandbeuno: is there an issue with the store?17:47
beunowill ping back17:47
jdstrandah, ok17:47
jdstrandSaviq: ^17:47
sergiusensogra_: http://paste.ubuntu.com/11842781/17:47
beunofor a handful of packages17:47
* sergiusens dputs17:47
ogra_sergiusens, thats schnappy :)17:47
sergiusens\o/17:48
sergiusensogra_: I might need one more fix to make this bullet proof17:49
ogra_sergiusens, well, and a "cat $TMPDIR/hardware.yaml" at the end of the script to get it into the log might not do harm either17:50
ogra_saves you from having to install an image to find out the file is brooken17:50
ogra_-o17:50
ogra_(or download or whatever)17:50
jdstrandsergiusens: there are ubuntu personal images now?17:54
jdstrandsergiusens: cause we need to figure out how to deal with security policy in snappy build17:55
kyrofajdstrand, yeah, seb128 has been working on them17:55
elopiosergiusens: did you find the rev# of the old kernel?17:55
jdstrandsergiusens: since my plan was to use existing phone policy for ubuntu-personal17:55
sergiusensjdstrand: yes there are17:56
jdstrandsergiusens: so that means snappy build needs to know about core vs personal and pick the right policy vendor17:56
sergiusensjdstrand: and seb128 is creating/seeding all the bits17:56
sergiusensjdstrand: yes, I've proposed adding a --release to Chipaca and mvo17:56
jdstrand(not to mention we need to work out what to do for policy version instead of just hardcoding 15.0417:56
jdstrand)17:57
jdstrandok, cool17:57
utlemmingsergiusens: er, looks like build 119 broke cloud images17:57
utlemmingsergiusens: sgdisk is needed in for cloud-init to resize the disk17:57
sergiusensutlemming: is that rolling or 15.04?17:57
utlemmingsergiusens: 15.0417:58
ogra_utlemming, where does that dep come from all of a sudden ?18:01
ogra_(also did you consider making it a dependency of the cloud-init package then ? )18:01
utlemmingogra_: that is likely my fault of not catching it in cloud-init logs -- my apologies18:03
utlemmingogra_: checking on the dep piece18:03
ogra_utlemming, well, i dont get why it worked before in 15.04 and in 119 it doesnt18:03
utlemmingorga_: yeah, lets hold on that for a minute...let me dig deeper before calling it the cause18:04
ogra_doesnt look like we ever had gdisk installed18:04
beunojdstrand, fixed18:04
jdstrandthanks!18:04
sergiusensogra_: http://paste.ubuntu.com/11842889/18:07
ogra_sergiusens, looks good ... go ahead18:08
sergiusensogra_: rsalveti seems to be one problem still and I'm not sure how to solve; but if we pull a new initrd and no new kernel, then s-i would remove the kernel from the delta and the upgrade would fail18:08
ogra_hmm18:09
kyrofasergiusens, looking at the snappy examples in contract to the snappy document, can I safely assume that .svg icons are no longer required even though the docs say so?18:10
sergiusensogra_: it's almost as if s-i should generate the hardware.yaml18:10
sergiusenskyrofa: I don't attest to that; I'll leave that to beuno18:11
sergiusenskyrofa: we are mostly killing package.yaml in the future btw...18:11
utlemmingogra_: red-herring18:11
kyrofasergiusens, ah, good to know. Is there other docs I should be referring to to build snaps, then?18:12
sergiusenskyrofa: well, if you are targetting rolling, the docs on developer.u.c are not what you want18:12
sergiusenslp:snappy /docs18:12
sergiusensbut I don't think there is anything in place yet18:13
kyrofasergiusens, I am indeed. Thank you!18:13
sergiusenskyrofa: rolling has no docs yet and anything is subject to change ;-)18:14
rsalvetisergiusens: why would the upgrade fail?18:15
kyrofasergiusens, that's alright, I can roll with it18:15
utlemmingogra_: the reason I wasn't seeing the error before was that with /etc/cloud/cloud.cfg.d being a writable path, the regular configurations where not being read when I built an image with that content populated.18:17
utlemmingi.e I put stuff in /writable/system-data/etc/cloud/cloud.cfg.d18:18
ogra_ah18:18
sergiusensrsalveti: because now the opposite happens, during the livecdrootfs phase we don't know what will be added or removed, so we add a kernel and initrd entry18:18
ogra_yeah, understood18:18
sergiusensrsalveti: but s-i might determine that initrd doesn't need to be in th delta18:18
sergiusensrsalveti: so the entry would point to an invalid file18:18
sergiusensrsalveti: as I was telling ogra, it feels like livecdrootfs is the wrong place to generate this file and it should be done during s-i18:19
rsalvetiright, indeed18:19
rsalvetisergiusens: so what can we do for now?18:20
sergiusensrsalveti: update both18:20
sergiusensrsalveti: or none18:20
sergiusensrsalveti: this problem exists in rolling as well18:21
rsalvetiguess just update both18:21
rsalvetiright, maybe not something we need to fix for this stable release18:21
ogra_well, how do you update both if one didnt change ?18:21
rsalvetisince your fix should already be enough for the current issue18:21
ogra_in snappy ?18:21
sergiusensogra_: generated images should update both init and kernel or the updates would fail18:22
ogra_sergiusens, right, but how do you enforce that ?18:22
ogra_if one of them is missing thanks to s-i18:22
sergiusensogra_: we control the stable channels, so it is easier18:23
sergiusensogra_: in the end, if we want to survive, we would need to have s-i generate the hardware.yaml18:23
ogra_yes18:24
rsalvetisergiusens: yeah, stable is fine for now I'd say, but definetly something we need to fix in s-i18:37
rsalvetisergiusens: just create a card for it and put it in the backlog18:37
sergiusensrsalveti: card created, I need to leave for a bit18:43
rsalvetisergiusens: sure18:43
rsalvetisergiusens: did you trigger a new image with your recent change?18:43
ogra_yes, he did18:44
* ogra_ cancels the arm64 build18:44
rsalveticool18:45
Letozaf_hey guys, once you installed packages like snake, and chatroom, for instance, If I do not know them and how they work, how can I find out? Is there some documentation somewhere, if I have to check if they work after install I have to know how they work.18:55
ogra_Letozaf_, webdm is supposed to show descriptions and also have a link that opens their externally defined port18:56
ogra_the description stuff is still broken i think18:56
Letozaf_ogra_, I will try again, but yesterday the link did not open anything, just a blank browser page18:57
ogra_for which app ?18:57
Letozaf_ogra_, yesterday I install snake and chatroom, just these two, but could not try them out18:58
ogra_hmm, works fine here ... i click on "raspberyy pi2" in webdm ... then on chatroom ... and there on open/manage18:58
ogra_that opens the chatroom page for me18:59
Letozaf_ogra_, I will try again just now, give me two minutes18:59
ogra_sure18:59
ogra_(note that chatroom only works in chromium ... (which the description would tell you if it would be shown :P ))19:00
ogra_sergiusens, rsalveti, hmm, that didnt work it seems19:03
ogra_https://launchpadlibrarian.net/211130437/buildlog_ubuntu_vivid_amd64_ubuntu-core-system-image_BUILDING.txt.gz19:03
ogra_oh19:03
ogra_ignore that :P19:03
ogra_wrong arch :P19:04
ogra_hmm, doesnt look like the "cat hardware.yaml" is executed19:05
Letozaf_ogra_, I am running yesterday's snappy 15.04 amd64 image (ubuntu-core vers. 117) I installed chatroom and in  Chromium when I click on "open/manage" I get "The webpage is not available" message19:05
ogra_weird19:06
rsalvetiogra_: cat should only show up on armhf, right?19:06
Letozaf_ogra_, I am runnin wily on my Desktop PC19:06
ogra_Letozaf_, http://webdm.local:656519:06
ogra_try that19:06
ogra_rsalveti, right, but it doesnt19:06
Letozaf_ogra_, same: This webpage is not available19:07
ogra_i can see the hashes being assigned to the vars though19:07
ogra_but that worked before already19:07
ogra_Letozaf_, weird, works fine on armhf ... i havent tried on amd64 in a while i must admit19:07
rsalvetiogra_: indeed19:08
rsalvetiogra_: guess we can open the device tarball and see19:08
Letozaf_ogra_, I have Wily installed and I am also using systemd19:08
ogra_yeah :/ ... thats what the cat was supposed to avoid19:08
ogra_but cats never do what you want :P19:08
Letozaf_am I the cat ? LOL19:09
ogra_lol19:09
ogra_meow19:09
ogra_no :)19:09
ogra_Letozaf_, a "cat" command that is supposed to put stuff in a logfile ;)19:10
Letozaf_ogra_, Hah! the cat command I thouth you were talking about a cat animal lol19:11
Letozaf_lolololo19:11
Letozaf_rotfl19:11
ogra_:D19:11
elopioppisati: ogra_: http://paste.ubuntu.com/11843280/19:11
elopiowas that what you wanted me to compare? How to know if it's correct?19:11
ogra_elopio, well, does it boot from a ?19:11
elopioand ogra_, it tries to boot first a, then it tries b. And keeps retrying be.19:11
ogra_if ti is in that state19:11
ogra_ah19:12
ogra_and both print that dtb error ?19:12
elopiowhat I pasted before was not the first try.19:12
ogra_well, i'd like to see the error from an a boot19:12
ogra_before it panics and reboots19:13
elopiolet me see if I pasted that one somewhere.19:13
elopionop. I hate that I can't scroll back on screen.19:14
elopioI will reproduce it one more time.19:14
ogra_partition-layout: system-AB19:17
ogra_hashes: 462b31071b9f41c50ef05670ca764780-9b0c722b5d417f5152a4f5a5d508491019:17
ogra_dtbs: assets/dtbs19:17
ogra_rsalveti, sergiusens ^^ looks fine19:17
rsalvetiogra_: yeah, now to test the upgrade and see :-)19:18
ogra_argh19:18
ogra_but we have everything duplicated in assets19:18
ogra_that makes it 52MB big now19:18
rsalvetiwhat19:20
ogra_initrd.img and initrd.img-3.19.0-22-generic ...19:21
ogra_same for the kernel19:21
Letozaf_ogra_, it works, it was a port redirect error :-P19:21
ogra_ha !19:21
ogra_Letozaf_, awesome :)19:22
Letozaf_ogra_, sorry for the hassle :)19:22
ogra_np19:22
ogra_i do that all the time when using kvm :)19:22
Letozaf_:-)19:22
ogra_rsalveti, wow, an we ship each and every available dtb by default19:22
ogra_8MB of dtb files19:22
rsalvetiogra_: right, at the kernel snap that is expected19:23
ogra_once that exists, yeah19:23
rsalvetiwell, it's the evolution from the device tarball :-)19:24
ogra_evolution ... like growing a third arm to pick your nose and such :P19:25
* ogra_ likes that the device tarball is small and on the point ... 19:26
ogra_but for generic thats probably fine ...19:26
rsalvetiright19:28
ogra_though wasting 25MB for the kernel and initrd duplication doesnt feel right19:30
ogra_i wonder if we can safely drop the unversioned ones19:31
ogra_hmm, no .. hardware.yaml uses them by default19:32
Saviqthe 'services' and 'no-cloud' config options from https://developer.ubuntu.com/en/snappy/guides/oem/ are a wish for now, right?19:37
elopioogra_: http://paste.ubuntu.com/11843609/20:00
elopiothat's the first error booting a after the second update. Same badlayout.20:01
ogra_elopio, so the dtb file is corrupt in general20:01
elopioI wonder if two real updates in a row end up in this too20:01
elopioI'll have to wait for tomorrow to check that.20:01
rsalvetican't we specify the version we want to update?20:03
rsalvetiif this indeed causes an issue, we might just break everyone that is using bbb :-)20:03
elopiorsalveti: not without faking things.20:04
elopiofgimenez did a script to update to rev -120:04
rsalvetiright20:04
elopioFull adventure logs:20:05
elopiohttp://paste.ubuntu.com/11843622/20:05
elopiohttp://paste.ubuntu.com/11843624/20:05
elopioI don't know how remounting / could cause this. I'll flash 94, update to 95, and wait for 96 to be available.20:06
rsalvetiwe can trigger a new wily one if you want20:06
rsalvetilet me do that while you flash 9420:07
elopiorsalveti: wait for me to finish the update to 9520:07
rsalvetielopio: sure, on your command :-)20:07
elopioit will take like ~30 minutes here to do the whole dance.20:07
rsalvetiright, probably the same time it takes to get the new image out20:07
elopiorsalveti: I'm in #95. go, please.20:25
rsalvetielopio: done20:26
elopiooh shit. The reboot ended up in emergency mode.20:27
rsalvetiman, we got some serious issues with bbb20:27
elopioI bet when I decided to work in QA, all the bad karma came in my aid.20:27
ogra_rsalveti, serious and weird20:28
elopiofwiw, federico could reproduce the second update issue.20:29
elopioand I haven't had an emergency mode for two weeks now.20:29
ogra_rsalveti, btw, do we have any complelling reason to use vfat and not ext2 ? we always seem to have issues with files on the fat20:31
rsalvetinot sure, would need to ask lool I guess20:31
rsalvetiprobably because vfat is usually supported everywhere20:31
rsalvetieven with super old uboot20:31
ogra_yeah20:32
ogra_but we insist on the very latest uboot :)20:32
rsalvetiright, which is why would be good to check with lool20:32
ogra_and we use very new features too20:33
ogra_bah, crap20:42
ogra_wily needs the same change in livecd-rootfs20:43
Saviqis there a place recommended to file bugs about docs?20:43
ogra_+ cp -ar boot/initrd.img-* /tmp/tmp.MYidIUKLNU/assets/20:44
ogra_cp: cannot stat 'boot/initrd.img-*': No such file or directory20:44
ogra_E: config/hooks/500-move-kernel-to-device-tar.binary failed (exit non-zero). You should check for errors.20:44
ogra_P: Begin unmounting filesystems...20:44
ogra_grrrr20:44
elopioSaviq: about docs in developer.ubuntu.com?20:46
Saviqelopio, yeah20:46
elopioSaviq: https://bugs.launchpad.net/developer-ubuntu-com/20:47
Saviqelopio, thanks20:47
elopioSaviq: please link the bug here.20:47
kyrofajdstrand, so if I write a dbus service, I'm getting the impression that it _must_ be a framework. Yes?20:47
jdstrandyes20:48
jdstrandbus-name is only available to frameworks20:48
kyrofajdstrand, right, okay. Does that immediately mean that I need custom apparmor profiles? All the service does is obviously listen on dbus and act as a network client20:49
elopiough, this is no good. Tried again and I'm in emergency mode. It's good I ordered more sd cards.20:50
elopiocan somebody try a bbb update from rolling edge #94?20:50
Saviqbug #147277820:50
nothalBug #1472778: "start exploring snappy..." link feels broken <Ubuntu Developer Portal:New> <http://launchpad.net/bugs/1472778>20:50
ubottubug 1472778 in Ubuntu Developer Portal ""start exploring snappy..." link feels broken" [Undecided,New] https://launchpad.net/bugs/147277820:50
jdstrandkyrofa: that isn't enough-- you need to have dbus bus policy to start a dbus service. I'm confused though-- why does an app need to be a dbus service?20:50
elopioSaviq: :) would you think it's better to link directly to the snappy tour instead?20:52
Saviqbug #147278020:52
nothalBug #1472780: No documentation about "assign" in oem guide <Ubuntu Developer Portal:New> <http://launchpad.net/bugs/1472780>20:52
ubottubug 1472780 in Ubuntu Developer Portal "No documentation about "assign" in oem guide" [Undecided,New] https://launchpad.net/bugs/147278020:52
Saviqelopio, TBH I'd just drop the link20:52
Saviqelopio, you're looking at "Next steps" by the time you're clicking it already20:52
ogra_sergiusens, fixed a quoting issue with the wily livecd-rootfs MP, uploaded20:53
elopioSaviq: done.20:53
rsalvetiogra_: thanks for uploading the fix20:53
kyrofajdstrand, it's the scope to install snaps for ubuntu personal. Scopes can't maintain state, thus the stateful bits are pulled into a dbus daemon20:54
kyrofajdstrand, so there are two parts-- the dbus daemon and the scope itself20:55
Saviqbug #147278220:56
nothalBug #1472782: webcam guide's assign/part-id does not work <Ubuntu Developer Portal:New> <http://launchpad.net/bugs/1472782>20:56
ubottubug 1472782 in Ubuntu Developer Portal "webcam guide's assign/part-id does not work" [Undecided,New] https://launchpad.net/bugs/147278220:56
Saviqelopio, ↑ that might be really a snappy bug, but it's unclear without real docs about assign20:56
ogra_rsalveti, so i guess it will still take a while til there is something to copy to the alpha channel20:56
rsalvetiogra_: yeah, not today20:56
ogra_cool20:57
rsalvetiit's all fine and good until we start finding blockers all around20:57
ogra_(or not)20:57
elopioSaviq: thanks for the bugs. I'm not sure, so I'll left them for somebody to triage.20:59
Saviqbug #147278320:59
nothalBug #1472783: oem guide mentions unsupported config parameters <Ubuntu Developer Portal:New> <http://launchpad.net/bugs/1472783>20:59
ubottubug 1472783 in Ubuntu Developer Portal "oem guide mentions unsupported config parameters" [Undecided,New] https://launchpad.net/bugs/147278320:59
Saviqelopio, there's some indentation issues on https://developer.ubuntu.com/en/snappy/guides/appliance-builder-guide-webcam/20:59
elopiowe are trying to fix the doc bugs before the next release.20:59
Saviqelopio, in the yaml listings21:00
Saviqbug #147278421:01
nothalBug #1472784: oem guide does not explain immutable config properly <Ubuntu Developer Portal:New> <http://launchpad.net/bugs/1472784>21:01
ubottubug 1472784 in Ubuntu Developer Portal "oem guide does not explain immutable config properly" [Undecided,New] https://launchpad.net/bugs/147278421:01
jdstrandkyrofa: why wouldn't this be shipped as part of the ubuntu personal image like it is on touch?21:05
kyrofajdstrand, it can be. We figured it would be easier to update if it was a snap21:06
kyrofajdstrand, do you disagree?21:07
jdstrandkyrofa: you can't right now. today, you must be framework to be able to be a dbus service21:07
jdstrandkyrofa: note you can't do this as a click either21:08
jdstrandkyrofa: because you need to adjust dbus bus policy (ie, not apparmor) in order to be a service21:08
jdstrandthere is no current mechanism to do that (unless you are a framework snap)21:08
kyrofajdstrand, is it a big deal for it to be a framework snap?21:09
jdstrandkyrofa: I suggest for now keeping it in ubuntu personal image and bringing this up with the architects group21:09
jdstrandkyrofa: it isn't a framework though, is it? you just are picking it as type framework because that happens to get you something you need21:10
jdstrandwhich I understand why you are doing that21:10
jdstrandI'm just saying that all the use cases for ubuntu personal have not been defined21:10
elopioSaviq: I only see the wrong identation on "build-in:"21:10
elopioam I missing another?21:10
Saviqelopio, that might've been it, checking21:10
kyrofajdstrand, yeah, it's really quite minimal, but apparently the only way to use dbus is to be a framework, that's all21:10
jdstrandand so there aren't appropriate mechanisms for you to use21:11
kyrofakgunn, are you still around? ^^21:11
Saviqelopio, - kernel: video* is 3 spaces in21:11
Saviqand that seems to be it21:12
jdstrandkyrofa: it might be that we want to allow bus-name in app types but trigger a manual review. I don't know (again, architects group (aka, tvoss))21:12
* jdstrand -> meeting21:12
kgunnkyrofa: i am...21:13
elopiommm, ok, that one comes from the source. Will propose a change in there.21:13
elopioand the built-in seems to be playing funny tricks with the editor.21:13
jdstrandkyrofa: it might be worth noting that snaps aren't meant to replace debs in a 1 to 1 fashion. this is providing a service to a specific something. perhaps put all those somethings into one snap and make that a framework (still, need architect's direction)21:14
jdstrandkyrofa: frameworks are strictly defined:21:14
davidcalleSaviq, elopio, I've just imported the latest stable oem doc, don't touch the page :p21:14
Saviq;)21:15
davidcalleSeriously :)21:15
* kgunn wonders why Saviq is here :)21:15
jdstrandkyrofa: https://developer.ubuntu.com/en/snappy/guides/frameworks/21:15
Saviqkgunn, Orange Matchbox ;)21:15
elopiodavidcalle: I'm not touching the oem page21:15
kgunnah21:15
jdstrandkgunn: he's keeping me busy :P21:15
kgunnfun21:15
Saviqam monitoring my energy use!21:15
* jdstrand iskidding (happy to help)21:15
davidcalleNote that we are working on auto-import for stable and edge snappy docs. In ~two weeks or so.21:15
Saviqoops21:15
Saviqjdstrand, but but but!21:16
* Saviq is filing bugs for you all!21:16
Saviqbugsies21:16
Saviqso many bugsies21:16
kyrofajdstrand, I gotcha. Yeah, I definitely don't need a framework... I guess I didn't expect dbus to be limited to frameworks is all21:16
kgunnkyrofa: i wouldn't have expected that either...thanks for poking21:16
kyrofakgunn, so the scope is two pieces-- the scope itself and a little dbus daemon for maintaining state. The docs and jdstrand point out a dbus service is only supported for frameworks, which is way overkill for this21:18
jdstrandkyrofa: well, a dbus service is a service to other apps21:18
kgunnkyrofa: sure...21:19
kgunnjdstrand: but in a generic case, "apps" using dbus are consuming that service no ?21:19
kgunnat least, i'd have thot if you provide a service you have to be an app....21:19
kyrofakgunn, yes, but in that case they depend on the framework and have a capability inherited from the framework21:20
kgunndang it...i mean fmwk21:20
kgunnkyrofa: so in turn "they" proxy dbus? in that case i do understand21:20
jdstrandkgunn: apps may use a service if they security policy allows it. that policy is expressed via framework-policy21:21
jdstrandkgunn: or via system supplied policy21:21
jdstrandkgunn: right now on touch, we have a bunch of dbus services that are shipped as part of the image, and the image ships security policy that apps may specify to use it21:22
jdstrandkgunn: but the services themselves aren't shipped as clicks21:22
kyrofajdstrand, so the only way to update them is OTA, yes?21:23
jdstrandkgunn: it is the same on snappy. things that ship services to other apps either need to be in the image or shipped as framework snaps21:23
jdstrandkyrofa: if on the image, yes. just like on touch21:23
jdstrandkgunn: my understanding was that the ubuntu personal image was going to be a big image (compared to core) like it is now on touch, as opposed to a collection of snaps on top of core21:24
kgunnjdstrand: yep, and no problem, i think kyrofa can continue down the "it's just in the image" road....21:24
jdstrandkgunn: if the latter, then we really need to get the architects talking about things with the various stakeholders (core, security, etc)21:25
kgunni was just curious about the dbus use mandating a thing be a fmwk....21:25
kyrofakgunn, jdstrand indeed I can. debs are easy21:25
jdstrandkgunn: well, it is because apps aren't supposed to be services to other apps21:25
jdstrandkgunn: apps are isolated21:26
kgunngot it21:26
jdstrandkgunn: consider this-- if we did make it so that an app could ship a dbus service and that service could listen on the dbus, no other apps would be able to talk to it because there is no security from them to declare to talk to it21:26
jdstrands/no security from/no security policy for/21:27
kyrofajdstrand, except a binary shipped in the same snap, yes?21:27
jdstrandyes21:27
jdstrandyou can always do that21:27
kyrofajdstrand, which is exactly what I need21:27
jdstrandok, well, you can setup a private dbus21:27
jdstrandand not use the system one. it would be a private session bus21:28
kgunn:P21:28
kgunnplease allow myself to talk to myself21:28
jdstrandactually, that won't work just yet21:28
jdstrandyou would need the 'sockets' stuff that isn't implemented yet21:28
jdstrandactually, perhaps just an abstract socket unix rule that is namespaced...21:29
jdstrandI need to think about that21:29
* jdstrand makes note21:29
jdstrandanyhoo, that isn't available today21:29
kyrofajdstrand, alright, not a big deal, getting it in the image is easy enough, just a little more work for seb21:30
jdstrandkgunn: today, you can setup a writable named unix socket in the snap's writable area and have apps communicate over that21:30
jdstrandbut that is probably more work than just putting it on the image21:30
kyrofakgunn, do you think the long-term vision is having this as a snap, or leaving it in the image? If we want it as a snap eventually it sounds like we should start talking to people21:31
jdstrandok, meeting for real now21:31
kyrofajdstrand, :P21:31
kyrofajdstrand, thanks for all your time!21:31
jdstrandnp21:31
kgunnkyrofa: honestly, it kinda feels like it'll always be in the image ? i mean at some point21:33
kgunnwe'll go all snaps all the time21:33
kgunnand we'll always need a scope installed for the store21:33
kyrofakgunn, yeah, it's kinda integral21:33
kgunnfeels more like a nice to have21:33
kyrofakgunn, agreed21:34
kgunnin terms of it being a snap21:34
kgunnbut thanks for trying21:34
kgunnthese are great attempts, we always learn a little more :)21:34
kyrofakgunn, definitely! Okay, I'll invest some time making sure I've got a good .deb coming out of the CI then instead21:35
kyrofakgunn, thanks for letting me drag you in! :)21:35
=== j12t_ is now known as j12t
kgunnkyrofa: thank you!21:45
Saviqlooking for +1s on bug #1472797, anyone?21:54
nothalBug #1472797: Should use bmap or a bmap-like solution to reduce flashing time <goget-ubuntu-touch (Ubuntu):New> <http://launchpad.net/bugs/1472797>21:54
ubottubug 1472797 in goget-ubuntu-touch (Ubuntu) "Should use bmap or a bmap-like solution to reduce flashing time" [Undecided,New] https://launchpad.net/bugs/147279721:54
Saviq;)21:54
Saviqhmm where do I file bugs against ubuntu-core?22:01
jdstrandSaviq: the snappy project is prbably a fine first choice22:02
fjayshould /var/lib/apps/<pkgname>/current/22:07
fjayexist?22:07
fjayw/ the proper packagename obviously22:07
fjayor has that approch been deprecated and the docs do not reflect that.22:07

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