[06:05] <aaaa_> hello
[06:06] <aaaa_> what's purpurse this forum?
[06:07] <aaaa_> are there any live guys?
[06:12] <mup> PR snapd#3547 closed: snap-seccomp: skip socket() tests on systems that use socketcall() instead of socket() <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3547>
[08:11] <mup> PR snapd#3533 closed: tests: extend find-private test to cover more cases <Created by fgimenez> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3533>
[08:16] <ogra_> hmpf ...
[08:18] <ogra_> mouse battery died .. with no warning, nothing ... takes me ten minutes to find new batteries ... when i return to my desktop a warning about my mouse battery being low pops up ... tsk ...
[08:18] <ogra_> (would really help to have warnings *before* the events happen :P )
[08:23] <ogra_> popey, what they call "ubuntu-core" is actually some self-bootstrapped classic install... i think the friendlyarm wiki should actually have an image linked for the air ...
[08:27] <ogra_> looks like http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Air should have something
[08:34] <ogra_> popey, and here we go ... "NanoPi NEO AIR has an Ampak AP6212 chip, which needs special firmware files" ... http://linux-sunxi.org/FriendlyARM_NanoPi_NEO_%26_AIR
[08:35] <ogra_> (it is a broadcom device as i suspected (ampak builds chips around broadcom stuff usually)
[09:03] <mup> PR snapd#3530 closed: cmd/snap: include snap type in notes <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/3530>
[09:03] <mup> PR snapd#3540 closed: overlord/state: Abort() only visits each task once <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/3540>
[11:01] <cjwatson> Could somebody please retry https://travis-ci.org/snapcore/snapd/builds/248376205 ?  I don't think the timeout is the fault of my PR.
[11:11] <niemeyer> Morning all
[11:11] <niemeyer> cjwatson: Looking
[11:12] <cjwatson> ta
[11:12] <niemeyer> cjwatson: Restarted.. there are MBR errors in the log.. Linode seems to have broken their image feature in the last 10 days or so
[11:13] <niemeyer> They're investigating
[11:13] <niemeyer> We'll give them one more week or so, and if they can't get it together we'll move elsewhere
[11:14] <Chipaca> niemeyer: does that mean we'll have a new backend for spread in about a week? :-)
[11:14] <Chipaca> niemeyer: how was your trip back, btw?
[11:14] <niemeyer> Chipaca: Well, it means I'll start working on one in a week :)
[11:14] <niemeyer> Chipaca: It was as good as it gets :)
[11:15] <niemeyer> Chipaca: Thanks for asking.. I'd guess yours was even better? :P
[11:15] <Chipaca> niemeyer: I can't comment
[11:20] <mup> PR snapcraft#1389 opened: Use newer distro module with no tuple <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1389>
[11:57] <mvo> niemeyer: hey, i see some lines in linode like "Cannot allocate linode:ubuntu-16.04-64: cannot create Linode disk with ubuntu-16.04-64: you do not have enough unallocated storage to create this Disk (608 requested, but only 0 available)" (https://travis-ci.org/snapcore/snapd/builds/249550256#L712). anything we can do about this?
[11:58] <mvo> niemeyer: also in the same run in line 816: Cannot allocate linode:ubuntu-core-16-64: cannot boot linode:ubuntu-core-16-64 (Spread-64): cannot Direct Disk boot a disk with no MBR: - do we need to update a config there maybe?
[12:00] <niemeyer> mvo: What machines are you seeing this in? I'll have a look
[12:01] <niemeyer> mvo: The second issue is known and has been reported late last week
[12:02] <mvo> niemeyer: spread-33, spread-70, spread-52 seems to be candidates
[12:03] <niemeyer> mvo: Thanks, I'll do a complete pass
[12:03] <niemeyer> mvo: These are likely follow ups from the primary issue of thawing images being broken
[12:04] <mvo> niemeyer: thank you!
[12:10] <niemeyer> mvo: np, I could find a single machine where there was space issues, Spread-14
[12:11] <mvo> niemeyer: that matches the log its right before the error message
[12:11] <mvo> niemeyer: shall I restart?
[12:11] <niemeyer> mvo: Ok, we're good then, thanks for the note
[12:11] <niemeyer> mvo: Yeah.. although note that I think Linode is still broken in terms of image thawing, so it may be a bit frustrating still
[12:11] <niemeyer> mvo: Please let me know if you see other/unknown issues
[12:17] <mvo> niemeyer: thank you, will do
[13:03] <mup> Bug #1702095 opened: snap enable removes complain for daemons <Snappy:New> <https://launchpad.net/bugs/1702095>
[13:59]  * pedronis break
[14:29] <mup> PR snapcraft#1369 closed: Handle I/O errors in os.link (LP: #1689956) <Created by evandandrea> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1369>
[14:47] <mup> PR snapd#3549 opened: many: epose services commands for snap services <Created by chipaca> <https://github.com/snapcore/snapd/pull/3549>
[14:48] <Chipaca> anybody looking to review that ^ please let me know if you'd rather I split it into individual PRs (or maybe 1 for osutil&systemd changes, one for daemon&cleint&cmd/snap changes)
[14:48] <Chipaca> each commit stands on its own (and on those coming before it)
[14:50] <pedronis> it is bigly
[14:57] <mup> PR snapd#3550 opened: update firewall-control to allow {arp,ip,ip6}tables to control bridged vlan/ppoe-tagged traffic <Created by coreycb> <https://github.com/snapcore/snapd/pull/3550>
[14:58] <Chipaca> pedronis: ok, adding an intermediate PR with osutil&systemd, let's see how that split works
[15:00] <mup> PR snapd#3551 opened: systemd, osutil: rework systemd logs in preparation for services commands <Created by chipaca> <https://github.com/snapcore/snapd/pull/3551>
[15:04] <Chipaca> pedronis: ^ there
[15:04] <Chipaca> not sure it helped much :-)
[15:05] <pedronis> Chipaca: it didn't :)
[15:06] <pedronis> so maybe up to daemon and client and cmd/snap ?
[15:06] <pedronis> (I don't know how big each checkin is)
[15:06] <Chipaca> pedronis: the commits are separate, and would be the PRs
[15:06] <pedronis> anyway, maybe ignore me, not sure I'm going to look at it today
[15:07] <Chipaca> pedronis: daemon: +625 −7
[15:07] <Chipaca> pedronis: client: +335 −0
[15:07] <Chipaca> pedronis: cmd/snap: +218 −0
[15:07] <Chipaca> ¯\_(ツ)_/¯
[15:07] <pedronis> ok, so 3 PRs would be reasonable
[15:07] <pedronis> or 2 PRS
[15:07] <Chipaca> pedronis: osutil+systemd, daemon, cmd+client?
[15:07] <pedronis> yes
[15:07] <Chipaca> on my way
[15:09] <mup> PR snapd#3552 opened: daemon: implement service commands <Created by chipaca> <https://github.com/snapcore/snapd/pull/3552>
[15:15] <mvo> ogra_: are the uboot version for the pi2/pi3 snaps similar/the-same or different? the timestamps indicate similar versions, is that the case?
[15:16] <ogra_> yeah, similar (same tag/branch) but different builds
[15:16] <mvo> ogra_: cool, thank you - same tag/branch is all the info I need
[15:17] <ogra_> i'm planning to move them all to "build directly from upstream source" soon ... then you can just check the branch version in snapcraft.yaml in the future
[15:17] <mvo> ta
[15:18] <ogra_> (should both be v2017.01)
[15:25] <Chipaca> niemeyer: http://i.imgur.com/gPbCUdF.png
[15:26] <mvo> Chipaca: hahaha
[15:27] <Chipaca> mvo: i take it i wasn't too subtle then :-D
[15:27] <Chipaca> (this is via https://dev.to/rly fwiw)
[15:28] <mvo> Chipaca: great stuff
[15:32] <niemeyer> Chipaca: We may be about to write the last chapter :)
[15:59] <mup> PR snapcraft#1377 closed: kernel plugin: add default targets per powerpc, ppc64el and s390x <Created by piso77> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1377>
[16:08] <mup> PR snapcraft#1390 opened: meta: bash completion support <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/1390>
[16:15]  * Chipaca hugs sergiusens 
[16:17] <Chipaca> sergiusens: we were talking about that the other day while I was walking across London, and I don't know if we finished that conversation
[16:18] <sergiusens> Chipaca: I was walking as well ;-)
[16:18] <sergiusens> fwiw, I think this needs to be automatic, also, I searched for complete.sh in the defined locations from your blog post and could not find it
[16:19] <Chipaca> sergiusens: the release of snapd that has that has not reached ubuntu yet
[16:19] <Chipaca> sergiusens: which is why i haven't worked on making it more automatic
[16:19] <sergiusens> Chipaca: hmm, I was told it had.. :-(
[16:19] <sergiusens> stgraber: fyi ^
[16:20] <Chipaca> sergiusens: but you'll probably have it in /snap/core/current/usr/lib/snapd/complete.sh
[16:20] <sergiusens> ls: cannot access '/snap/core/current/usr/lib/snapd/complete.sh': No such file or directory
[16:20] <sergiusens> installed:          16-2 (1689) 83MB - (latest/stable)
[16:22] <Chipaca> sergiusens: ah well, at least the world is consistent
[16:23] <Chipaca> sergiusens: (i assumed you were tracking something newer than stable, but it makes sense for you)
[16:24] <Chipaca> sergiusens: in any case, we're working on the next release (yes it's delayed for a number of good reasons), should be in stable soon and then i can move on to the next step of the evil^Wmaster plan
[16:40] <stgraber> Chipaca: oh, I was told 2.26 had it, it's even in the announcement
[16:41] <Chipaca> stgraber: I do believe 2.26 does have it
[16:43] <Chipaca> stgraber: yep, confirmed 2.26 (at least as in artful) does have it
[16:44] <Chipaca> sergiusens: ^ fwiw
[17:47] <sergiusens> Chipaca: hmm, I am on zesty, maybe I should move...
[18:00] <bdx> hello all
[18:00] <bdx> I'm working on a snap for a rails app
[18:01] <bdx> I'm hitting two issues, 1) I need to symlink a yml file into the app config dir
[18:02] <bdx> 2) I can't seem to access $SNAP_COMMON, $SNAP_USER_COMMON from with the install srcipt for some reason
[18:03] <bdx> is there a recommended way of linking files into the versioned snap dir?
[18:03] <bdx> I'm working with this http://paste.ubuntu.com/25012754/
[18:04] <bdx> lines 43-47 depict where I'm having the issue
[18:04] <bdx> the application.yml needs to exist so that assets:precompile can run
[18:05] <bdx> so I keep an empty string filled application.yml with the application code
[18:05] <bdx> that the snap uses to run assets:precompile
[18:06] <bdx> in the install step
[18:06] <bdx> following that, I need to remove that application.yml and point the app to an application.yml that can be configured by the user
[18:06] <bdx> on a per deploy basis
[18:07] <bdx> one that lives outside of the versioned snap dir
[18:08] <bdx> I cant seem to access the $SNAP_COMMON and $SNAP_USER_COMMON (where I feel like this file should go) from the install scriptlet
[18:08] <bdx> so I decided to try moving it to /srv/ and symlink from there to the versioned application dir
[18:08] <bdx> this worked to some degree
[18:09] <bdx> the symlink exists from the versioned snap dir to /srv/prm/config
[18:10] <bdx> but the rails app it self doesnt seem to be able to access it ... even though the symlink exists  where the application.yml shoudl be in the config/
[18:15] <bdx> one more thing
[18:16] <bdx> how can I make a configurable value for RAILS_ENV
[18:16] <bdx> such that the rails env could be set on a per install basis?
[18:20] <mup> PR snapd#3553 opened: interfaces: enable access to bridge settings <Created by coreycb> <https://github.com/snapcore/snapd/pull/3553>
[18:40] <ogra_> bdx, your chances to catch some snapcraft devs are higher on https://rocket.ubuntu.com in the #snapcraft channel
[18:44] <bdx> ogra_: thx
[20:02] <mup> PR snapcraft#1372 closed: cli: Containerbuild clean <bug> <Created by kalikiana> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1372>
[22:11] <mup> PR snapcraft#1385 closed: lxd: Don't assume user ID to 1000 for raw.idmap <Created by kalikiana> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1385>
[22:17] <mup> PR snapd#3554 opened: client: wrap services calls <Created by chipaca> <https://github.com/snapcore/snapd/pull/3554>