[03:08] <liuxg> ping woodrowshen
[06:40] <pitti> Good morning
[06:40] <pitti> Chipaca: I am now
[07:45] <renat> Hi all. It's renat from Screenly. I have a question about snapcraft tool. I want to specify $SNAP_APP_DATA_PATH but
[07:46] <renat> But I get this error: "services description field 'Start' contains illegal 'usr/bin/screenly-playlist.wrapper -c '$SNAP_APP_DATA_PATH/config.yaml'' (legal: '^[A-Za-z0-9/. _#:-]*$')
[07:46] <renat> "
[07:46] <deenlee> eww
[07:47] <renat> Does this mean that I shouldn't use environment variables in a start command, or it's a bug?
[07:55] <dholbach> good morning
[08:04] <liuxg> dholbach, ping
[08:07] <dholbach> hi liuxg
[08:08] <liuxg> dholbach, I created a python project using requirements.txt at https://github.com/liu-xiao-guo/restapi
[08:09] <dholbach> liuxg, I never played around with pip and snapcraft
[08:09] <liuxg> dholbach, however, there is a problem with the project. It works well on the desktop. When I deploy it onto KVM, it does not work. I see a symbolic link in the snap file http://paste.ubuntu.com/13780578/
[08:10] <liuxg> dholbach, would you please help me to confirm whether it is a bug or not.
[08:10] <dholbach> let me see
[08:11] <liuxg> dholbach, thanks a lot. the django stuff seems not packaged into the snap though they are pulled down.
[08:11] <ricmm_> renat: it means the path is just a path, not a command line
[08:12] <ricmm_> you should put this -c ARG into the wrapper itself
[08:12] <dholbach> liuxg, why don't you use django from the Ubuntu archive? didn't that work? or do you strictly need django 1.9?
[08:13] <dholbach> liuxg, for me django is contained in the snap
[08:13] <dholbach> it's in ./usr/lib/python2.7/dist-packages/django
[08:13] <dholbach> (run dpkg -c mysnap.snap | less)
[08:14] <liuxg> dholbach, in fact, anything should work. I just tried to see whether it works or not. if I want to use it from the ubuntu archive, I should use the "stage-packages", right?
[08:14] <dholbach> yep
[08:15] <liuxg> dholbach, after I deploy it, it is a little strange, in the KVM, it is a symbolic link there though the file is in the "snap" directory.
[08:17] <liuxg> dholbach, this is what is seen in my place http://paste.ubuntu.com/13780734/
[08:18] <dholbach> yes, it's a broken symlink
[08:19] <dholbach> so yes, I can confirm the issue
[08:19] <liuxg> dholbach, is this a bug in the tool?
[08:20] <liuxg> dholbach, maybe I need to report a bug for it?
[08:20] <dholbach> yes, as far as I can tell, there shouldn't be symlinks going to locations which just exist in your home-directory when snapping
[08:20] <dholbach> yes
[08:20] <dholbach> your case is very good for testing
[08:21] <liuxg> dholbach, it took me quite a while to debug this problem
[08:21] <renat> ricmm_, thanks. I was thinking about it. I can't do it from a snapcraft. So I decided to create a bug in the launchpad.
[08:22] <ricmm> renat: I dont understand, why cant you do it with snapcraft?
[08:22] <dholbach> liuxg, maybe we can, as a safety measure, get the reviewers tools to give a warning if the symlinks are going to be broken
[08:22] <dholbach> liuxg, let me know once you've filed the bug
[08:22] <ricmm> you are using a wrapper script, so those arguments are better suited inside of the wrapper
[08:22] <liuxg> dholbach, sure, I am reporting a bug for it.
[08:24] <dholbach> thanks liuxg
[08:27] <liuxg> dholbach, i have reported the bug at https://bugs.launchpad.net/snapcraft/+bug/1523384. please take a look at it. I hope it can fixed soon!
[08:28] <dholbach> brilliant - thanks
[08:28] <dholbach> I'll add a task for the reviewers tools as well
[08:29] <liuxg> dholbach, thanks for your confirmation. I think this is a serious bug for it :)
[09:00] <renat> ricmm, that wrapper script is created by snapcraft tool. So I want it  to include my command line options.
[09:03] <ricmm> ahh I understand, yes
[09:04] <ricmm> renat: you can modify the .wrapper in snap/ and manually build, or make your own and put it in the right location with a copy plugin
[09:55] <mvo> ogra_: any concerns about http://paste.ubuntu.com/13782938/ ? we currently rely on /etc/sudoers.d/90-cloud-init-users for sudo but it seems a group makes more sense
[09:57] <ogra_> mvo, no objections at all ... but doesnt that also need a change in could-init then ?
[09:58] <ogra_> (it creates some stuff in /etc/sudoers.d IIRC)
[10:00] <mvo> ogra_: it won't hurt (the cloudinit stuff). its just *if* we use a system without cloud init (a os snap) then things still work with sudo, right now they don't without cloud init
[10:00] <mvo> ogra_: I will upload then, thanks for the sanity check
[10:00] <ogra_> ah, cool, yeah, if it is preventive thats fine indeed :)
[10:14] <mvo> ogra_: looks like bzr and archive are out of sync *grrr*
[10:14] <ogra_> oh ?
[10:17] <ogra_> and sil2100's last commit misses a changelog entry
[10:18] <mvo> ogra_: indeed it does
[10:18] <ogra_> wow, what a mess
[10:18] <mvo> choas!
[10:19] <mvo> ogra_: I will untangle the mess (unless you are already on it)
[10:20] <ogra_> no, i only checked, didnt start anything yet
[10:21] <mvo> ogra_: ok, should be fixed in some minutes
[10:42] <Chipaca> pitti: it seems systemd's journal loses messages during shutdown
[10:42] <Chipaca> pitti: is this expected?
[10:42] <Chipaca> pitti: or are we doing something wrong?
[10:44] <Chipaca> pitti: as in: 'stop' action prints some messages that normally appear in journal, but they're nowhere to be seen on shutdown, but stop action can be seen to be working by tee'ing the messages to a file under its control
[10:46] <renat> ricmm, seems it's really possible to use shell variables. You may see here that "args" argument is not used in _wrap_exe. https://github.com/ubuntu-core/snapcraft/blob/a06a75e70bcbc76f02f4cbeacee11010f3f24440/snapcraft/meta.py#L256
[10:48] <renat> ricmm, thanks for help. I want to experiment with snapcraft and see what I can improve.
[11:01] <Guest9543> stevebiscuit: hello
[11:01] <stevebiscuit> beowulf: 'ello
[11:02] <beowulf> mvo: Chipaca: stevebiscuit is the "Steve" for webdm now
[11:02] <stevebiscuit> there can be only one
[11:41] <mvo> stevebiscuit: welcome!
[11:41] <stevebiscuit> mvo: cheers :)
[13:10] <rsalveti> ogra_: ricmm: so, what are the kernel plans for dragonboard?
[13:10] <rsalveti> I want to make sure we're aligned in there somehow
[13:10] <rsalveti> and avoid yet another kernel tree
[13:10] <ogra_> rsalveti, no idea, waiting for ppisati ...
[13:10] <ogra_> i just want his deb ;)
[13:10] <ogra_> <- lazy
[13:11] <rsalveti> got it :-)
[13:11] <rsalveti> tell him to ping me later
[13:12] <ogra_> he is out today i was just told
[13:12] <ogra_> so probably rather tomorrow
[13:12] <rsalveti> yeah, no worries :-)
[13:12] <rsalveti> ogra_: next ubuntu release is going to use 4.4, right?
[13:12] <ogra_> do you know if i need all of the 8 boot partitions ?
[13:12] <ogra_> i.e. the blob stuff
[13:13] <rsalveti> didn't yet try booting without them, so not so sure
[13:13] <ogra_> ok, then i'll do trial and error as usual :)
[13:14]  * ogra_ is still pondering how to reflect that partition mess in the oem snap 
[13:17] <ogra_> hmm, tha dragonboard u-boot tree or the booti command dont understand CONFOG_RAW_IN'ITRD
[13:18] <ogra_> even with the option set i need to use an uInitrd
[13:18] <rsalveti> just ping the maintainer, he can easily find out why
[13:18] <rsalveti> hallor at #96boards
[13:18] <ogra_> ah i *knew* there was a board channel :P
[13:29] <pitti> Chipaca: are these messages from very late shutdown, perhaps after journal already stopped?
[13:29] <pitti> Chipaca: also, I thought snappy uses ephemeral journal only (i. e. not in /var/log)?
[13:29] <ogra_> pitti, no, it uses both
[13:29] <ogra_> we have rsyslog installed and running
[13:33] <pitti> Chipaca: oh, you mean you are not seeing late messages in /var/log/syslog? that's rsyslog, not journal
[13:33] <pitti> rsyslog gets stopped earlier indeed; but still a bit blurry about what kind of messages are missing
[14:08] <liuxg> Chipaca, ping
[14:30] <kyrofa> elopio, don't merge yet
[14:31] <elopio> kyrofa: ahhhh
[14:31] <kyrofa> Haha, that's okay
[14:31] <kyrofa> elopio, not important
[14:31] <elopio> kyrofa: I'm on the hangout.
[14:31] <kyrofa> elopio, getting on now
[14:43] <kyrofa> dholbach, so you've been adding some documentation for the snapcraft plugins?
[14:45] <dholbach> kyrofa, yep, I've been going through the app developer manual and checking where we could reintegrate some of the bits from there
[14:46] <kyrofa> dholbach, I'd like to help with documenting the ROS Catkin plugin
[14:47] <dholbach> kyrofa, it would probably make sense to make it a separate article, right?
[14:47] <dholbach> a tutorial with an example on how to use the plugin maybe?
[14:48] <kyrofa> dholbach, yeah probably
[14:48] <dholbach> kyrofa, probably easiest to just add it to snapcraft trunk and we import it from there :-)
[14:48] <kyrofa> dholbach, okay. You're pulling from 1.x, right?
[14:49] <kyrofa> elopio, how do you feel about cherry-picking the ROS plugin updates into 1.x?
[14:49] <dholbach> kyrofa, right now yes, but soon from both
[14:49] <kyrofa> dholbach, oh good to know
[14:49] <dholbach> kyrofa, right now it's still manual, but we're working on the automatic imports
[14:50] <kyrofa> dholbach, do you have a favorite article who's format I can follow?
[14:51] <elopio> kyrofa: I would prefer not to touch the other branch if we don't have to. Maybe once you finished doing all the changse and are totally happy with the plugins, we can just replace them.
[14:51] <kyrofa> elopio, good deal
[14:52] <dholbach> kyrofa, no, not really - maybe just make it a walkthrough how to turn an existing ROS project into something which works with snapcraft?
[15:05] <kyrofa> dholbach, right, I guess that was more of a "where exactly should I put it and how do I make it look similar" question
[15:05] <dholbach> kyrofa, if you just place it as a .md file in snapcraft's ./docs that should be good enough
[15:06] <kyrofa> dholbach, alright. Would it be worth creating a "plugins" subdir there so that directory doesn't just balloon as we add plugin docs?
[15:06] <dholbach> I don't know
[15:07] <kyrofa> dholbach, not important I suppose. I'll just add to the root for now and we can move stuff around if necessary
[15:07] <dholbach> yep, let's do that
[16:04] <plars> elopio: joining?
[16:04] <elopio> plars: uf, sorry.
[21:09] <sergiusens> kyrofa, elopio, in case you are feeling bored https://github.com/ubuntu-core/snapcraft/pull/160
[21:10] <kyrofa> Hey sergiusens, how is brazil?
[21:11] <sergiusens> kyrofa, great, going out for dinner now; but the sprint conversation was great, covered many things, all snaps and capabilities more than anything else
[21:11] <sergiusens> tomorrow it will be assertions
[21:11] <kyrofa> sergiusens, awesome :)
[22:02] <genii> blount