[05:37] <tbr> rsalveti: I'm trying to understand how I'd be supposed to do this: https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/1425370/comments/4 - It has been established that building your own image is effectively impossible and as the image doesn't contain dpkg.
[06:18] <dholbach> good morning
[09:07] <Chipaca> tbr: what are you trying to do?
[09:08] <tbr> Chipaca: ultimately I'd like to boot snappy on this embedded linux device that has uefi based firmware.
[09:09] <tbr> that says there is a fix and even built, but that points to a package, how do I go from that to a snappy image.
[09:09] <JamesTait> Good morning all; happy International Nurses Day! 😃
[09:09] <Chipaca> tbr: goget-ubuntu-touch is the project that holds ubuntu-device-flash
[09:10] <Chipaca> tbr: does that answer your question?
[09:10] <Chipaca> JamesTait: ooh! i should call my mum
[09:10] <tbr> not really
[09:10] <Chipaca> tbr: tell me more :)
[09:11] <JamesTait> Chipaca, your mum is a nurse?
[09:11] <Chipaca> JamesTait: yep
[09:11] <Chipaca> JamesTait: well, she's now an OAP, but once a nurse always a nurse, right?
[09:12] <tbr> Chipaca: so, for x86_64 there is this: http://releases.ubuntu.com/15.04/ubuntu-15.04-snappy-amd64-generic.img.xz - it doesn't support UEFI.
[09:12] <Chipaca> tbr: did you install that package?
[09:13] <Chipaca> tbr: ubuntu-device-flash is what you use to build the images
[09:13] <tbr> Chipaca: I thought there was no dpkg on those images?
[09:13] <Chipaca> tbr: you don't install that package on the target, you install it on the host
[09:13] <tbr> ok. I'll have to install it and try to figure that out then
[09:15] <Chipaca> tbr: sudo ubuntu-device-flash core rolling --output amd64.img --developer-mode --channel edge
[09:15] <Chipaca> tbr: once you've got the ppa set up
[09:15] <Chipaca> tbr: that'll give you an "amd64.img" that you can run with kvm, or dd onto a device
[09:17] <Chipaca> tbr: to set up the ppa, you do this:
[09:17] <Chipaca> gah, can't link it
[09:17] <Chipaca> gimme a sec
[09:17] <Chipaca> tbr: well, it's explained in https://launchpad.net/~snappy-dev/+archive/ubuntu/tools?field.series_filter=vivid
[09:17] <tbr> don't worry
[09:17] <tbr> I can manage a ppa
[09:18] <Chipaca> tbr: basically, sudo add-apt-repository ppa:snappy-dev/tools  && sudo apt-get update && sudo apt-get install ubuntu-device-flash
[09:18] <Chipaca> tbr: ah, ok
[09:18]  * Chipaca always wonders why add-apt-repository doesn't do the update itself
[09:19]  * tbr wonders why add-apt-repository only reasonably works with PPAs and not with adding other repositories, but that's completely unrelated
[09:20] <tbr> oh, that's in 15.04 of that ppa only. time to boot a vm with that...
[09:20]  * tbr prefers LTS as the main machine
[09:21]  * Chipaca is upgrading to wily today
[09:21] <Chipaca> well, actually maybe next week when the rest of my team is back
[10:03] <tbr> ok, so one step closer.
[10:04] <tbr> it boots, but I have to manually kick fs0:\EFI\BOOT\BOOTX64.EFI
[10:09] <tbr> easily addressed by "echo fs0:\\EFI\\BOOT\\BOOTX64.EFI >startup.nsh" in the root directory of the EFI partition. Not sure if there is a "nicer" way
[10:14] <beowulf> Chipaca: would you like a review? i added a bem linter for webdm's css https://code.launchpad.net/~stephen-stewart/webdm/post-css-bem-lint
[11:01] <Chipaca> beowulf: on it
[11:14] <Chipaca> beowulf: http://pastebin.ubuntu.com/11094443/
[11:21] <beowulf> Chipaca: ooo
[13:23] <soothran> hey folks!
[13:23] <soothran> I am bit confused reading about snappy!
[13:24] <soothran> how can i (or can I) install Ubuntu snappy core in 32-bit pc?
[13:24] <soothran> not as a kvm image but directly.
[13:26] <thesheff17> I don't think you can right now soothran
[13:27] <thesheff17> its also server only really at this point
[13:28] <soothran> hmm..so why does it say it can be in x86 here (https://www.linux.com/news/embedded-mobile/mobile-linux/804659-ubuntu-snappy-leads-mobile-linux-migration-to-iot)
[13:29] <soothran> also in ubuntu website it says "Ubuntu Core can be installed directly on X86 or ARM devices" https://developer.ubuntu.com/en/snappy/
[13:30] <thesheff17> it might eventually have ISO but its super alpha right now
[13:30] <beuno> soothran, you can on amd64
[13:30] <beuno> the x86 builds have been failing lately
[13:30] <beuno> but I'm sure we'll get around to fixing them soon
[13:30] <beuno> not a lot of 32bit users left out there though!
[13:31] <soothran> i know it can be in ARM..but it is the x86 part that confuses me..
[13:31] <beuno> soothran, it works on intel as well
[13:32] <beuno> but just 64bit atm, the 32bit builds have been failing and we haven't gotten around to fixing them yet
[13:33] <soothran> thanks beunno..so my plain question will be "if i have a x86 intel laptop, is it possible to directly install ubuntu snappy core?
[13:34] <thesheff17> even if you could I would consider it very alpha
[13:34] <soothran> that's oke
[13:34] <thesheff17> why so set on installing snappy on old hardware?
[13:34] <soothran> I am not going to anyways, just wanted to know if it is possible
[13:34] <beuno> soothran, yes you will
[13:35] <beuno> all new laptops are 64bit
[13:36] <soothran> AFAIK, i am not able to burn the 64-bit snappy image from the repo (http://ftp.arnes.si/pub/mirrors/ubuntu-cdimage/vivid/)
[13:36] <soothran> into a usb and boot it. i think this is just hte kvm image or something?
[13:36] <soothran> that's why i was wondering how can i install it 'directly' in a computer
[13:44] <davmor2> soothran: why would you? if you want to experiment with snappy just install it in kvm, you will not have a desktop and you will have very limited set of applications.
[13:45] <davmor2> soothran: what's your actual plan for snappy
[13:46] <soothran> as i said i am not planning to do this thing..i am missing something here.
[13:46] <davmor2> soothran: and is this a throw away laptop, ie is it one that is sat there doing nothing and you want to put it to some use?
[13:47] <davmor2> soothran: if so then you can try just dd'ing the img file only the hdd not sure if that will work or not as I don't think there is an actual installer for it yet
[13:48] <soothran> nothing to be honest..all i wanted is a clarification on few sentences that I read. first one "Ubuntu Core can be installed directly on X86 (or ARM, i am sure about arm part)"
[13:48] <soothran> this one is from here ---> https://developer.ubuntu.com/en/snappy/
[13:49] <soothran> but there is no resources that points to a x86 image (or 64-bit image for that matter)  that can be 'directly' installed in a PC
[13:49] <davmor2> soothran: https://developer.ubuntu.com/en/snappy/start/ say kvm only
[13:52] <soothran> how about this one -----> https://www.linux.com/news/embedded-mobile/mobile-linux/804659-ubuntu-snappy-leads-mobile-linux-migration-to-iot
[13:52] <soothran> says "...while any x86 computer or VM should do the trick on the x86 side. (Here's a Dustin Kirkland tutorial on loading Snappy on the BeagleBone Black.)"
[13:52] <soothran> what's with the "any x86 computer" part?
[14:00] <davmor2> soothran: no idea I can only go by the stuff on the Ubuntu website as that will actually be updated but the fact that you can run in kvm on any x86 system might be what they are mis-understanding maybe
[14:01] <tbr> even the 64bit image  is not quite there yet for use outside kvm (with bios) and legacy bios HW. UEFI support is only getting added.
[14:08] <soothran> hmm
[14:08] <soothran> yeah may be
[15:38] <vmayoral|pc> pitti: I'm trying to figure out a way to create a snap from a ROS package. Do you have any thoughts on this?
[15:39] <vmayoral|pc> pitti: i guess that the most straightforward way is to scan the CMakeLists.txt of the ROS package and fetch/place the binaries under src/ of a new snap.
[15:42] <jdstrand> dholbach: hi! fyi, docs/security.md has been updated-- can you update the site? also, if you compare https://developer.ubuntu.com/en/snappy/guides/security-policy/ and https://developer.ubuntu.com/en/snappy/guides/frameworks/, you can see that the security page is not formatted correctly (there is no whitespace border around the page)
[15:43] <dholbach> I think davidcalle looked into this earlier? ^
[15:43] <jdstrand> dholbach: fyi, this is also pending: https://code.launchpad.net/~jdstrand/snappy/snappy.bus-name-docs/+merge/258894 (meta.md and frameworks.md)
[15:43] <dholbach> thanks jdstrand
[15:43] <dholbach> I'll talk with davidcalle tomorrow to think of a better solution than this
[15:44] <davidcalle> dholbach, +1
[15:44] <jdstrand> dholbach: I don't know if you want to review that MP so I can commit it and people can update those three pages at the same time
[15:44] <davidcalle> jdstrand, ouch for the security page, looks like a broken import. Fixing.
[15:44] <jdstrand> dholbach, davidcalle: thanks for looking into this
[15:45] <dholbach> jdstrand, I'm a bit preoccupied right now
[15:46] <jdstrand> dholbach: not a problem at all
[15:46] <dholbach> thanks jdstrand, thanks davidcalle
[15:49] <jdstrand> davidcalle: https://developer.ubuntu.com/en/snappy/guides/security-policy/ looks pretty again
[15:49] <davidcalle> jdstrand, :)
[15:52] <itsme_> so i am trying to install "wily-preinstalled-core-http://cdimage.ubuntu.com/ubuntu-core/daily-preinstalled/current/i386.tar.gz " from
[15:52] <itsme_> how to i go about creating a live USB with this file?
[15:52] <itsme_> is it possible at all?
[15:54] <pitti> vmayoral|pc: ah, hello; (tried to reply this morning, but you weren't online)
[15:55] <pitti> vmayoral|pc: my initial gut feeling would have been to build the ROS core as a framework, and make ROS apps depend on it, so that you don't always have to build/duplicate everything
[15:55] <pitti> vmayoral|pc: but apparently that very duplication is "by design" now :/
[15:56] <pitti> vmayoral|pc: as for building, I figure the tutorial build script that I did a few months back should be by and large apply to other modules too
[15:56] <pitti> join #ubuntu-meeting-2
[15:56] <pitti> oops
[16:11] <jdstrand> Chipaca: oh, you know, if the launcher is doing all the env var setting, then the bin-path and systemd bits go away and things are always in sync
[16:11] <jdstrand> Chipaca: you probably thought of that already, so, nice job! :)
[16:18] <Chipaca> jdstrand: :)
[16:18] <Chipaca> you'll laugh at the bit of code that made me avoid doing this in this mp before
[16:18] <Chipaca> it's the mkdir -p
[16:19] <jdstrand> heh
[16:20] <Chipaca> i've got to: make sure the appname and version have no /. build /tmp/snap.$UID. mkdir that. add the appname. mkdir that. add the version. mkdir that. add tmp. mkdir that. kill me now.
[16:20] <Chipaca> each thing with its error checking of course
[16:20]  * Chipaca bites the bullet
[17:33]  * Chipaca gets bogged down
[17:34]  * Chipaca EODs while tests pass
[17:43] <jdstrand> mterry: did your question regarding snappy.bus-name-docs constitute a review?
[17:44] <mterry> jdstrand, sure?  It was the only thing I noticed.  I'm not qualified to comment on content itself, but for presentation, that's all I saw.  rest is good  :)
[17:45] <jdstrand> mterry: thanks
[17:45] <mterry> jdstrand, I noticed you pushed the other branch directly -- do we not use CI for snappy?
[17:45] <jdstrand> tbh, I think I am the only person qualified to comment (I implemented/designed said feature and wrote the review tools checks :)
[17:45] <jdstrand> mterry: not currently
[17:46] <jdstrand> I imagine that is something that might change in the coming weeks as we got more organized
[17:46] <jdstrand> there is tarmac
[17:46] <jdstrand> I should probably set to 'approve' and let it do its thing
[17:46] <mterry> jdstrand, and as for my comment about quotes -- is that line the same with or without quotes in yaml?
[17:46] <jdstrand> of course, in this case, it is only docs changes
[17:47] <jdstrand> mterry: oh I commented on that-- it should've been quoted. fixed
[17:47] <mterry> jdstrand, so what would it be if yaml parsed it without the quotes?  (i.e. how does it parse bus-name which doesn't have quotes?)
[17:49] <jdstrand> mterry: quotes force it to be parsed as a string. '<' and '>' are apparently special in yaml, so we should quote
[17:50] <mterry> jdstrand, ok.  so bus-name will be recognized as a string since it's not an int and doesn't use reserved chars.  So doesn't *need* the quotes
[17:51] <jdstrand> right
[17:51] <jdstrand> just like with 'name'
[17:51] <mterry> cool
[17:51]  * mterry is not super familiar with yaml
[17:52] <ogra_> it is like txt :)
[17:52] <jdstrand> yeah, I'm not either. getting better at it
[17:53] <jdstrand> I guess I should say that I am familiar with it these days
[17:53] <jdstrand> but not an expert
[18:36] <bjf> i'm trying to build an amd64 image for an intel nuc. i'm looking for a device tar ball to use. where do i find one?
[21:41] <beowulf> ogra_: using node-snapper, it's complaining that the vivid images can't be found, s/vivid/wily seems to work
[22:15] <c-nv-s> test