[01:12] hi2all! How to me to create the folder in a HOME directory of application before its start in start.sh? if i use mkdir -p $HOME/folder i see in log ubuntu-core-launcher mkdir: cannot create directory ‘/folder’: Read-only file system === chihchun_afk is now known as chihchun [07:29] good morning [08:06] good morning === davmor2_ is now known as davmor2 === beowulf is now known as Guest82904 [10:17] Good morning all; happy Monday, and happy Fibonacci Day! 😃 === vrruiz_ is now known as rvr [10:56] longsleep: moin! did you ever file a bug about wait4network not coming after firstboot? [10:56] or was it frameworks.target not coming after firstboot [10:57] i can't find it, so i'm going to assume you didn't === chihchun is now known as chihchun_afk [13:00] Good morning [13:36] sergiusens, I'm getting a plainbox crash in snapcraft... not super familiar with it [13:38] sergiusens, http://pastebin.ubuntu.com/13476687/ any ideas? [14:03] kyrofa, are you on xenial? if not, add the ppa from the docs [14:11] sergiusens, the docs say only if 15.04 or previous. I'm on wily-- should the docs say 15.10 or previous? [14:11] zyga, ^ [14:11] kyrofa, paste me the plainbox error just in case [14:11] * zyga looks [14:11] sergiusens, http://pastebin.ubuntu.com/13476687/ [14:12] kyrofa, are you adding stuff, but the traceback, the name of the test is the problem? [14:12] kyrofa: odd, can you tell me if that's vanilla or did you change anything to trigger that? [14:13] Chipaca: hey i am playing around with your http.chipaca snap and wanted to try snapd with it - though i get a audid DENIED on /run/snapd.socket - any ideas? [14:13] kyrofa: and if you did, can you run ./manage.py validate please [14:13] zyga, just cloned snapcraft, installed deps in debian/control + plainbox, and ran tests [14:13] kyrofa: hmmm [14:13] kyrofa: thanks, please file a bug on plainbox and attach this backtrace [14:13] kyrofa: I'll see if I can replicate that [14:13] zyga, sure! [14:14] kyrofa: it looks really weird on first look [14:15] longsleep: the socket is 0600 so you need sudo for any op for now [14:15] Chipaca: i am running as root [14:15] longsleep: also it'll only work on rolling without more fiddling [14:15] Chipaca: ah [14:15] as 15.04 still uses @snapd, not /run/snapd.socket [14:15] Chipaca: Ah so i would need to change the aa profile to get it running? [14:16] addr="@snapd" i see in that [14:16] kyrofa: please ping me with the URL or assign the bug to me (zyga) [14:16] longsleep: the .socket file (you can copy it to /etc/systemd/system and edit it there) [14:16] longsleep: and even then you probably need to change something in apparmor [14:16] Chipaca: ok :) - so the snapd profile is essentially broken on 15.04 then? [14:16] zyga, will do. I'm gonna toast my lxc and try clean one last time, then I'll log it [14:17] longsleep: yeah :-( /usr/share/apparmor/easyprof/policygroups/ubuntu-core/15.04/snapd is still @snapd [14:17] hmmm [14:17] kyrofa: thanks [14:17] longsleep: what happens if you edit "do" to use \0snapd? [14:18] Chipaca: let me check [14:19] Chipaca: ConnectionRefusedError(111, 'Connection refused') [14:20] sigh [14:20] longsleep: i'll play with it in 15.04 and see how i can make it work [14:20] longsleep: you're not the first person to ask me this :) [14:20] i think olli was always wanting this [14:20] but, priorities [14:21] (it might'v been asac wanting http.chipaca on 15.04) [14:21] Chipaca: cool - i am not so much about the http snap, i rather want to play with snapd to check if i should go through it or rather import snappy directly to read and sed configuration [14:22] longsleep: ah! that's an easy one to do [14:22] longsleep: sudo /lib/systemd/systemd-activate -l 8080 /usr/bin/snapd [14:22] Chipaca: ah ok [14:22] longsleep: tadaa, snappy rest daemon on 8080 [14:22] longsleep: *unauthenticated* [14:22] awesome - thanks! [14:22] (you just gave root to the network) [14:23] sure === barry` is now known as barry_ [14:23] fie with me :D [14:23] fine [14:23] but, for testing, in a vpn or whatever, you're fine :) === barry_ is now known as barry [14:41] zyga, yeah still hitting this. You want the bug filed against plainbox even though this is in snapcraft? [14:41] kyrofa: yes [14:41] kyrofa: please [14:41] kyrofa: I'll re-assign if needed [14:41] Doing now [14:42] thank you [15:02] Chipaca: regarding snapd, i am retrieving ubuntu-core.ubuntu.config with GET and trying to PUT this back, is that supposed to work? [15:02] Chipaca: i just get line 1: cannot unmarshal !!str `modprob...` into coreconfig.configYaml [15:04] zyga, https://bugs.launchpad.net/plainbox/+bug/1519008 [15:04] Launchpad bug 1519008 in PlainBox (Toolkit) "Plainbox crash: AttributeError: 'NoneType' object has no attribute 'replace'" [Undecided,New] [15:05] kyrofa: thank you, I just prepared a xenial environment to run some tests [15:06] * zyga hopes to get up to speed with go so that he can still maintain useful add-ons to plainbox and checkbox [15:09] kyrofa: wait, wily or xenial? [15:10] zyga, wily (the docs led me to believe wily was okay-- should this be xenial instead?) [15:10] zyga, I can re-test in xenial [15:10] kyrofa: no, that's okay, I misundertood you earlier [15:10] kyrofa: wily is fine [15:19] Chipaca: ok got it, yaml format issue. Another question though, probably general to snappy config, how do i delete nodes from the yaml when they there added before? [15:48] Chipaca: fyi, when using the updated content for /usr/share/apparmor/easyprof/policygroups/ubuntu-core/15.04/snapd from xenial/ubuntu-core-security-apparmor http.chipaca works just fine on 15.04/stable [15:49] Chipaca: i think i patch the profile in our rootfs and go forward with connecting to snapd via /run/snapd.socket [15:50] Chipaca: is anyone actually using the abstract snapd socket? If not i suggest the next rootfs for 15.04 should have a fix for the snapd socket policygroup [16:13] fgimenez: ah, another thing I tried last week was to attach the failure reason into the subunit file. But I found that requires a change in gocheck. [16:13] you know, to avoid that StringException that is shown on jenkins. [16:13] elopio, it would be very helpful [16:13] I think that will be one of the priorities for the following weeks, show nice errors. [16:15] elopio, yes, once the pull requester has access to the results having the failure reason right there would be much better [16:17] nessita: Chipaca: mvo: now I'm getting 401. This one is new. [16:17] hello-world failed to install: received an unexpected http response code (401) when trying to download https://public.apps.ubuntu.com/anon/download/canonical/hello-world.canonical/hello-world.canonical_1. [16:17] 0.18_all.snap [16:17] Has happened like 2 times out of 4 today. [16:18] elopio, myapps is failing atm, we're working on that [16:18] elopio, you shouldn't get a 401 but some 500, you sure is a 401? [16:18] longsleep: no, nothing is using the abstract socket. Need to check with jdstrand_ but I suspect we can bump the policies in the next 15.04 (if there is a next 15.04) [16:19] nessita: yup, 401. [16:19] Here's another: [16:19] elopio, what API call is returning 401? [16:20] hello-dbus-fwk failed to install: received an unexpected http response code (401) when trying to download https://public.apps.ubuntu.com/anon/download/canonical/hello-dbus-fwk.canonical/hello-dbus-fwk.can [16:20] onical_1.0.2_multi.snap [16:23] the code says: // try anonymous download first and fallback to authenticated [16:23] so maybe it gets a 500 on the anonymous downlaod, and then a 401 on the authenticated. [16:24] it's a GET on that URL of the snap. [16:29] nop, that's not what it's doing. [16:32] jdstrand_: if I could get approval for "ubuntu-classic.mvo" that would be neat. its a first iteration of the ubuntu-classic mode for snappy [16:50] nessita: elopio: i had a brief spat of 401s from downloads from public.apps.u.c. as well [16:50] but resolved itself [16:51] noise][, we have fixed the store [16:52] I wonder why a 500 from the store would be a 401 in updown [16:52] I should check the code [16:52] not sure, let me know if you need timestamps of my 401s [16:55] elopio, shall we wait for your PR to release a new snapcraft? [16:55] if not, then a sort of final test run would be good today [16:56] sergiusens: no. There are no regressions. I can do exploratory today and you can release unless I find something big. [16:56] sergiusens: do you have a nice list for this milestone? [16:56] elopio, sounds good [16:58] elopio, https://launchpad.net/snapcraft/+milestone/0.5 [16:58] same old place :-) [16:58] thanks. === pixel is now known as pixel_ === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [18:38] hmm, how would I go about contributing to Snappy? [19:08] I am just not finding that clear of information on this [19:08] just how to install Snappy and use it [19:14] tsimonq2, https://developer.ubuntu.com/en/snappy/start/ ? [19:15] tsimonq2, https://github.com/ubuntu-core [19:15] pixel_: that is just getting started and developer/usage tips, no? [19:17] tsimonq2, yes how to install and use snappy [19:18] pixel_: but what about actually *contributing*? [19:20] tsimonq2, https://launchpad.net/snappy (lp) https://github.com/ubuntu-core (github) mailing lists https://lists.ubuntu.com/archives/snappy-app-devel/ + https://lists.ubuntu.com/archives/snappy-devel/