[10:24] <zyga-ubuntu> o/
[12:24] <sSs_> hi
[12:25] <sSs_> is here the best place to ask about build.snapcraft.io?
[12:45] <zyga-ubuntu> sSs_: hey
[12:45] <zyga-ubuntu> sSs_: I think you should ask at forum.snapcraft.io
[12:45] <zyga-ubuntu> :)
[12:45] <sSs_> thanks!
[12:59] <zyga-ubuntu> jdstrand: hey
[12:59] <zyga-ubuntu> jdstrand: are you at the rally?
[13:00] <popey> zyga-ubuntu: he is
[13:00] <mup> PR snapd#3958 opened: many: add support for /home on NFS <Created by zyga> <https://github.com/snapcore/snapd/pull/3958>
[13:02]  * mwhudson waves at zyga-ubuntu
[13:02] <mwhudson> sadly
[13:04] <zyga-ubuntu> mwhudson: hey
[13:04] <zyga-ubuntu> :-(
[13:04] <zyga-ubuntu> yeah
[13:05] <zyga-ubuntu> popey: say hi to him :)
[13:23] <__chip__> o/
[13:37] <mup> Bug #1681547 changed: Gnome3 on Ubuntu 17.04 doesn't find snap desktop files <wayland> <Snappy:Fix Released> <https://launchpad.net/bugs/1681547>
[13:51] <ogra_> zyga-ubuntu, you just need http://bit.ly/2yDzMdg
[14:02] <mwhudson> can someone point me to the seeding code?
[14:04] <smallfoot-> Can you guys make a template for GNOME Builder that includes files to build a snap?
[14:05] <zyga-ubuntu> ogra_: hehe
[14:05] <zyga-ubuntu> ogra_: and someone to drive me around :)
[14:06] <zyga-ubuntu> smallfoot-: that's an interesting idea
[14:06] <mwhudson> also is there some way to make seeding extremely verbose?
[14:06] <ogra_> zyga-ubuntu, well, thats old ... nowadays you'd have a flying drone driven by ubuntu core ;)
[14:06] <zyga-ubuntu> smallfoot-: can you please post this proposal to forum.snapcraft.io so that it doesn't get lost?
[14:06] <zyga-ubuntu> ogra_: wait, there's a core refresh
[14:06] <zyga-ubuntu> xxxxx
[14:06] <ogra_> lol
[14:06] <zyga-ubuntu> ogra_: I see my dragonboard power usage spike whenever it reboots on core rebuild
[14:07] <ogra_> rebuild ? you mean refresh ?
[14:07] <zyga-ubuntu> well, rebuild that triggers refresh
[14:07] <zyga-ubuntu> yes
[14:08] <ogra_> all our default kernels boot with the performance cpufreq governor (to speed up booting) and use a script to switch to ondemand 60sec after the boot
[14:08] <ogra_> theoretically you shoulld see such a spike on every boot ... not typically related to the refresh itself
[14:08] <zyga-ubuntu> right, but it doesn't reboot otherwise :)
[14:08] <zyga-ubuntu> it runs 24/7
[14:08] <ogra_> yeah
[14:09] <zyga-ubuntu> ogra_: btw, did you see my lab?
[14:09] <ogra_> but it is just a coincidence
[14:09] <ogra_> i saw the pics from a while ago
[14:09] <ogra_> are there new ones ?
[14:09] <smallfoot-> zyga-ubuntu, I don't have any forum account on snapcraft.io
[14:09] <zyga-ubuntu> no, nothing new. I plan to add 4 more boards but I have no time to set them up
[14:09] <zyga-ubuntu> I need a small rack to keep this tidy
[14:10] <ogra_> well, now that you are idling at home and everyone esle is in NYC you should have some time ;)
[14:13] <zyga-ubuntu> ogra_: I'm not at home today
[14:14] <zyga-ubuntu> ogra_: but I can ssh home :)
[14:14] <ogra_> heh
[14:14] <zyga-ubuntu> ogra_: I mainly don't have a rack
[14:14] <zyga-ubuntu> ogra_: I had some errands to do in the morning, taxes and VAT paperwork
[14:14] <ogra_> home is where the authorized_keys is !
[14:14] <zyga-ubuntu> ogra_: hahaha :)
[14:14] <zyga-ubuntu> yeah
[14:15] <ogra_> i would love to give you my 2x1x1m server cabinet ... but i guess delivery would be really expensive
[14:15] <ogra_> (trying to get rid of it since ages)
[14:16] <zyga-ubuntu> hmmm
[14:16] <zyga-ubuntu> how heavy is it?
[14:16] <zyga-ubuntu> I have space for that
[14:17] <zyga-ubuntu> but I'd rather have small desk rack as I have separate office network and no wiring to where I could keep the rack
[14:17] <zyga-ubuntu> (the big rack)
[14:17] <ogra_> its a big metal cabinet with glass front and back doors probably somewhere between 50-100kg
[14:18] <zyga-ubuntu> nice, why do you want to let go of it?
[14:18] <ogra_> because even 20 of the boards i work with nowadays fit on a shelf ...
[14:19] <ogra_> it just takes space, i dont really have any big 19" server HW in use anymore
[14:19] <mwhudson> pedronis: are you looking at irc? :)
[14:19] <zyga-ubuntu> ogra_: can you send me a pic sometime (telegram is fine)
[14:20] <ogra_> yeah, remind me next week when i'm home
[14:20] <zyga-ubuntu> thank you!
[14:21] <smallfoot-> Why does 'snapcraft init' put the yaml file in snap/ instead of build-aux/snap/ ?
[14:22] <smallfoot-> Now it pollutes the root, instead of be like build-aux/snap/ and build-aux/meson/
[14:22] <mup> PR snapd#3957 closed: cmd,dirs: treat "liri" the same way as "arch" <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3957>
[14:36] <kyrofa> jdstrand, I assume you're at the rally?
[14:42] <mup> PR snapd#3959 opened: hooks: rename refresh to after-refresh <Created by stolowski> <https://github.com/snapcore/snapd/pull/3959>
[14:58] <mup> PR snapd#3956 closed: snap-confine: bind mount /usr/lib/snapd relative to snap-confine <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3956>
[15:02] <cachio> pstolowski, https://paste.ubuntu.com/25615089/
[15:07] <kyrofa> zyga-ubuntu, are you here?
[15:07] <kyrofa> (on IRC, I mean)
[15:07] <nacc> sergiusens: is the env stuff from c#1 in LP: #1600035 done? A comment from ~1 year ago says "we are also going to allow..." without any date
[15:07] <mup> Bug #1600035: no way to differentiate between build-time and run-time env vars in plugins <Snapcraft:Triaged by kyrofa> <https://launchpad.net/bugs/1600035>
[15:12] <nacc> kyrofa: or maybe you kow (about environment: / build-environment: in the yaml). That would I think basically drop my custom wrappers and plugin altogether
[15:13] <kyrofa> nacc, environment is there, yeah, should get rid of a lot of wrappers
[15:13] <kyrofa> nacc, build-env, I don't think so
[15:13] <kyrofa> nacc, environment is a key on each app you declare
[15:13] <kyrofa> (like plugs)
[15:13] <kyrofa> There _might_ be a global one... I can't remember
[15:14] <zyga-ubuntu> kyrofa: hey
[15:14] <zyga-ubuntu> kyrofa: yes
[15:14] <nacc> kyrofa: oh ok, it's not here: https://snapcraft.io/docs/build-snaps/syntax
[15:14] <kyrofa> Hey zyga-ubuntu! I see the kernel-module-control interface... any chance you could give me a quick synopsis of what that does?
[15:15] <nacc> kyrofa: that's still better than what I have, so that's fine :)
[15:15] <zyga-ubuntu> kyrofa: yes, sure
[15:15] <kyrofa> nacc, hmm, indeed. This will help: https://stackoverflow.com/questions/42991501/snapcraft-custom-ld-library-path
[15:15] <zyga-ubuntu> kyrofa: that interface allows the snap to insert/remove kernel modules
[15:16] <kyrofa> nacc, would you mind logging a bug for the missing docs, please? Against snapcraft
[15:16] <zyga-ubuntu> kyrofa: by itself, not with snapd acting at the middle man
[15:16] <zyga-ubuntu> kyrofa: so you can modprobe essentially
[15:16] <kyrofa> zyga-ubuntu, modules contained within an app snap?
[15:16] <zyga-ubuntu> kyrofa: tip: snap interface kernel-module-contorl
[15:16] <mup> PR snapd#3960 opened: travis: switch to container based test runs <Created by mvo5> <https://github.com/snapcore/snapd/pull/3960>
[15:16] <zyga-ubuntu> kyrofa: well, any, you can wget modules or stuff
[15:16] <kyrofa> zyga-ubuntu, dude, awesome. Is that privileged?
[15:16] <zyga-ubuntu> kyrofa: it's just the permission to perform the kernel operation
[15:16] <zyga-ubuntu> kyrofa: totally
[15:16] <zyga-ubuntu> kyrofa: it requires an assertion to connect
[15:16] <zyga-ubuntu> kyrofa: canonical-livepatch uses it
[15:18] <nacc> kyrofa: yep will do after a mtg
[15:19]  * zyga-ubuntu will EOD soon
[15:19] <zyga-ubuntu> any last calls from the Ubuntu rally?
[15:20] <zyga-ubuntu> mvo: what is the motivation for https://github.com/snapcore/snapd/pull/3960/files ?
[15:20] <mup> PR #3960: travis: switch to container based test runs <Created by mvo5> <https://github.com/snapcore/snapd/pull/3960>
[15:20] <zyga-ubuntu> mvo: is it just faster
[15:20] <mvo> zyga-ubuntu: correct
[15:20] <mvo> zyga-ubuntu: also more "machines" available
[15:20] <mvo> zyga-ubuntu: its a bit of an experiment right now
[15:20] <zyga-ubuntu> aha, thank you for the explanation
[15:20] <zyga-ubuntu> hehe, "machines" :-)
[15:21] <mvo> zyga-ubuntu: your welcome, we are currently trying to find out if this is true
[15:22] <mvo> zyga-ubuntu: right now there is quite a bit of lack between pushing a PR and the first time travis asssigns a worker
[15:22] <zyga-ubuntu> yep
[15:23] <zyga-ubuntu> "lag" I assume
[15:23] <zyga-ubuntu> we're using the KVM based machines and those just cost them more
[15:29]  * zyga-ubuntu EODs
[15:29] <zyga-ubuntu> have a great rally everyone!
[15:31] <nacc> sergiusens: what is the 'correct "program loader"'? and how is that determined?
[15:34] <jdstrand> kyrofa: yep, I'm here. zyga asked too if you see him
[15:59] <mup> PR snapd#3959 closed: hooks: rename refresh to after-refresh <Created by stolowski> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3959>
[16:02] <ogra_> ppisati, http://paste.ubuntu.com/25615430/ is the attempt to fix AlbertA and bschaefer's SD corruption ...
[16:17] <apol> sergiusens: https://paste.kde.org/prox9diqs
[16:21] <sergiusens> stgraber mind parsing what that means ^... this is on arch
[16:29] <stgraber> apol: you need the linux-userns kernel
[16:29] <stgraber> apol: the default Arch kernel doesn't have user namespaces so only privileged containers can be used until you switch to the linux-userns kernel
[16:29] <stgraber> apol: you can create privileged containers with -c security.privileged=true
[16:31] <apol> right...
[16:32] <apol> I'll try with  -c security.privileged=true
[16:36] <nacc> sergiusens: is there black voodoo going on that allows generated wrappers (in classic snaps) to have #!/bin/sh in them?
[16:37] <kwmonroe> is it possible to mount a rw slot (write: $SNAP_DATA) from a ro plug (target: $SNAP/foo)? with core 16-2.27.6, i get permission denied: http://paste.ubuntu.com/25615637/
[17:47] <sergiusens> nacc check snapcraft.internal.meta, but we don't generate wrappers for classic
[17:47] <nacc> ... sure you do :)
[17:48] <nacc> http://paste.ubuntu.com/25615968/
[17:48] <nacc> I don't konw *why* you do
[17:48] <nacc> http://paste.ubuntu.com/25615970/
[17:51] <sergiusens> nacc to allow you to specify `command: some-command -w $SNAP_USER_DATA`
[17:51] <sergiusens> nacc so, environment variables
[17:52] <nacc> sergiusens: right, so you *do* make wrappers :)
[17:52] <sergiusens> nacc yeah, we do; that dropped my mind
[17:52] <sergiusens> but...
[17:52] <nacc> sergiusens: yep, i imagine it's some voodoo so that /bin/sh isn't used from the host FS
[17:53] <sergiusens> nacc your thoughts on  https://github.com/snapcore/snapcraft/pull/1420 would be appreciated
[17:53] <mup> PR snapcraft#1420: add new "no-wrapper" property to apps <Created by mvo5> <https://github.com/snapcore/snapcraft/pull/1420>
[17:53] <nacc> sergiusens: i'll take a look :)
[17:54] <sergiusens> nacc for classic the voodoo is incomplete though, we would need to change it to `#!/snap/core/current/bin/sh`
[17:54] <nacc> sergiusens: i know little of the internals, but can give feedback
[17:54] <nacc> sergiusens: yep, that's what i'm havig to do in my scripts, or they segfault :)
[17:55] <sergiusens> nacc if you want to create a PR with that fix to use the correctly shebanged sh in the wrapper I would appreciate that ;-)
[17:55] <sergiusens> if not I'll take care of it
[17:55] <nacc> sergiusens: heh, i'll put it on my backlog :)
[17:56] <sergiusens> nacc if you can't get to it, just tell me and I'll take care of it
[17:57] <nacc> sergiusens: it's probably not going to bubble to the top of my queue anytime soon, so it's probably better for you to do
[18:11] <cachio> mvo, when you have a minute https://github.com/snapcore/spread-cron/pull/46
[18:11] <mup> PR spread-cron#46: Add configure files as part of the sync <Created by sergiocazzolato> <https://github.com/snapcore/spread-cron/pull/46>
[18:11] <mvo> cachio: sure, coming in a minute
[18:15] <ppisati> ogra_: http://people.canonical.com/~ppisati/linux-image-4.4.0-1075-raspi2_4.4.0-1075.83~ograsdquirks_armhf.deb
[18:15]  * ogra_ hugs ppisati ... 
[18:26] <mup> PR snapd#3961 opened: git: make the .gitingore file a bit more targeted <Created by mvo5> <https://github.com/snapcore/snapd/pull/3961>
[18:27] <jdstrand> nessita: hi! I just noticed that https://dashboard.snapcraft.io/dev/snaps/6058/rev/661/ is 'stuck'. the automated review passed, but it didn't get approved and there are a bunch of revisions after it pending review
[18:28] <jdstrand> nessita: (and it's showing up in https://dashboard.snapcraft.io/dev/snaps/reviewer/ubuntu/)
[18:29] <roadmr> jdstrand: hm, similar to what just happened with hugo, which I just unblocked
[18:29] <roadmr> jdstrand: ah! 6058 *is* hugo :)
[18:31] <roadmr> jdstrand: 661 is now ready to release? so is 662...
[18:31] <roadmr> jdstrand: revision 620 was pending resolution, so all subsequent uploads got held. I unblocked 620 and the queue is being processed...
[18:33] <roadmr> almost there, there are 714 revisions, it's up to 702 and working
[18:38] <roadmr> elopio1, jdstrand : all outstanding hugo uploads are reviewed, passed and ready to release
[18:48] <ogra_> pstolowski, i need the output of: grep . /sys/class/mmc_host/mmc0/mmc0:*/* 2>/dev/null
[18:49] <pstolowski> ogra_, http://pastebin.ubuntu.com/25616270/
[18:49] <ogra_> perfect !
[19:00] <navyguns> I was trying the tutorial found at snapcraft.io and followed it exactly but keep getting this error when running the snapcraft command: "Issues while validating snapcraft.yaml: found character '\t' that cannot start any token on line 14 of snap/snapcraft.yaml". I cannot find the "\t" character anywhere in the .yaml file. Anyone else run into this issue?
[19:01] <nacc> navyguns: it's a tab character
[19:02] <navyguns> Thanks. I'll check.
[19:03] <nacc> navyguns: my guess would be mixing tabs and spaces, possibly?
[19:07] <navyguns> Yes, that was it. Now i'm getting  a "mapping here on line 2" which contains Version: '2.10"
[19:12] <navyguns> Well, got rid of those errors.  Executing snapcraft now produces a bunch of python3 code errors and then quits. Running on Mint 18.2 Cinnamon.
[19:21] <elopio1> thank you. I've notified them in the bug. And thanks jdstrand for looking at it too.
[19:23] <nacc> navyguns: 'code errors'? Can you pastebin the command and output?
[19:24] <willdeberry> quit
[19:26] <navyguns> https://pastebin.com/WprAeU7Q
[19:28] <nacc> navyguns: it would appear that mint's snapcraft doesn't work?
[19:29] <nacc> navyguns: dunno, that error implies no subclass is being used
[19:31] <navyguns> Thanks for looking. I'm going to have to deal with it later. Work calls.
[19:36] <kwmonroe> heyo jdstrand: i can't figure out a hook that i can call to setup a content plug subdirectory early enough to beat the interface auto-connect.  does such a thing exist?  (install, prepare-plug-foo don't seem to work).  when you get some time, can you advise on https://bugs.launchpad.net/snapd/+bug/1719370
[19:36] <mup> Bug #1719370: snaps with content plug fail to install with auto-connect <snapd:New> <https://launchpad.net/bugs/1719370>
[19:38] <kwmonroe> i have a couple workarounds:  1) install the plug snap first, then the slot snap, or 2) work out something using the home interface.  ideally though, i'd like to keep these bits in a $SNAP_x directory vs every users' $HOME.
[20:18] <mup> PR snapd#3961 closed: git: make the .gitingore file a bit more targeted <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3961>
[20:31] <mup> PR snapd#3962 opened: tests: Increase SNAPD_CONFIGURE_HOOK_TIMEOUT to 3 minutes to install real snaps <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/3962>
[20:34] <gouchi> hi
[20:34] <gouchi> to use https://build.snapcraft.io
[20:34] <gouchi> the snapcraft.yaml needs to be in the root or snap directory only ?
[20:35] <gouchi> it can't look other directory ?
[20:36] <nacc> gouchi: where else would you like it to live? snap sources often have toplevel snap/
[20:37] <gouchi> some software may organize their source differently with sub directory
[20:37] <gouchi> for instance pkg/deb, pkg/rpm , pkg/snap ...
[20:38] <gouchi> not necessarily in snap/
[20:45] <gouchi> it will be great if you can specify custom path to snapcraft.yaml for the building process
[20:48] <kwmonroe> +1 gouchi.. fwiw, i'm writing snaps for apache bigtop which keeps their packaging bits in ./pkgs/src/[deb|rpm].  my workaround for now is to maintain intermediate repos for use by the snap builders (1 snap per repo, each with ./snap/snapcraft.yaml).  i plan to manually sync those with upstream periodically, but if the builders supported a user-specified snapcraft.yaml location, that'd be awesome!
[20:51] <nacc> gouchi: it depends, i guess
[20:51] <nacc> as kwmonroe said, it's trivial to create just a basically empty repo with snap/ inn it
[20:51] <nacc> that fetches the 'upstream' source via git
[20:51] <nacc> (in the yaml)
[20:52] <gouchi> yes
[20:53] <nacc> kwmonroe: why do you need to sync yours with upstream?
[20:53] <nacc> kwmonroe: that is, why isn't the upstream a part in your yaml
[20:55] <kwmonroe> nacc: the upstream is a part of my yaml (https://github.com/juju-solutions/snap-hadoop/blob/master/snap/snapcraft.yaml#L100) just like you said -- fetching upstream in one of my parts.  but since bigtop houses rpm and deb control files, it'd be nice to stick ./snap up there too.
[20:55] <kwmonroe> to clarify, the nice part would be if a snap builder (snapcraft or lp) would let me specify the snapcraft.yaml location in the repo when i register it to build.
[20:56] <nacc> kwmonroe: oh i see, so they could do some testing? and for the latter, so you don't need the intermediary
[20:56] <kwmonroe> yup
[20:56] <nacc> (and for the former, to match their other stuff)
[20:56] <nacc> got it
[20:59] <kwmonroe> fwiw nacc, projects like bigtop house 30ish other projects (https://github.com/apache/bigtop/tree/master/bigtop-packages/src/deb), so if i wanted to have a snap for each of those, i'd be maintaining 30is intermediate repos.
[21:00] <nacc> kwmonroe: true enough
[21:11] <mup> PR snapcraft#1570 opened: Don't fail over empty or faulty lines <Created by aleixpol> <https://github.com/snapcore/snapcraft/pull/1570>
[21:14] <mup> PR snapcraft#1571 opened: Make sure we don't try to include an empty set <Created by aleixpol> <https://github.com/snapcore/snapcraft/pull/1571>
[21:14] <apol> kyrofa: https://github.com/snapcore/snapcraft/pull/1571 https://github.com/snapcore/snapcraft/pull/1570
[21:14] <mup> PR snapcraft#1571: Make sure we don't try to include an empty set <Created by aleixpol> <https://github.com/snapcore/snapcraft/pull/1571>
[21:14] <mup> PR snapcraft#1570: Don't fail over empty or faulty lines <Created by aleixpol> <https://github.com/snapcore/snapcraft/pull/1570>
[21:48] <mup> PR snapd#3963 opened: cmd/snap-confine: add support for per-user mounts <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/3963>
[21:54] <sergiusens> flexiondotorg `export SNAPCRAFT_CONTAINER_BUILDS=1`
[21:56] <apol> sergiusens: thanks
[22:05] <mup> PR snapcraft#1572 opened: catkin plugin: allow ROS_MASTER_URI change <Created by cratliff> <https://github.com/snapcore/snapcraft/pull/1572>