[06:30] good morning [07:27] Good morning! === erkules_ is now known as erkules [08:00] hey there, not sure who has topic edit right, but you might want to "snappy-ubuntu" -> "snappy" in the Bugs launchpad url [08:08] morning [08:32] Good morning all; happy Weights and Measures Day! 😃 [08:40] mo'in! [08:41] mvo: hi there [08:41] hey Chipaca [08:41] yo [08:42] mvo: I called it packageYaml.dirname because there's already Dirname(part) [08:42] mvo: also because no other word described what it did [08:42] was tempted by fqdn too [08:42] mvo: i mean: "no other word described what it did" applied more to when i worte Dirname(part) [08:43] mvo: fullname comes close, but isn't descriptive [08:43] Chipaca: I kind of like fqdn better, dirname pops images of directory structures into my brain, but like I said, maybe thats just me :) [08:43] mvo: otoh i know dirname is not immediately obvious [08:44] I guess namespacedName is too long :/ [08:44] mvo: also, wrong [08:44] mvo: because it's not namespaced if it's a framework or a gadget [08:44] aha, because for frameworks its not [08:44] meh [08:44] quite :) [08:44] fqn() :) ? [08:44] fqsn() - full-qualified-snap-name? [08:45] but I can life with dirname(), I just wish we had a better name [08:49] nameMaybeNamespaced [08:50] although Maybe makes me think it's either the namespaced name, or nil [08:51] * mvo nods and scratches head [09:05] mvo, in the package.yaml - am I supposed to use "name: appname" or "name: appname.username"? [09:05] dholbach: name: appname [09:05] it looks like the former (else I get "package name with namespace not supported") [09:05] ok [09:05] thanks Chipaca [09:05] dholbach: the origin does not go in the yamel [09:06] ok cool [09:07] ogra_, can you pull from lp:~dholbach/+junk/chatroom? [09:07] ogra_, ... and have a look at https://code.launchpad.net/~dholbach/node-snapper/update/+merge/259584? [09:08] dholbach, oh, nice, but i dont think that will work for non wily ... the cdimage url is completely different for released tarballs [09:09] ogra_, distro-info will always give you the current release [09:09] err, current development release [09:09] dholbach, right [09:10] ogra@anubis:~/datengrab/holbi$ wget http://cdimage.ubuntu.com/ubuntu-core/daily/current/trusty-core-armhf.tar.gz [09:10] 2015-05-20 11:10:07 FEHLER 404: Not Found. [09:10] mh? [09:10] the REM_ vars need to be adjusted too ... [09:11] daily/current/$DIST...tar.gz only works for the durrent devel release [09:11] *current [09:11] right... I though that the current dev release is what we want? [09:11] if you ran node-snapper on a trusty system DIST would be set to trusty [09:12] but that url only works for wily :) [09:12] does anyone has topic edit right/saw my comment earlier? [09:12] dholbach, for trusty the url would have to be http://cdimage.ubuntu.com/ubuntu-core/releases/trusty/release/ubuntu-core-14.04-core-armhf.tar.gz [09:13] (note the different tarball name (along with the different path) [09:13] ogra_, ok... I thought distro-info-data was backported for trusty, etc [09:13] then we probably just update the string to 'wily' and be done with it :/ [09:13] seb128, sorry, no op privileges here :/ [09:13] oh [09:14] ogra@anubis:~/datengrab/holbi$ distro-info -d [09:14] ubuntu-distro-info: Distribution data outdated. [09:14] Please check for an update for distro-info-data. See /usr/share/doc/distro-info-data/README.Debian for details. [09:14] heh [09:14] i guess thats the problem here [09:14] right [09:14] dholbach, ok, no worry, hey btw :-) [09:14] hey seb128 [09:15] hrm [09:15] apt doesnt think it is outdated ... weird [09:15] ogra_, I'll leave it up to you to either update your trusty vm or just use 'wily' as string in the script - 'vivid' doesn't work :) [09:15] yeah, i have the wily change local, just not merged yet [09:15] ok ok [09:15] yours appears better though [09:15] (saving me from updating every cycle) [09:16] yeah, works after update ... [09:17] <3 [09:19] ogra_, I'm turning your blog entry into a tutorial, that's why I was verifying all the steps [09:19] merged and pushed [09:20] both? :) [09:20] no, looking at the chatroom one now [09:20] thanks ogra_ [09:21] i cant buiuld snaps here due to a bug in the verification for "ports" :/ [09:21] really? [09:21] yeah [09:21] which version of snappy do you have installed? [09:21] is this vivid? [09:21] trusty [09:21] latest from the PPA [09:21] snappy-tools is 10 [09:22] click-reviewers-tools is 0.26~snappy0.14.04.1 [09:22] and ubuntu-snappy-cli? [09:22] 0.1.2-1+419~ubuntu15.04.1 [09:22] aha [09:22] 1.0.1-1+439~ubuntu15.04.1 [09:23] yeah, just noticed [09:23] from https://launchpad.net/~snappy-dev/+archive/ubuntu/beta [09:23] man... you're years behind! [09:24] ogra@anubis:~/datengrab/snaps$ snappy build snap-inspector-term/ [09:24] Generated 'snap-inspector-term_0.1-1_multi.snap' snap [09:24] YAY !!!! [09:24] yeeeeeeeehaw [09:24] dholbach, did you try rolling a chatroom snap with that change ? [09:24] (i'm surprised there is not more to change) [09:25] doesnt complain though ... [09:25] * ogra_ merges [09:27] and pushed [09:28] hanks! [09:28] thanks! [09:33] ogra_, if you create the snap like that and sideload it using snappy-remote... does the chatroom app work for you? [09:35] dholbach, no, if i create it like that the whole of node-snapper is missing :) [09:35] cant work [09:35] you need to follow the steps ;) [09:36] I think I did [09:36] http://pastebin.ubuntu.com/11241760/ [09:36] right, i didnt :) [09:36] ahhhhhh ok :) [09:37] i dont think you can start a snap service like that [09:37] I was just trying to debug why it didn't start up [09:37] use systemctl ... and watch syslog [09:38] well, the PATH isnt right ... and you will mis all the env vars when just calling it with sh [09:38] what would the systemctrl invocation be? [09:39] not sure if we still redirect stdout to syslog, but you could switch to "set -ex" [09:39] systemctl | grep chatroom [09:39] that gives you the service name [09:40] sorry, I meant... how do I use systemctl to start the chatroom? [09:42] systemctl start [09:42] probably sudo too :) [09:42] I don't see it listed there [09:46] yeah, just noticing the same with my snap-inspector-term [09:46] seems the systemd handling changed [09:47] (my snappy knowledhge is about as outdated as that package above was :) ) [09:49] mvo: pushed with 'qualifiedName' [09:50] does anyone know how systemd for snaps changed ... is that documented anywhere ? [09:50] (i dont see a unit for my snap ... ) [09:51] ogra_: changed when? [09:52] ogra_: hasn't changed :) [09:52] in ages. two weeks at least. [09:52] Chipaca, well, i'm using a snap that works fine on my really old (several months) snappy install [09:52] i re-built with a new snappy (fixed all complaints) and installed it ... [09:53] systemctl doesnt list it ... [09:54] (and it obviously doesnt autostart as it used to) [09:57] * ogra_ sees /apps/snap-inspector-term.sideload/0.1-1/meta/snap-inspector-term.snappy-systemd but nothing installed anywhere else [09:59] ogra_: interesting [10:00] i see it attempted to start in syslog [10:00] (amd64)ubuntu@localhost:~$ systemctl list-units| grep inspector [10:00] (amd64)ubuntu@localhost:~$ [10:01] (amd64)ubuntu@localhost:~$ sudo grep Inspect /var/log/syslog [10:01] May 20 09:43:27 localhost systemd[1]: Started Inspect the environment of a snap package in a browser. [10:01] May 20 09:43:27 localhost systemd[1]: Starting Inspect the environment of a snap package in a browser... [10:03] ogra_: sudo systemctl | grep -i inspector [10:03] no change ... [10:03] hrmph [10:04] ogra_: note the sudo there [10:04] yeah, i tried with and without [10:04] ogra_: what's your package.yaml like? [10:05] http://paste.ubuntu.com/11242104/ [10:05] systemd usually prints *something* if it tried to start it. and you say there isn't a file in /etc/systemd/system for your service? [10:06] there is [10:06] ah! what's it called? [10:06] but systmctl doesnt seem to know about it [10:06] snap-inspector-term_snap-inspector-term_0.1-1.service [10:08] ogra_: and “systemctl status snap-inspector-term_snap-inspector-term_0.1-1” isn't helpful? [10:08] ok, calling it gets me a start event [10:08] but it doesnt start and there is no stdout debug output in any log :/ [10:09] do we exclude snaps from list-units for security reasons ? [10:11] also how do i get the old verbosity back ? [10:11] ogra_: no, they're always there [10:11] we used to redirect stdout of the started script to journald ... seems that is suppressed now [10:12] which makes debugging really hard ... [10:12] ogra_: i'm not aware of that having changed [10:13] May 20 10:07:12 localhost.localdomain sudo[3133]: ubuntu : TTY=pts/1 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/bin/systemctl start snap-inspector-term_snap-inspector-term_0.1-1.service [10:13] May 20 10:07:12 localhost.localdomain sudo[3133]: pam_unix(sudo:session): session opened for user root by ubuntu(uid=0) [10:13] May 20 10:07:12 localhost.localdomain systemd[1]: Started Inspect the environment of a snap package in a browser. [10:13] May 20 10:07:12 localhost.localdomain systemd[1]: Starting Inspect the environment of a snap package in a browser... [10:13] that is all i get [10:13] ogra_: let me start with a fresh image here, as i'm not seeing what you're seeing [10:13] ogra_: what image are you on? [10:13] even with the start-service.sh script set to "set -x" [10:13] the kvm image currently ... [10:13] the released one [10:13] ogra_: rollin'? [10:13] no, whatever is in the default docs for kvm [10:14] 15.04 image .... [10:14] ogra_: can you give me the command you used to create the image? [10:14] i didt [10:14] *didnt [10:14] wget http://releases.ubuntu.com/15.04/ubuntu-15.04-snappy-amd64-generic.img.xz [10:14] :) [10:15] * Chipaca wgets [10:16] the script is surely still having issues (using SNAPP in the var names etc) ... but i kind of would expect that i can get some more verbose output from the failed start [10:17] you should [10:17] and it also should be in list-units [10:17] (which is the default command, btw; you don't need to say it) [10:18] right [10:18] well. it definitely isnt ... [10:18] but this time rount it at least seems to respect the set -x ... i see a bit more output [10:18] ogra_: can you try whether the xkcd one works? [10:21] installing it through webdm this at least works: [10:21] (amd64)ubuntu@localhost:~$ sudo systemctl | grep -i xkcd [10:21] xkcd-webserver_xkcd-webserver_0.5.service loaded active running A fun webserver [10:21] (amd64)ubuntu@localhost:~$ [10:21] and ps shows: [10:21] /usr/bin/python3 /apps/xkcd-webserver.canonical/0.5/bin/xkcd-webserver [10:21] asac: hey [10:22] dholbach: and systemctl status xkcd-webserver_xkcd-webserver_0.5.service should be nice too [10:22] http://excellent.mezgr.de/snappy [10:22] yeah, all fine with that [10:23] ogra_: can you put your snap somewhere so i can give it a poke? [10:24] sure [10:24] i would prefer to get proper output from the startup though .,... to be able to fix it myself [10:25] using set -x doesnt give me any error output [10:25] oh, and i see why [10:25] there is an "ubuntu-core-launcher" that seems to swallow it [10:25] thats not on my old snappy installs [10:26] the launcher shouldn't affect stdout/stderr [10:26] http://paste.ubuntu.com/11242416/ [10:26] well, i seem to get stdout ... [10:26] zyga: hello [10:26] but since the start fails i would also expect something on stderr [10:27] the paths look all ok [10:27] this reminds me, mvo: when you've got a sec, we should discuss the launcher private tmp branch thing [10:30] asac: I'd like to schedule a call with you, it's not urgent, I'd like to talk about snappy certification [10:31] Chipaca, hmm, i suspect there is something wrong with the node binary actually ... setting all the vars manually and trying to run it it just silently returns [10:32] Chipaca: right after lunch maybe? so in about 1h? or now but then I don't know how much time I have until lunch is ready :) [10:33] mvo: basically, making the tmpdir predictable opens us up to nasty attacks [10:33] mvo: so we either need to be very careful, or we use mkdtemp [10:33] mvo: leaning towards the latter myself. think about it and tell me after lunch maybe :) [10:35] yay, now i get roper ouutput [10:35] *proper output [10:36] Chipaca: my gut feeling is mkdtemp too, being careful is not my strength and its also hard to get right IME (i.e. hard to be careful enough :/ [10:37] Chipaca: I have not looked at this branch yet, I need to do that [10:37] ogra_: yay [10:37] mvo: tyhicks is looking :) [10:39] bah, and now apparmor gets in my way [10:51] ogra_: these security modules, coming over here, stealing our jobs [10:51] heh [10:51] "stealing our jooobs" [10:52] well, the package is a mess ... (apparently) ... [10:54] mvo: also about the launcher, what do you think of changing it so we pass in all the bits and it creates the environ 'from scratch'? [10:58] what dholbach tried above seems to be very typical when debugging (just running the start script with "sh -x" ) ... is there a way to manually run the launcher instead ... heanding the path to the script to it to be able to debug ? [10:58] if so we need to put it in the docs ... if not, it would be nice to have such a feature :) [11:04] * ogra_ just tries using /usr/bin/ubuntu-core-launcher ... seems it doesnt set a single var ... [11:10] \o/ [11:10] finally got it working [11:11] hmm, semi-working it seems [11:24] ogra_, did you update the branch already? :) [11:25] Chipaca: I see mvo was not as lazy as me and commented on the review :) [11:25] dholbach, yes [11:25] good morning btw! [11:25] all your changes should be pushed [11:25] sergiusens: yeah, i'm thinking of firing you as a reviewer and getting another mvo instead [11:25] mvo: btw, I discussed this with Chipaca yesterday http://snappy.asac.ws:9001/p/dot.store can I get your thoughts? [11:25] sergiusens: he's not as mean [11:25] Chipaca: :( [11:25] Chipaca: you are mean! [11:26] :-P [11:26] sergiusens: only because you like it! [11:26] ogra_, what's still missing? [11:27] Chipaca: in any case, I didn't find anything that bothered me, and planned to look at again today, so there [11:27] dholbach, dunno, i have to run through the whole howto again ... [11:27] sergiusens: neener neener [11:27] (just trying to debug the other snap now, i'll move over to chatroom after that) [11:27] ogra_, ok, I'll try as well [11:28] Chipaca: should I base my origin change on top of this one or are there more coming? [11:29] sergiusens: that one is very cryptic [11:29] not clear what it is proposing [11:30] asac, can you fix the bug link in the topic to not use snappy-ubuntu ? [11:30] (seems it is readonly) [11:30] sergiusens: there's going to be "more coming" all week :) [11:31] sergiusens: this one is probably a good place for it as any [11:31] sergiusens: next one *should* be the move to make a lot of things methods on SnapPart, but i've had branches pop up in the middle of this before now :) === asac changed the topic of #snappy to: Our 4 Forces: Snappy for Things: http://www.ubuntu.com/things || Snappy for Cloud: http://www.ubuntu.com/cloud/tools/snappy || Snappy for App Devs and Porters: https://developer.ubuntu.com/en/snappy/ || Snappy for Bugs: https://bugs.launchpad.net/snappy :P [11:39] ogra_: i have no idea how to change anything wrt access settings etc... so just changed it. if we want to change acls etc. or you need op powers talk to lool :P [11:39] or i think it was beuno [11:40] i'm not eager to get op powers ... usually if there is a troll i'm still searching for the right commands to gain OP when someone else already kicks him :) [11:43] is this really the right way to set up wifi on my bbb? [11:43] http://www.marinus.nu/2015/02/enabling-wifi-on-snappy-ubuntu-core.html [11:43] seems like making the partition rw is sub-optimal [11:45] rickspencer3: if it needs you to set the partition rw, it is not the right way [11:45] * Chipaca reads [11:47] rickspencer3: we're shipping wpa_supplicant already [11:47] rickspencer3: so the post is wrong, but also outdated [11:47] Chipaca, so I just need to drop a config file somewhere? [11:48] looks like [11:48] rickspencer3: beats me :) but either drop it or edit it [11:48] (i can find out, certainly, but i don't know offhand) [11:52] Chipaca: launcher> if you mean that instead of generating all this env madness in the wrapper script it should go into the launcher, thats a plus one from me, we just need to make sure that we do as little as possilbe in the part that runs as root, but thats obvious anyway :) [11:52] mvo: it would mean changing the way we call the launcher (we need to give it the version and origin and some other stuff) [11:53] sergiusens: reading the etherpad now [11:53] Chipaca: yeah, I'm fine with that as long as its not too ugly :) [11:54] mvo: the alternative being to parse yaml in C [11:54] *shudder* [11:54] LOL [11:54] as root! [11:54] * mvo drops dead in shock [12:01] sergiusens: dot.store looks good, I'm a bit unhappy that /frameworks and /apps have a different dir layout now, i.e. one with /$origin/ in there and the otherwithout, but its not a big deal and probably unavoidable, I guess I just like symmetry :) I will add some inline comments [12:02] ogra_, I haz the power [12:02] (so does the ubuntu IRC council) [12:02] yeah, thats usually my last resort :) [12:03] ogra_, happy to give you access [12:03] nah, i'm find pinging someone with power ... we usually dont lock the topic iin ubuntu channnels though [12:20] ogra_, does it work for you now? [12:21] dholbach, havent gootten to chatoom yet ... i'll let you know then [12:21] <3 [12:27] does this look to anyone like i have my wifi configured properly? [12:27] http://pastebin.ubuntu.com/11244005/ [12:28] mvo, I'm looking at a tutorial which seems partly to depend on python being in the Ubuntu Core image - do you have plans to change that? :) [12:29] rickspencer3, depends what properly means. No IP address, not connected to anything [12:29] beuno, right [12:29] so, that's a "no" :) [12:30] dholbach: sort of, for 16.04 it will most likely change, for 15.04 it will stay (unless asac decides otherwise :) [12:30] ok... do you have a bug open for it? [12:31] beuno, does this look right? http://pastebin.ubuntu.com/11244055/ [12:31] rickspencer3, no, remove the EOF [12:31] dang it [12:31] the rest looks fine [12:31] I assumed the EOF would be ignored [12:32] also, now we can all park in front of rickspencer3's house and leach off the wifi [12:32] it is the second half of the "echo" in the blogpost :) [12:32] oh fudge [12:32] lol [12:32] if you remove the echo line you also need to remove the EOF [12:33] ogra_, I think I am looking at the wrong thing, can you give me the link again? [12:33] dholbach, there are more issues with node-snapper (just starting to inspect them) [12:33] rickspencer3, which link ? [12:34] http://www.marinus.nu/2015/02/enabling-wifi-on-snappy-ubuntu-core.html ? [12:34] ogra_, oh, I thought you were referring me to a blog post with instructions [12:34] let me look [12:34] right, that's the one I used [12:34] but since Chipaca told me that wpa supplicant was already installed, I skipped installing the debs [12:34] well, you need the config [12:35] so I need to make it ro afterall? [12:35] that seems pretty horrible [12:35] and you need: [12:35] sudo chmod go-r /etc/network/interfaces.d/* [12:35] yeah, I did that [12:35] no, you shouldnt need to make it ro [12:35] err [12:35] rw [12:35] that dir should be rw [12:35] right, rw, worry [12:35] ogra_, so I don't need to install the debs, right? [12:35] so that you can create /etc/network/interfaces.d/wlan0 [12:36] no, you dont need to [12:36] right, so I made the config file [12:36] I chmoded the file [12:36] right [12:36] so you should be able to bring up the interface now [12:36] sudo ifup wlan0 [12:37] oh [12:37] I can't just plug it in? [12:37] seems suboptimal that I have to connect to ethernet to turn on wifi ;) [12:37] not sure that triggers a connect [12:37] it should come up on boot ... [12:37] oh, ifup said the interface was already configured [12:37] but i dont know if anything would call "ifup wlan0" if you plug it in [12:38] so ifdown it first [12:38] ogra_, I assumed that the allow-hotplug wlan0 line meant I could just plug int eh dongle when I want [12:38] might be configured with old settings [12:38] still no ip address :/ [12:38] iirc it just means the interface can vanish and appear [12:38] ok [12:38] but i might be wrong [12:39] well, ifconfig sees the dongle, just doesn't have an ip address [12:39] * rickspencer3 tries different dongle [12:40] oops, the Belkin dongle categorically does not work :/ [12:40] dholbach, seems the armhf build of the node modules completely fails in wily ... (i get a proper amd64 tarball though) [12:40] that will need some more love [12:41] so Netgear one is recognized, but still does not get an IP address [12:43] rickspencer3, hmm ... i think the underscores there are wrong [12:43] interesting [12:43] ogra_, just delete those? [12:43] try wpa-ssid and wpa-psk [12:45] i got some interesting messages that time :) [12:45] ogra_, http://pastebin.ubuntu.com/11244254/ ? [12:46] so it tried to get the ip vis dhcp but wasnt connected to the AP i would say [12:46] does ifconfig list the wlan0 interface ? [12:48] mvo, do you have a bug open for moving off of python? [12:49] ogra_, yes, iconfig lists it [12:49] ogra_, ima try a reboot [12:49] and iwconfig ? [12:49] command not found [12:50] aha [12:50] * rickspencer3 braces [12:51] well, i'm not sure if wpa_supplicant actually needs it installed [12:52] (it is just helpful for debugging to see if there is an AP connection) [12:53] rickspencer3, check the dmesg output when connecting the thing ... [12:53] dmesg | tail -50 ... or so [12:53] k [12:53] (or -100 for more lines) [12:53] also checking the packet counters for the interface might give an indication if there is anything working [12:53] yeah [12:54] in ifconfig that is [12:54] let me do ifdown/ifup and get dmesg first [12:55] * ogra_ needs to move for a meeting ... brb [12:55] ogra_, kk [12:55] http://pastebin.ubuntu.com/11244363/ [12:56] ^for when you get back [12:57] rickspencer3: you have your interfaces files in a paste? [12:58] asac, yes, let me get you the latest [12:58] asac, http://pastebin.ubuntu.com/11244393/ [12:58] this time I removed my password ;) [13:00] hmm [13:00] heh [13:00] [ 1894.677595] musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_host (91, missing firmware ? [13:00] rickspencer3: does that dongle work on your desktop? [13:01] good to check there first before trying to go embedded :P [13:01] asac, yes, but ... for all I know I had some non-free drivers installed [13:01] ahh [13:01] I don't recall installing non-free drivers, though, tbh [13:02] I haven't used the thing in quite some time [13:02] * rickspencer3 tries on laptop [13:02]