=== chihchun_afk is now known as chihchun [06:55] morphis: hey [06:56] zyga: hey! [07:19] good morning [08:03] hello hello from mvo's place :-) === bigcat_ is now known as bigcat [08:11] morning :) [08:26] moinsen [08:26] Morning all. [08:27] We have a fix for cloud-init for snappy on Azure; where in the normal Ubuntu development lifecycle does this have to get for edge builds to pick it up? Will an upload to wily be sufficient? [08:33] Odd_Bloke, stable pulls from the official vivid archive (incl. sercurity and updates) and from https://launchpad.net/~snappy-dev/+archive/ubuntu/image [08:34] s/stable/15.04/ [08:34] rolling pulls from wily [08:37] ogra_: Cool, thanks. :) [08:39] * guest42315 they see me rollin' la la la [08:41] uh [08:41] my snapcraft build doesnt build anymore [08:41] Branched 4 revisions. [08:41] [1mIssues while validating snapcraft.yaml: [{'exec': 'usr/bin/bipmkpw', 'name': 'bipmkpw'}] is not of type 'object'[0m [08:41] Traceback (most recent call last): [08:41] what does that mean ? [08:45] did the definition for "binaries" change since yesterday ? [08:48] ogra_: I think so :/ [08:48] where is that documented then ? [08:48] ogra_: where is your project? could you push it somewhere? [08:48] ogra_: I hope in the snapcraft docs of the branch [08:48] * ogra_ is happy to make changes as long as he knows which :P [08:49] mvo, not really, thats onle the generic stuff from the website [08:49] ogra_: binaries:\n name: foo -> changes to binaries:\n foo:\n exec: foo" [08:49] ogra_: if you push your stuff I can have a look and help with the diff [08:50] ogra_: if its not documented we need to fix that too :/ [08:50] well, the docs dir in the snapcraft tree has exactly the two pages we have on developer.u.c [08:50] not sure there are other docs hidden anywhere [08:52] bah, and the services description changed too it seems [08:54] ah, got it by blindly poking around [08:54] (and by looking at the schema file) [08:56] and hello snappy-bip ! [09:36] Good morning all; happy Thursday, and happy Punctuation Day! 😃 === ogra2 is now known as ogra-snappy-test [10:36] JamesTait: instead of punctuation day today I'm celebrating I've been a dad officially for 11 years and haven't killed anybody yet \o/ [10:36] 🙌 [10:36] congrats to the calmness ! [10:36] Chipaca, that definitely is cause for celebration! [10:36] Is there cake? [10:36] there is not. Because the boys are in France on a school trip. [10:36] \\\\\o////// [10:37] ;D [10:37] for the last 11 years no wonder you haven't killed them [10:37] instead i can stay hacking until 4am and not have to get up at 6 to kickstart their day :) [10:38] davmor2: har :) [10:38] davmor2: just this week :) [10:38] davmor2: for several of those years i couldn't afford the milk they needed, let alone fancy schmancy france :) [10:39] well. maybe it was a couple of months. felt like years :) [10:39] Chipaca: hahaha [10:40] kas1000, wherever you are, i hope your rabbits are all dead [10:41] clobrano: thanks to your branch we found we were misfiling the CLA emails, so double thanks for that :) [10:42] :D, I find also bugs I am not even looking for [10:56] clobrano: reviewed! [10:56] clobrano: needs fixing, but good job [10:56] clobrano: (i wouldn't be surprised if you told me the code you're replacing suffers from the same problems i called out in your code, fwiw) === chihchun is now known as chihchun_afk [11:10] clobrano: another alternative would be to write a couple of variations of the AtomicWrite helper, one for append, one with a line-at-a-time interface [11:10] or maybe write a whole atomic-writable type that did the whole dance behind the scenes [11:18] Chipaca: I'll have a look at it ;) [11:19] clobrano: fwiw I think you should do as i suggested in the review [11:19] clobrano: the other things can be done in later branches [11:19] Chipaca: ook [11:31] clobrano: sorry if the "atomic-writable file type" sounded very exciting [11:31] :) [11:31] * Chipaca would be tempted too [11:31] but that's how branches get un-reviewable [11:31] :D [11:32] well, actually I thought about using AtomicWriteFile, but I misinterpreted the description and didn't look at the code well [11:35] asac: ricmm: http://chipaca.com/post/129773078277/talking-http-to-an-abstract-unix-socket fwiw [11:36] asac: ricmm: as people trying to use the rest api have stumbled on this a bit [11:52] clobrano: https://github.com/dchest/safefile fwiw :) [11:54] pitti: when you have a bit of time, i've got a systemd question just for you [11:54] pitti: not urgent, not work related [11:54] trying to start a user unit on a udev event; have gotten the device to show up, but the user unit doesn't [11:57] Chipaca: what is your udev rule? [11:58] Chipaca: we do that quite a lot, usually through something like ..., ENV{SYSTEMD_WANTS}+="my_unit.service" [11:58] Chipaca: for those (SYSTEMD_WANTS) you need to add TAG+="systemd" so that systemd creates a .device unit for it [11:58] Chipaca: or you can call systemctl start --no-block in a RUN rule directly too, of course [12:01] pitti: sorry, xchat crashed and missed that, let me pastebin the bits i have [12:02] pitti: this is 99-batteries.rule: http://pastebin.ubuntu.com/12541325/ [12:02] pitti: which results in [12:02] sys-devices-LNXSYSTM:00-LNXSYBUS:00-PNP0C0A:01-power_supply-BAT1.device loaded active plugged /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:01/power_supply/BAT1 [12:03] pitti: and this is cbatticon@.service: http://pastebin.ubuntu.com/12541330/ [12:04] pitti: i tried with BindTo=%i.device also, and didn't have it work [12:04] Chipaca: BindTo= doesn't exist, you probably mean BindsTo= [12:05] Chipaca: but what is that supposed to do? the After= should already be implied [12:05] pitti: the internets told me to do it! [12:05] couldn't find documentation that mentioned BindTo [12:05] Chipaca: WantedBy= also seems redundant/unnecessary as you start this from an udev rule, not from a target [12:06] Chipaca: man system.unit [12:06] Chipaca: but aside from these nitpicks, what does it do? if you plug in the battery, what does systemctl status -l .. show? [12:06] Chipaca: i. e. does it get activated and fail, or not activated at all, etc? [12:07] pitti: it never shows up in systemctl --user status [12:07] Chipaca: why would it be in --user? [12:07] pitti: because SYSTEMD_USER_WANTS? [12:07] you start it through udev, that's system [12:08] Chipaca: oh sorry, I thought that's SYSTEMD_WANTS [12:08] pitti: the device unit does show up, as above [12:11] hey everyone [12:11] QUESTION: what's the difference between snaps and clicks? [12:11] hey! [12:11] we're building a small experimental framework [12:11] we're (morphis and me) using bluez 5.34 [12:11] Chipaca: ok, then I don't have an off-hand answer, I'm afraid [12:11] yay, bluez support ! [12:12] if anyone is interested to follow us, the code is currently in https://git.launchpad.net/~zyga/+git/snap-manual-bluez5/tree/ [12:12] guest42315: you can think of snaps as clicks v2 [12:12] ask us questions about this anytime if you are interested [12:12] Chipaca: "systemd-analyze set-log-level debug", and watching the journal while you plug in the battery might be insightful [12:12] guest42315: also, HELLO, why the QUESTION format? :) [12:12] click is in "maintenance mode" [12:12] snap is actively going forward [12:13] morphis: passing bt via -bt hci,host didn't work [12:13] morphis: I'll try -bt hci,null [12:13] zyga: for too [12:13] morphis: just to see if there's anything on the inside [12:13] fails with a: qemu: `hci0' not available [12:13] morphis: for too? [12:13] Chipaca, oh, is not live yet? [12:13] morphis: oh, where did you see that [12:13] pitti: found BindsTo, dunno why i was reading it as BindTo all the time (and unable to find it like that) [12:13] morphis: in my branch I have redirected qemu lots [12:13] logs* [12:14] morphis: so that they don't spam the terminal [12:14] morphis: but Ididn't see anything about hci [12:14] (I think) [12:14] guest42315: 12:30 utc is in 17 minutes [12:14] morphis: trying now with: qemu-system-x86_64 -m 768 -nographic -snapshot -redir tcp:8022::22 -bt hci,null kvm.img >qemu-serial.log & [12:15] oh, soon then [12:15] so Chipaca .. what would be the name for v3? v1 is clicks, v2 is snaps, [12:15] guest42315: claps ;) [12:16] guest42315: pops [12:16] guest42315: poofs [12:16] no no no [12:16] guest42315: booms [12:16] guest42315: kapows [12:16] probably not "no no nos", no [12:16] Cracks [12:16] ^^ +1 [12:17] As in "I'm addicted to updating, I just have to have the latest Crack." [12:17] hehe [12:17] JamesTait: heh :) [12:18] or maybe we sell out and call it the Big CoproporationTM Asynchronous Atomic Secure Boring System And Package Maintenance Agent, or bcaasbsapma for short [12:19] home edition? [12:19] * Chipaca would not put any chits on that number [12:19] guest42315: the home edition would let you use more than one core at a time! [12:19] guest42315: for only 99 a month more [12:19] :))) [12:19] 10 min left [12:19] yep :( [12:19] :-) [12:20] zyga: problem solved, do a sudo hciconfig hci0 up [12:20] dholbach: you have people queueing up to see you. It's the price of fame I'm afraid. [12:20] but before: systemctl stop bluetooth [12:20] Chipaca, they all want to see sergiusens [12:20] dholbach: ah. So you're the bass player in the group, I see. [12:21] Drummer. 😉 [12:21] ohh [12:21] I'm such a dummie [12:21] I kept running the old snap :) [12:21] morphis: so what is that with host or null? [12:21] with host [12:21] push a chnage in a minute [12:21] pitti: do i have to "enable" the @.service, or is that automatic? [12:21] Chipaca, JamesTait: works for me - hip hip chin chin to the rhythm section [12:22] * JamesTait is the roadie or something. [12:22] zyga: pull [12:23] morphis: nice! [12:23] we could also use vhci support if we want [12:23] morphis: trying [12:23] morphis: what is vhci exactly? [12:23] qemu seems to have support for that [12:23] a virtual HCI device [12:23] Chipaca: no, if you start it from udev you don't want/need to start it at boot (which is what enabling does -- you say that some target that is already started at boot pulls in that) [12:23] morphis: is it a totally virtual bt [12:24] yes [12:24] morphis: or some sort of sharing from the real one [12:24] morphis: can we boot two qemu boxes [12:24] no, totally virtual [12:24] morphis: and have them talk over those virtual bts? [12:24] never tried that [12:25] I'll check that passthrou works [12:25] morphis: what do we do next if this works? [12:25] zyga: verify if we find any available bluetooth devices :) [12:26] morphis: ok, let's see [12:26] doing that already [12:26] morphis: mine stil boots [12:26] hm [12:26] why doesn't the bluetooth device appear [12:28] morphis: is it possible that we need udev rule for something [12:29] it isn't in /sys [12:29] that is where it should be [12:29] there is no bt device in 7dev [12:30] morphis: where should it be in /sys/ ? [12:30] sys/class/hci or somethingf? [12:30] (slow slow slow) [12:30] /sys/class/bluetooth [12:30] QUESTION: can i install snappy on my home router? [12:30] morphis: yep, it is empty [12:31] just about to start [12:31] morphis: any modules we might be missing? [12:32] live [12:32] morphis: what does your systemctl status say? mine says degraded [12:32] yay [12:32] wave o/ [12:32] live :) [12:32] install snappy on a toaster! live [12:32] zyga: rebooting .. [12:33] o/ [12:33] morphis: where do logs go? syslog or dedicated [12:33] zyga: that is what I am not sure about [12:33] trying to figure out how this bt forwarding works [12:33] journalctrl or syslog [12:33] (both atm) [12:33] starcraft? [12:34] snapcraft is our start, yes [12:34] *star [12:34] :) [12:34] :D [12:34] zyga: some documentations says only the M800, M810 qemu machine type has a emulated hci ctrl [12:34] morphis: I think the mistake is that we switch off bluez on the host [12:34] morphis: (bluez only) The corresponding HCI passes commands / events to / from the physical HCI identified by the name id (default: hci0) on the computer running QEMU. Only available on bluez capable systems like Linux. [12:35] "The Transport Layer is decided by the machine type. Currently the machines "n800" and "n810" have one HCI and all other machines have none." [12:35] morphis: it seems that the actual hardware says on the host, what happens is tha the gues just sees some events injected by qemu? [12:35] no [12:35] morphis: ok, let's try USB pass-thru [12:35] the host interface needs to be on [12:35] morphis: that works for sure (we used it) [12:35] qemu will forward all HCI commands to the enabled host interface [12:35] Is there an gui for snappy? [12:36] noizer, only a web gui for the store atm [12:36] When will there an release with a gui? [12:36] zyga: looks like the missing emulated device in qemu is the reason [12:36] morphis: I think you are right [12:36] and a snap scope? on the phone? [12:36] * zyga looks at how to identify the right bt device to use [12:37] zyga: so usb forwarding .. [12:37] noizer, planned for the future, but the focus is currently headless ... once that is 100% solid there will be UI bits on top (essentially anything that can use Mir/XMir [12:37] no ETA yet though [12:38] guest42315, i thinnk that exists already (but doesnt do much, needs snap integration on the bottom layer) [12:38] zyga: look at /sys/class/bluetooth/hci0/device/uevent [12:38] gives you PRODUCT= [12:39] morphis: lsusb [12:39] ogra_, yeah someone posted a video on youtube, if i remember correctly [12:39] morphis: for me that says Bus 004 Device 003: ID 0a5c:2145 Broadcom Corp. BCM2045B (BDC-2.1) [Bluetooth Controller] [12:39] or that way [12:39] morphis: then I just add -usb -device usb-host,hostbus=4,hostaddr=3 \ [12:40] morphis: testing now [12:40] morphis: needs sudo :) [12:40] is a bit more complex here [12:40] connected over an internal hub [12:41] morphis: how? [12:41] mvo wrote a God daemon? :) [12:41] rbasak, to make snappy rule the world ;) [12:41] it is confined though [12:41] morphis: I removed the hci up and service shut-down [12:41] zyga: do I have to leave the port number just out when setting up the forwarding? [12:41] morphis: not sure if that's needed [12:42] zyga: you need to unload the bluetooth driver your system has loaded [12:42] morphis: port number for tcp redirects? [12:42] btusb normally [12:42] |__ Port 11: Dev 13, If 0, Class=Wireless, Driver=btusb, 12M [12:42] (booting now, we'll see shortly) [12:42] morphis: for wifi we did not touch any modules [12:43] morphis: maybe bt is different, let's see what I get [12:44] staging the stage [12:44] staging phase [12:45] :) [12:45] thanks dholbach [12:46] uoa question: are the sections/stanzas for the .yaml file described in detail somewhere? [12:47] carif_, there si a schema file in the snapcraft source that is supposed to be turned into a proper doc [12:47] morphis: success [12:47] morphis: it worked! [12:47] yeah! [12:47] didn't get my usb device forwarded yet [12:47] ogra_, ty [12:47] morphis: I'll push my setup [12:47] carif_, http://bazaar.launchpad.net/~snappy-dev/snapcraft/core/view/head:/schema/snapcraft.yaml [12:48] there will be a proer example snapcraft.yaml based on that [12:48] *proper [12:48] * guest42315 witchcraft [12:48] uoa: it's very nice to see that snapcraft pulls all dependencies for you [12:48] morphis: but I can already see that confinement aside this really works [12:48] zyga: yeah! [12:48] zyga: next things: [12:48] run bluetoothctl [12:48] > power on [12:48] > scan on [12:48] waiting for devices being found [12:49] morphis: works [12:49] morphis: I see my speaker! [12:49] wow! [12:49] morphis: it works :D [12:49] haha [12:49] nice [12:49] uoa: any reason why libgthread is not listed in snap: section? [12:49] how long did it took us? [12:49] :D [12:49] zyga: you have some LE device? [12:49] o/ [12:49] morphis: no, I don't :-( [12:49] zyga: half a day :) [12:49] zyga: I have one [12:49] morphis: amazon links appreciated [12:49] morphis: test it! [12:50] search for TI sensortag [12:50] zyga: let me get some lunch first [12:50] QUESTION: do the asterisks at the end of the file names in the yaml file have significance? [12:50] zyga: would be great if you can help until I am back with how to forward my usb device the right way: http://paste.ubuntu.com/12541750/ [12:51] morphis: ok [12:51] it's: |__ Port 11: Dev 13, If 0, Class=Wireless, Driver=btusb, 12M [12:51] morphis: lsusb? [12:51] UOA question: can I use language packages as parts, e.g. python pip packages? [12:51] morphis: you can try both [12:51] just using bus=1 and addr=13 didn't worked [12:51] morphis: look at my branch, I used sudo as well [12:51] oh [12:51] hmm [12:52] carif_, i thnk you can [12:52] zyga: oh wonder [12:53] with your changes it just seem to work [12:53] lets wait until the device has booted [12:53] zyga: you have another BT Usb dongle? [12:53] zyga: or an Ubuntu phone? [12:54] yup, that answered it, ty [12:54] morphis: yes [12:54] morphis: both :) [12:54] morphis: what do you have on your mind? [12:54] setting up a GATT service [12:55] morphis: though the dongle I have is ancient, it's not 4.0 [12:55] ah [12:55] morphis: my desktop has 4.0 though [12:55] morphis: it's pretty fresh [12:55] morphis: and I also have the phone [12:55] that is the one used in the vm? [12:55] morphis: (all kinds) [12:55] morphis: no, the one in the VM is whatever my thinkpad x200 has [12:55] morphis: BCM2045B [12:56] morphis: though I can boot the KVM image on another machine [12:57] lol [12:58] morphis: so what would be the best target to try [12:58] zyga: great [12:58] zyga: bluez-5.34/tools/gatt-service.c is the one you need to run there [12:58] with bluetoothd running [13:00] QUESTION: could you go into more detail about stage-packages? i don't understand whether you have to have them or they are helpful but optional [13:01] pratt, the stage dir is always there ... not always used for packages though, it is just the place wheer all bits are collected for later consumption [13:02] morphis: it's not built by the current config, trying to build it explicitly [13:02] zyga: http://paste.ubuntu.com/12541848/ [13:03] QUESTION: does `snapcraft run` can run ARM instance on amd64 host? [13:03] not yet, no [13:03] zyga: that is my small LE key finder [13:03] :) [13:03] morphis: let me try something like that [13:03] snapcraft also can not cross build yet, you need to run it in an arm chroot or on arm HW [13:03] thanks! [13:03] so, now its really time for lunch [13:05] morphis: later on you have to tell me what's the right comand sequence [13:05] morphis: pair vs connect [13:05] morphis: http://pastebin.ubuntu.com/12541867/ [13:05] morphis: I had to fiddle with on/off button on the device to make it discoverable [13:06] https://wiki.ubuntu.com/Snappy/Parts [13:06] Is there any news for building multi-arch snaps with snapcraft? [13:06] longsleep, not yet, nope [13:11] QUESTION: .snap packages are mean to be self contained, meaning there shouldn't be any dependecies like .debs. What is the current plan to support basic libraries like libc or libz for dependecies from existing C applications? Are we gonna have API versions/levels like Android? [13:12] Debian policy says "Packages must not require the existence of any files in /usr/share/doc/ in order to function [115]." [13:13] So perhaps it is acceptable for snappy to default to exclude that by default since it is guaranteed to not break anything. [13:13] rbasak, well ... [13:14] rbasak, debs often ship the copyright file in there ... if your snap includes deb binaries you will likely want at least the copyrigth to persist [13:15] I imagine that maintaining copyright and licensing information should be part of a separate process [13:15] why ? [13:15] ah, ok. so apps should target to an lts release? [13:16] As debs are only once source of files being delivered, and one that happens to embed this information. What about the others? [13:16] if you have existing copyright files there is no need to re-write that or copy it around [13:16] uoa question: so to clarify, I make a .snap with snapcraft and i install a .snap with snappy. 'snapcraft run' fires up a container and 'snap install' s the snap, right? [13:16] rbasak, well, for other projects the mechanism they actually use is used ... i.e. make install [13:17] Need to define some way to pull those in and present the information to the end user. When grabbing from debs grab the copyright file (only), when grabbing from other sources then use what is defined for that (or from the main yaml file or whatever). Then consolidate all of that into one place. [13:17] rbasak, there are no plans to "present" it [13:17] Hello! Is there a snapcraft part type for qmake-projects? [13:18] rbasak, but we need to chip it in the snap [13:18] *ship [13:18] If shipping it in the snap is how you define "present" it, then that's fine. [13:19] Wiki parts seem like a really neat way to make it easy for snappers to share parts. Good job to whoever came up with that :) [13:19] * ogra_ would like to see /usr/share/doc/ contents gone btw ... since its a waste of space ... [13:19] but we have to keep the copyright file there [13:20] Is there a list of all the project types supported by snapcraft? [13:20] My point is that you don't have to keep it *there*. As long as you ship it. [13:20] sure, but that would mean more modification [13:20] Forget usr/share/doc. It makes no sense to a snap consumer anyway, since they aren't seeing things on a per-package basis. [13:20] (in the course of deleting content from the dir it could indeed copy the copyright file someweher else) [13:21] dholbach, mvo, sergiusens, ty for uoa tutorial [13:21] thanks a bunch everyone! [13:22] thanks! [13:22] thanks [13:22] carif_, no problem, was a pleasure [13:23] thibautr, there is a doc planned (not sure if early work exists already) ... sergiusens ? [13:23] thibautr, I intend to add this to snapcraft's cli, but for now all plugins are defined in /usr/share/snapcraft/plugins [13:23] ogra_, yes there is a doc planned being written as we speak which will eventually go into developer.u.c [13:24] \o/ [13:24] s/as we speak/as we write and read/ [13:24] moar docs !! [13:25] do we have a qmake type yet ? [13:25] thanks, yeah, it was a pleasure! [13:25] (see T-mon''s question above) [13:26] ogra_, I answered live about that [13:26] oh [13:26] * ogra_ missed that [13:26] repeating just in case, there is no qmake type for a part but we are glad to help you write one if you feel like it :-) [13:32] sergiusens: about api level, is there anyway to specify which release an app is targetting to? [13:34]