[00:25] <mup> PR snapcraft#1015 opened: tests: reorganize command tests into subdirectory <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/1015>
[00:43] <mup> PR snapcraft#996 closed: Updated nodejs plugin to use get_build_properties() <Created by ZenHarbinger> <Merged by kyrofa> <https://github.com/snapcore/snapcraft/pull/996>
[01:49] <knight__> Ok folks, so how can I run a mkdir in a snapcraft.yaml inside of a part before it builds?
[01:53] <knight__> shell-command?
[02:19] <grapestomper> knight - do you know how to make snapcraft execute a shell command during the build process?
[02:51] <knight__> grapestomper, yes, but i'm not sure if that will fire before, during, or after the build itself
[02:54] <knight__> it seems that i can create a part focused on shell commands, but i can't run an arbitrary shell command inside of a part itself
[03:09] <knight__> it looks like i have to make the part a shell plugin and do the compilation manually in shell commands, rather than use the make plugin
[03:20] <knight__> what version of snapcraft has the new shell plugin?
[03:32] <grapestomper> knight - kindof greek to me. I have also wanted to know who to do this.
[03:32] <grapestomper> who = how
[03:42] <mup> Bug #1651936 opened: autopkgtests fail on ppc64el <Snappy:New> <https://launchpad.net/bugs/1651936>
[05:02] <grapestomper> first time using snapcraft to compile with make = error
[05:02] <grapestomper> here is the error I am seeing ->> http://pastebin.com/vSXsAyGB
[05:03] <grapestomper> here is the source ->> https://github.com/chadyoungdell/Snappy_Ubuntu_Core/tree/master/Snapcraft_2.x/hello_cpp
[05:03] <grapestomper> would someone mind taking a look?
[05:03] <grapestomper> the standalone Makefile works fine, but add snapcraft and it pukes
[06:57] <liuxg> nowadays, I see  a lot of "Use of build-properties in the schema is deprecated" during building a snap project. How can I get rid of the warnin? thanks
[08:49] <aravinth> system
[08:50] <aravinth> ignore
[08:50] <aravinth> ignore_all
[11:22] <mup> PR snapcraft#1016 opened: cmake: extend parte build properties as it extends make <Created by 3v1n0> <https://github.com/snapcore/snapcraft/pull/1016>
[11:40] <mup> PR snapcraft#1017 opened: make: add support for cwd path <Created by 3v1n0> <https://github.com/snapcore/snapcraft/pull/1017>
[13:29] <cachio> ogra_, hey, I am integrating some tests execution in jenkins and I would like to trigger the job when a new core is available in edge channel, do you already have something for that? I mean automatically detect there is a new available version
[13:31] <ogra_> cachio, not really, you could screen scrape the timestamp from http://people.canonical.com/~ogra/core-builds/ but that only monitors automated builds ...
[13:31] <ogra_> if you want to do it properly you probably want to write an lp-lib script
[13:33] <cachio> ogra_, ok
[13:36] <cachio> ogra_, I'll start checking in that page from jenkins and then I'll og for a lp-lib script
[13:37] <ogra_> sounds like a plan :)
[13:37] <cachio> ogra_, yes, kind of
[14:36] <liuxg> sergiusens, now I have found the same issue as https://bugs.launchpad.net/snapcraft/+bug/1650946, how can I resolve this problem? thanks
[14:36] <mup> Bug #1650946: unhelpful error when building a classic snap: classic confinement requires the core_dynamic_linker to be set <Snapcraft:New> <https://launchpad.net/bugs/1650946>
[15:18] <grapestomper> looking for help on an error I am seeing ->> http://pastebin.com/vSXsAyGB
[15:50] <mup> PR snapcraft#1016 closed: cmake: extend parte build properties as it extends make <Created by 3v1n0> <Closed by 3v1n0> <https://github.com/snapcore/snapcraft/pull/1016>
[15:53] <mup> PR snapcraft#1018 opened: autotools: extend Make plugin instead of repeating code <Created by 3v1n0> <https://github.com/snapcore/snapcraft/pull/1018>
[16:55] <mup> PR snapd#2529 opened: interfaces: mm: permissions for protocol proxies <Created by alfonsosanchezbeato> <https://github.com/snapcore/snapd/pull/2529>
[18:38] <mup> PR snapcraft#997 closed: plugins: update go plugin to use get_build_properties() <Created by ZenHarbinger> <Merged by kyrofa> <https://github.com/snapcore/snapcraft/pull/997>
[18:56] <mup> PR snapcraft#1019 opened: tests: reorganize state tests into subdirectory <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/1019>
[19:51] <mordor> hi all ... can I ask a question ?
[20:44] <mup> PR snapcraft#1002 closed: plugins: update python plugin to support get_pull_properties() <Created by ZenHarbinger> <Merged by kyrofa> <https://github.com/snapcore/snapcraft/pull/1002>
[21:02] <wililupy> Is there an example of using the shell snippets in snapcraft?
[21:03] <kyrofa> wililupy, yessir, hold on
[21:03] <wililupy> thanks kyrofa.
[21:05] <kyrofa> wililupy, well, wait. Are you just wanting to run a shell script? Or run specific parts of the build via shell commands?
[21:05] <kyrofa> Hmm... those sound the same huh :P
[21:05] <wililupy> kyrofa: run a shell script.
[21:07] <kyrofa> wililupy, to do what, exactly. Are we talking fboss here?
[21:07] <wililupy> kyrofa: yes. I want to see what happens if I run this shell script that was sent to me to build it.
[21:08] <kyrofa> wililupy, well the `apt install` commands might prove troublesome if you ever want to build on launchpad, so I still recommend extracting those into build/stage packages as necessary
[21:08] <kyrofa> wililupy, but other than that, I'd wrap the script in a Makefile so you can take care of the install step as well
[21:08] <kyrofa> (since they don't write any)
[21:08] <kyrofa> Then you can get rid of your custom plugin
[21:10] <wililupy> kyrofa, this is just for a test right now. I should be able to use the dump plugin for install since its just the agent and a config file.
[21:10] <wililupy> oh, and the py for testing the routes.
[21:11] <kyrofa> wililupy, I'd still do it in a Makefile, just make an install rule that does nothing if you like
[21:12] <wililupy> kyrofa: Ack.
[22:05] <mcphail> Hi. I'm trying to use "snapcraft cleanbuild" but I'm getting errors about missing network access as per http://termbin.com/xcfe . I know nothing about setting up networks in lxc. Shouldn't this be handled automatically by snapcraft? How can I fix this?
[22:06] <grapestomper> mordor - what was your question?
[22:08] <grapestomper> kyrofa - do you know how to make a file get moved to the users home dir (/home/user) when a snap get installed? if so can you point to an example?
[22:08] <kyrofa> mcphail, why do you think lxd doesn't configure it?
[22:09] <kyrofa> (snapcraft doesn't for the same reasons)
[22:10] <kyrofa> grapestomper, there are a number of ways. You can do it in a wrapper script upon startup, or you can do it in the `configure` hook assuming you're up-to-date enough to use it
[22:10] <mcphail> kyrofa: this is opaque to me just now. What do I need to understand to resolve it?
[22:10] <kyrofa> grapestomper, which sounds best to you? Then I can show you an example :)
[22:11] <kyrofa> mcphail, yeah, ignore snapcraft. Get lxd/lxc working, and once you have that cleanbuild will work
[22:11] <kyrofa> mcphail, let me find something, hold on
[22:11] <mcphail> kyrofa: thanks
[22:11] <kyrofa> mcphail, I think this might help: https://insights.ubuntu.com/2016/04/07/lxd-networking-lxdbr0-explained/
[22:12] <kyrofa> Hrmm... no wait
[22:12] <kyrofa> It's not that complex
[22:14] <kyrofa> mcphail, yeah, just run `sudo lxd init`
[22:15] <kyrofa> It's a little wizard that'll walk you through setting stuff up
[22:15] <mcphail> kyrofa: ok, although I'm sure I've played with lxd on this box before...
[22:15] <kyrofa> mcphail, snapcraft just runs `lxd launch ubuntu:xenial -e` essentially
[22:15] <kyrofa> Err, lxc
[22:15] <mcphail> "error: You have existing containers or images. lxd init requires an empty LXD."
[22:16] <grapestomper> kyrofa - thanks, do you now know were I can start reading about wrapper scripts? I dont see this on the snapcraft page. I will seach for the configure hook on my own.
[22:16] <kyrofa> grapestomper, there's nothing to read. Let's say you have a binary called X that you wanted to run as a service
[22:17] <kyrofa> grapestomper, but X requires a config file in $SNAP_DATA (or whatever)
[22:17] <kyrofa> grapestomper, so instead of using `command: X` in your YAML, you use `command: run-X` and write a script called `run-X` that copies the config file and then runs X
[22:18] <kyrofa> I forget X is an actual product. I should have used Y
[22:18] <grapestomper> kyrofa - thanks
[22:18] <kyrofa> mcphail, I suggest you read up on lxd/lxc, then: https://linuxcontainers.org/lxd/getting-started-cli/
[22:32] <kyrofa> grapestomper, here's an example: https://github.com/nextcloud/nextcloud-snap/blob/master/snapcraft.yaml#L35
[22:33] <kyrofa> grapestomper, that exists for two reasons: to create redis' logging directory, and rewrite its config: https://github.com/nextcloud/nextcloud-snap/blob/master/src/redis/scripts/start-redis-server
[22:38] <mup> PR snapcraft#993 closed: plugins: update qmake to use get_build_properties and get_pull_properties() <Created by ZenHarbinger> <Merged by kyrofa> <https://github.com/snapcore/snapcraft/pull/993>
[23:44] <mcphail> http://termbin.com/rv2u - this curses-based app prints garbage extra characters to the terminal when run as a snap, but works fine when run from stage/usr/local/bin/sneakers . Any idea what I need to tweak or add to get a curses app to work properly?