[00:10] <mhall119> sergiusens: if you're around tomorrow, I could really use your help with some cmake/pkg-config problems I'm having
[00:26] <Shibe> in a snappy system, will apt still be used for core parts of the system such as kernel and drivers?
[00:31] <mhall119> sgclark: d_ed: we've started sending out a weekly email higlighting snap work from the community, do you have a few bullet points about what you've been doing that I can include?
[02:32] <nhaines> Shibe: no.
[03:21] <nhaines> I give up.  I'm trying to snapify a script that calls sox via play, and I can't get any progress past "play FAIL sox: Sorry, there is no default audio device configured".
[03:22] <nhaines> The "pulseaudio" interface is defined and connected.  I don't know whether or not I'm supposed to have PulseAudio installed in the snap (it doesn't seem to make a difference) or for that matter, why sox works immediately on a classic system and has no configuration inside a snap.
[03:23] <nhaines> I have installed libsox-fmt-pulse.  I come back to it every week and it's been five weeks and I'm stumped.
[03:24] <elopio> nhaines: does it fail even with --devmode ?
[03:25] <elopio> thomi: hey, I see in keybaise that you have an invitation available... :)
[03:25] <elopio> *keybase
[03:25] <thomi> elopio: I sure do - you want one?
[03:26] <nhaines> elopio: it does!
[03:26] <elopio> thomi: yes please.
[03:26] <thomi> elopio: PM me your email address
[03:27] <elopio> nhaines: please report a bug. Sounds like sox needs configuration, which I have no idea how to do.
[03:27] <nhaines> elopio: after 5 weeks of trying, neither do I!  :)
[03:28] <nhaines> But I hate to report a bug if it's really me just being dumb.  :)
[03:30] <elopio> nhaines: that's what I do all day!
[03:31] <nhaines> heh  :)
[03:32] <nhaines> What project do I file against in LP?
[03:44] <elopio> nhaines: snappy
[03:47] <nhaines> Now to figure out how to protect my suuuuuper secret proprietary one-line sox command trade secrets!
 Shibe: no.
[03:55] <Shibe> okay, so how will drivers and kernels be installed/updated in snappy?
[03:55] <Shibe> isn't each snap isolated from the rest of the system?
[03:57] <nhaines> Shibe: drivers will be part of the gadget snaps and kernels will be part of the kernel snaps.
[03:58] <Shibe> nhaines: is there any information about these "gadget/kernel snaps"?
[03:59] <nhaines> https://developer.ubuntu.com/en/snappy/ under System Overview
[04:00] <nhaines> Also probably https://developer.ubuntu.com/en/snappy/guides/porting/
[04:21] <ePierre> hello!
[04:21] <ePierre> I'm trying to create a snap from a Python package. I've managed to create the snap, but when I try to run it, I have the following issue:
[04:22] <ePierre> locale.setlocale(locale.LC_ALL, '')
[04:22] <ePierre>   File "/home/pierre/dev/rapid/parts/rapid/install/usr/lib/python3.5/locale.py", line 595, in setlocale
[04:22] <ePierre>     return _setlocale(category, locale)
[04:22] <ePierre> locale.Error: unsupported locale setting
[04:38] <ePierre> argh. Now I get another error when trying to re-build the snap. → "ImportError: No module named 'DistUtilsExtra'" although in my snapcraft.yaml, I have
[04:39] <ePierre> build-packages:
[04:39] <ePierre> - python3-distutils-extra
[04:39] <ePierre> looks like snapcraft doesn't downloaded this package before trying to build...
[04:39] <ePierre> (but it worked before and I don't know how)
[05:30] <nhaines> https://bugs.launchpad.net/snappy/+bug/1593558
[06:00] <trijntje> I've installed a snap as user1, but I can't use it as user2. When I want to install it for user2, I get a message that the snap is already installed. Is that a known limitation or should I file a bug?
[06:01] <trijntje> hmm, it looks like /snap/bin is not in the PATH of the new user I created with adduser
[06:07] <qengho> trijntje: $ grep /snap /etc/profile.d/*
[06:07] <trijntje> /etc/profile.d/apps-bin-path.sh:# Expand the $PATH to include /snap/bin which is what snappy applications
[06:07] <trijntje> /etc/profile.d/apps-bin-path.sh:PATH=$PATH:/snap/bin
[06:08] <trijntje> qengho: I've added /snap/bin to my PATH as a temporary fix
[06:11] <trijntje> It happens both for users added with adduser and via the gui. Should I file a bug against snapd for this problem?
[06:11] <dholbach> hey hey
[06:24] <trijntje> https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1593578
[06:26] <qengho> trijntje: What shell do new users have? Check /etc/passwd .
[06:27] <trijntje> qengho: /bin/bash, same as the first user
[06:28] <qengho> trijntje: Is anything in their home clobbering PATH var? Also see /etc/skel/ .
[06:32] <trijntje> qengho: no, only /etc/skel/.profile adds $HOME/bin to PATH.
[06:32] <trijntje> echo $PATH
[06:32] <trijntje> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
[06:37] <nhaines> dholbach: morning!
[06:39] <dholbach> hi nhaines
[06:41] <qengho> trijntje: $ ls -l /etc/profile.d/apps-bin-path.sh
[06:42] <trijntje> $ ls -l /etc/profile.d/apps-bin-path.sh
[06:42] <trijntje> -rw-r--r-- 1 root root 101 mei  3 08:00 /etc/profile.d/apps-bin-path.sh
[06:48] <qengho> trijntje: That doesn't make sense. Something you said is wrong. At login, bash "runs" /etc/profile, which runs /etc/profile.d/*, which sets PATH to include /snap/bin . Put a "echo hi" in /etc/profile.d/apps-bin-path.sh to see if/that it's running.
[06:50] <trijntje> qengho: you are right. If I do a real login, snap is in the path. I was just using 'su user' from a terminal, and if I do that its not in the path
[07:01] <nhaines> dholbach: snapcraft frustrates me, as I've been unable to build absolutely anything.  But I've destroyed whole development systems over and over in lxc containers while my laptop's 16.04 LTS install remains pristine, and *that's* been really pleasant.  :)
[07:11] <trijntje> qengho: what does this mean for the bug? Is it invalid/expected behaviour?
[07:15] <d_ed> mhall119: * patched parts of KDE frameworks to support KIO in snappy
[07:15] <d_ed> mhall119: thus fixing downloading/file browsing
[07:17] <qengho> trijntje: well, the bug-report title should be changed to mention "su".
[07:20] <dholbach> nhaines, maybe if you post your snapcraft.yaml somewhere, somebody can help you?
[07:20] <dholbach> nhaines, or you ask a more specific question?
[07:24] <trijntje> qengho: I've added this to the bug report, thanks for your help
[07:24] <ePierre> hey there
[07:25] <ePierre> I'm trying to create a snap for this app: https://launchpad.net/rapid
[07:25] <ePierre> I bzr branched the code (bzr branch lp:rapid), then created a snapcraft.yaml file, but I cannot build it
[07:25] <qengho> trijntje: In the mean time, $ su other -
[07:26] <ePierre> it worked once (but then I couldn't run the program, which is another issue), and since then, whenever I try to rebuild, I get an error
[07:26] <qengho> That's all. sic
[07:26] <ePierre> both snapcraft.yaml and error are here: http://paste.ubuntu.com/17426643/
[07:26] <ePierre> does anyone have a clue of what's going on?
[07:27] <qengho> ePierre: also use "--debug" as arg to snacraft.
[07:29] <ePierre> qengho, ok. It provides a bit more info, but nothing interesting I think
[07:31] <nhaines> dholbach: I did!  It's in the bug report.  :)  https://bugs.launchpad.net/bugs/1593558
[07:32] <dholbach> cool
[07:32] <qengho> ePierre: "cd parts/rapid/install; pip3 install"  # What is wrong with pip3 install there? How should you install?
[07:32] <qengho> ...if this were not a snap, what are install instructions?
[07:33] <nhaines> dholbach: although my attempt at snappifying hollywood didn't go anywhere either, which is sort of a shame.  :)
[07:33] <dholbach> bring it up on the mailing list
[07:34] <nhaines> Okay.  I'm shy of mailing lists when the more probable cause is my own incompetence.  :)
[07:34]  * nhaines tries to remember what the mailing list is caled this week.
[07:34] <ogra_> snapcraft@snapcraft.lol
[07:34] <ogra_> ;)
[07:34] <nhaines> ogra_: :D
[07:35] <nhaines> The list admin should really use the [snapcraft] prefix.
[07:35] <svij> ogra_: you forgot the "lists." before snapcraft.lol! :P
[07:35] <ogra_> ouch, indeed
[07:35] <ogra_> nhaines, so that you cant read the subject in dekko you mean ?
[07:35] <ogra_> yep, good idea :)
[07:36] <ePierre> qengho, there is an install script: https://launchpad.net/rapid/pyqt/0.9.0a3/+download/install.py
[07:40] <qengho> ePierre: plugins are only smart about standard ways of installing software parts. You could make your own plugin that runs that. Extend python3 module, perhaps.
[07:40] <trijntje> What is the proper way to create a snap for a program that can read files outside of the users home (eg /bigdata)
[07:41] <nhaines> ogra_: do that I can find them in Thunderbird.  Is there some strange Dekko bug?  :)
[07:41] <zyga> good morning
[07:42] <ogra_> nhaines, no, just a strange screen width of phones :P
[07:43] <ogra_> prefixing subjects is a pretty bad habit since it pushes the actual info you want to the right ... if your screen isnt particulary wide the text you want to read might not be readable anymore
[07:48] <nhaines> ogra_: that's what rotating the phone sideways is for, of course.  ;)
[07:48] <ogra_> sure ...
[07:48] <nhaines> The actual info I want tends to be "why am I getting these emails?"
[07:50] <ogra_> i get that by looking at the "To" address :)
[07:51] <nhaines> ogra_: I don't have time for that.  :)
[07:52] <ogra_> then use a proper filter ;)
[07:54] <trijntje> is it possible to have a snapped program read a file from outside the users home directory? 'my-app /path/to/data/file'
[07:56] <ogra_> not at the moment
[07:56] <morphis> zyga: ping
[07:57] <ogra_> well ... if you install with --devmode it might
[07:57] <zyga> morphis: hi
[07:57] <morphis> zyga: do you have time to take a last look at the modem-manager interface?
[07:58] <zyga> morphis: little but I can have a quick look now
[07:58] <trijntje> ogra_: I'll give devmode a try, thanks
[07:58] <morphis> zyga: we would like to get it merged, jdstrand already gave his +1
[07:58] <morphis> abeato: ^^
[07:58] <pmp> morning, I finally succeeded in building a custom kernel (which is correctly configured to working with ubuntu-core) for raspi with IIO support \o/
[07:58] <nhaines> Yay!
[07:59] <pmp> I finally could run a command from a snap which tries to access iio-devices
[07:59] <pmp> and it fails ! Yay!
[07:59] <nhaines> \o/
[07:59] <pmp> I'm using lsiio which access sysfs
[08:00] <pmp> my goal is to create a bug on launchpad which will make the devs create an appropriate interface - unless there is already one?! Hence my report here before posting a bug.
[08:02] <pmp> (I will also try to write an article/report on how I did to create an IIO-kernel for raspi based on 4.7-rc3 - it wasn't torture but not far from it. Thanks to ogra_ for supporting me all the time
[08:05] <trijntje> ogra_: putting 'devmode' in the snapcraft.yaml file did not work, but installing the snap with --devmode did. Thanks for the advice
[08:08] <dpm> seb128, good morning. I tried your suggestion last night http://paste.ubuntu.com/17426218 and that made dconf happy - thanks! The app started, but then apparmor blocks it as it's trying to write to /var/cache/fontconfig/
[08:08] <ePierre> qengho, thanks! I'll dig a bit more and perhaps discuss with the owner of the software about it
[08:10] <seb128> dpm, great for dconf! unsure about the fontconfig issue though
[08:10] <dpm> no worries, I'll keep investigating
[08:12] <seb128> dpm, first time I see that issue, you use the standard wrapper?
[08:13] <dpm> seb128, parts of it. It's the qt5-launch wrapper, to which I had to add some bits from the gtk wrapper for a qt app that uses gtk theming
[08:13] <seb128> dpm, is XDG_CACHE_HOME set?
[08:14] <dpm> seb128, yeah, that's one bit that I took from the gtk wrapper: https://github.com/dplanella/qt5conf/blob/with-gtk/qt5-launch#L53
[08:16] <seb128> dpm, sorry I don't know offhand
[08:16] <dpm> np, thanks anyway
[08:17] <ogra_> trijntje, yeah, the entry in snapcraft.yaml just makes sure that a snap from the store blocks when you install it without --devmode ...
[08:21] <trijntje> ogra_: I see. I was still able to install it though, I just got the same 'permission denied' error when I tried to read the file
[08:25] <ogra_> trijntje, yeah, but you installed it locally ... the a snap install from the store should behave differently
[08:26] <ogra_> we dont actually stop you from shooting both your feet when you sideload stuff ;)
[08:27] <trijntje> ogra_: that makes sense. I'll mostly be creating snaps for myself and some colleagues, so foot-shooting is no big deal ;)
[08:27] <ogra_> just wear these heavy duty shoes then ;)
[08:47] <didrocks> dholbach: dpm: did you get issues with snapcraft cleanbuild? I'm trying from snapcraft-example godd, run "snapcraft cleanbuild"
[08:47] <didrocks> I'm getting a lot of E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/f/file/python3-magic_5.25-2ubuntu1_all.deb  500  Internal Server Error
[08:47] <didrocks> in my new lxd container
[08:47] <didrocks> it doesn't refresh?
[08:48] <dholbach> it worked for other projects earlier
[08:48] <dpm> didrocks, it worked for me yesterday, I've not tested it today. I think someone mentioned this on gitter yesterday, and `lxd init` helped them
[08:48] <dholbach> let me try godd
[08:48] <didrocks> thanks :)
[08:48] <didrocks> keep me posted
[08:49] <dholbach> it wfm with godd - looks like snapcraft 2.11 can get all build-deps - trying with trunk
[08:50] <dholbach> hum... it install snapcraft 2.11 in the lxc container
[08:51] <dholbach> so yeah... it works
[08:52] <slvn> hello, I tried the "pulseaudio" interface on my snap, and it didnot seem to work. I have blocked message from app armor
[08:52] <didrocks> I'm going to try lxd init
[08:52] <didrocks> already ran :/
[08:52] <didrocks> hum, unsure what's happening
[08:58] <tsimonq2> didrocks: there's an open bug by Alan Pope reporting the 500
[08:58]  * tsimonq2 finds it
[08:59] <didrocks> oh great!
[08:59] <didrocks> popey: you have the same issue as well, did you get it fixed?
[08:59] <popey> didrocks: I am not here, but I did fix it
[09:00] <popey> nuke lxd/lxc config from orbit and start again
[09:00] <popey> it was lxc/lxd networking at fault, not snappy
[09:00]  * popey disappears in a puff of aether
[09:00] <didrocks> popey: always the big restart button! Many things, and good week-end! :)
[09:00]  * tsimonq2 chases after popey but to no avail, he is gone (:P)
[09:01] <tsimonq2> popey: have a good weekend :)
[09:31] <ePierre> When I try to build a snap from a Python3 project, what happens in snapcraft exactly? Cause in the project I'm trying to build, it requires a few packages to be installed (e.g. python3-gi), and they are installed on my system, and they are also in build-packages: section, but somehow the setup.py script doesn't seem to have access to them when I launch snapcraft
[09:37] <zyga> ePierre: you want them in stage-packages
[09:37] <zyga> ePierre: they are required at runtime, not just at build-time
[09:37] <zyga> ePierre: gi is gobject introspection
[09:37] <zyga> ePierre: that requires the actual shared objects (random .so files)
[09:37] <zyga> ePierre: the .gir files
[09:37] <ePierre> zyga, indeed... it seems to build properly now
[09:37] <zyga> ePierre: and then python[23]-gi itself
[10:34] <jdstrand> dpm: the access to /var/cache/fontconfig is non-fatal and almost certainly not why your app didn't work (consider the fact that it wants to write to a directory it doesn't have access to anyway-- that dir is root owned and your app runs as you)
[10:34] <jdstrand> it is a weird fontconfig thing
[10:37] <dpm> jdstrand, I figured out the /var/cache/fontconfig issue, as you say, it was a red herring. It turns out that the app ships a fonts.conf file that specifies that directory as the first to use in a list. I tried to alter that list with a local.conf file, which didn't work, and then figured out that the app was not starting because of a missing 'network-bind' plug, which snappy-debug hadn't flagged in previous tests
[10:37] <dpm> after it did, I added the plug and it then worked
[10:41] <pandaadb> Hi - I am trying to package a java server application with snappy for the first time. My jenkins server builds the things and I have a url for that (hardcoded for now).
[10:41] <pandaadb> What I would like to do is to download it (with auth)
[10:41] <pandaadb> is there a wget plugin?
[10:41] <pandaadb> or would that be the pull plugin
[10:41] <dpm> jdstrand, by the way, am I using snappy-debug correctly? It does not seem to work as expected -> http://paste.ubuntu.com/17428561
[10:43] <jdstrand> dpm: you said 'does not start the app', but it does-- it is tailing the log and will hang there until it has something to report
[10:43] <jdstrand> dpm: you can run it as non-root, but if you do you run the risk of hitting kernel rate limiting for log output
[10:44] <jdstrand> dpm: so, in earlier tests it might have been rate-limited or stopped before it hit the denial
[10:44] <jdstrand> (the app stopped before it hit the denial)
[10:44] <dpm> ack
[10:45] <dpm> jdstrand, so regarding the usage of snappy-debug, then it's better to launch the app in another terminal to at least see the UI?
[10:45] <jdstrand> dpm: there is no ui. think of it as a fancy 'tail -f /var/log/syslog'
[10:45] <jdstrand> well, there is no gui
[10:46] <jdstrand> there is cli output
[10:47] <dpm> jdstrand, right, I just thought that that would launch the app's UI rather than holding it
[10:47] <Mikaela> Is there any ETA for Firefox and LibreOffice snaps appearing?
[10:48] <tsimonq2> Mikaela: AFAIK there's already a LibreOffice snap
[10:49] <tsimonq2> Mikaela: http://news.softpedia.com/news/libreoffice-5-2-beta-2-now-available-as-a-snap-for-ubuntu-linux-other-distros-505263.shtml
[10:49] <tsimonq2> that's from two days ago
[10:50] <Mikaela> nice
[10:51] <pandaadb> Is there a place where the plugins are documented?
[10:53] <pandaadb> e.g. the curl plugin has no docs doing snapcraft help curl
[10:54] <tsimonq2> dpm, dholbach: ^
[10:55] <pandaadb> Maybe i should take a step back and find out if I am using this for the right purpose? I have the server app that is already built. I want to create a snap package that can be run anywhere. For this all i really need is to download the zip, unzip it in a location and setup the properties. After that it only needs to run
[11:19] <morphis> zyga: you had time for the modem-manager interface?
[11:22] <ogra_> morphis, not zyga, you know he is slacking all day :)
[11:22] <morphis> ogra_: I know, but it looks like nobody else can then approve my PR :-)
[11:35] <dholbach> pandaadb, https://developer.ubuntu.com/en/snappy/build-apps/plugins/
[11:35] <dholbach> there's no `curl` plugin, it's a part: https://wiki.ubuntu.com/Snappy/Parts
[11:36] <pandaadb> hey - thanks
[11:36] <dholbach> anytime :)
[11:36] <pandaadb> so downloading a zip somewhere is not what I am meant to do? I am starting to think I am using snappy for the wrong purpose
[11:38] <pandaadb> Oh okay - so using a "curl" part simply downloads curl into my snappy package so that curl is available
[11:38] <zyga> morphis: I'm still reading it
[11:38] <zyga> morphis: I'll land it shortly
[11:38] <zyga> morphis: it's just very long :)
[11:39] <morphis> zyga: awesome! :-)
[11:39] <zyga> morphis: I think you will be happy to hear about that you may soon get auto-connecting network-manager
[11:40] <zyga> morphis: internally plugs and slots will auto-connect within one snap
[11:40] <morphis> zyga: you make my dreams become true :-)
[11:41] <dholbach> pandaadb, yep and downloading a zip sounds reasonable (https://github.com/ubuntu-core/snapcraft/blob/master/demos/tomcat-maven-webapp/snapcraft.yaml does it too)
[11:43] <pandaadb> ah tar-content can download anything
[11:43] <Son_Goku> zyga yo
[11:43] <pandaadb> snapcraft help tar-content does not recognize the plugin though for help (add authentication and such)
[11:45] <Son_Goku> zyga, is SELinux support for snaps coming soon?
[11:45] <Son_Goku> I'd rather not have to throw SELinux into permissive mode for this
[11:47] <zyga> Son_Goku: hi
[11:47] <zyga> Son_Goku: I'm not working on it yet but I can help someone that is interested and experienced in selinux
[11:48] <zyga> Son_Goku: the model supports it from day one
[11:48] <Son_Goku> I work in both the Fedora and Mageia communities, so I'm happy to help if you need anything
[11:48] <zyga> Son_Goku: that's great!
[11:49] <Son_Goku> and protip, Fedora COPR will soon offer Mageia as a release target
[11:49] <Son_Goku> Mageia 6 anyway
[11:49] <Son_Goku> since we're gradually moving onto the same tooling as Fedora for package management
[11:49] <zyga> Son_Goku: I think the first thing that should be doable is a way to run snapd in a mode where some interfaces are available and some are not
[11:49] <zyga> Son_Goku: and when an interface is not yet implemented for selinux, snaps using those have to be installed in devmode
[11:49] <zyga> Son_Goku: on fedora we could enable seccomp pretty easily I think
[11:49] <Son_Goku> yes
[11:49] <Son_Goku> that should cover most of it
[11:50] <zyga> Son_Goku: the first step towards that would be to make snap-confine allow seccomp while not yet using apparmor
[11:50] <zyga> Son_Goku: that should be pretty simple, it's roughly one or two lines and an optional compile on one file (have a look, it should be very fast to implement)
[11:50] <zyga> Son_Goku: for selinux itself I'd like to have something simple we could implement to prototype the idea
[11:50] <zyga> Son_Goku: I think the network interface (the thing that lets snaps talk to the network) is the first thing we could try
[11:51] <Son_Goku> unfortunately can't touch things requiring a CLA
[11:51] <Son_Goku> it gets too messy for me to contribute to stuff like that
[11:51] <Son_Goku> :(
[11:51] <Son_Goku> best I can do is help you along
[11:51] <Son_Goku> do you not already talk to NetworkManager?
[11:52] <Son_Goku> all variants of Fedora use NetworkManager as the default management interface
[11:52] <Son_Goku> well, except Cloud, which uses systemd-networkd
[11:53] <zyga> Son_Goku: as it is very well defined, a lot of the snaps need just that and we could try that
[11:53] <zyga> Son_Goku: why not? is your employer against that?
[11:53] <zyga> Son_Goku: it's not about network manager
[11:53] <zyga> Son_Goku: there are two interfaces: network, which lets you create AF_INET sockets and a few other things
[11:53] <zyga> Son_Goku: and network-manager, which lets you talk to n-m over dbus
[11:53] <zyga> Son_Goku: those are totally separate
[11:53] <zyga> Son_Goku: if you cannot work with the CLA in any way then I guess you'll have to wait until someone else steps up and can sign the CLA or that your situation changes
[11:53] <Son_Goku> it's not that I can't, but because the CLA involves copyright assignment, it has to be reviewed
[11:53] <Son_Goku> certain types of CLAs are easier to deal with than others
[11:54] <Son_Goku> and lawyers scare me :)
[11:55] <Son_Goku> in the meantime, it seems like it'd be a good idea to learn Go, though not really a fan of the language
[11:56] <zyga> Son_Goku: again, network and network-manager are totally different
[11:56] <zyga> Son_Goku: network lets you run a program like wget
[11:56] <zyga> Son_Goku: it lets wget use a few syscalls
[11:56] <zyga> Son_Goku: and perhaps read a few typical files (/etc/resolv.conf)
[11:56] <zyga> Son_Goku: are you familiar with the particular CLA used here? are you sure it's impossble to sign?
[11:56] <zyga> (for you)
[11:57] <Son_Goku> not sure actually
[11:57] <Son_Goku> but I was familiar with the ones used in older projects I tried to contribute to
[11:57] <Son_Goku> upstart, etc.
[12:01] <Son_Goku> why isn't snapcraft part of the snap project?
[12:03] <zyga> Son_Goku: the same codebase or the same group on github?
[12:04] <Son_Goku> snapcraft is in ubuntu-core rather than snap-core
[12:05] <Son_Goku> does snapcraft only work with ubuntu?
[12:05] <zyga> Son_Goku: it is a combination of reorgs to the code
[12:05] <ogra_> currently, yes
[12:05] <zyga> Son_Goku: currently snapcraft does currently only work on ubuntu but this is being changed
[12:05] <zyga> Son_Goku: it should be able to build snaps on any OS
[12:05] <ogra_> its just python ... might not be hard to port to other distros
[12:05] <zyga> Son_Goku: probably as a snap itself
[12:05] <Son_Goku> O.o
[12:06] <pandaadb> hey - i am trying to pull a jdk. I read this: If you only need to embed a Java runtime, add a part with the jdk type.
[12:06] <pandaadb> how does a part with a type look like?
[12:06] <Son_Goku> if it's a snap, that'd make it hard to consume things like rpms and debs, wouldn't it?
[12:06] <ogra_> why
[12:06] <pandaadb> It keeps telling me to use a plugin but i would like to only add the jdk
[12:06] <zyga> Son_Goku: not really, it would be easy to run it anywhere snapd runs
[12:06] <ogra_> as long as it knows where to get them and how to unpack them
[12:06] <zyga> pandaadb: I think the word "type" is really "plugin" today
[12:07] <pandaadb> oh okay. So that one tells me that source is mandatory
[12:07] <Son_Goku> oh geez
[12:08] <Son_Goku> it needs arch translations
[12:08] <qengho> Son_Goku: Snapcraft is one of many possible tools to make snap packages. For a while, snap packages were made with "cp" and "vi".
[12:08] <Son_Goku> ew
[12:08] <Son_Goku> vi!?
[12:08] <qengho> Yes. UCB. not vim.
[12:08] <zyga> Son_Goku: snaps are just squashfs filesystems with meta/snap.yaml file
[12:08] <zyga> Son_Goku: they can be made in any way you want
[12:09] <Son_Goku> that's more gross than vim
[12:10] <qengho> Okay.
[12:11] <Son_Goku> but wow
[12:11] <Son_Goku> so it's a loop with stuff inside plus a declaration file
[12:11] <qengho> Son_Goku: Anyway, you asked why. Snapcraft came after snap, as an idea to help snaps, not as The Only Ordained Way To Make Snaps Forevermore.
[12:11] <zyga> yep
[12:12] <Son_Goku> I don't see debs as a plugin in snapcraft
[12:12] <Son_Goku> so how does it consume debian packages/repos?
[12:12] <qengho> Son_Goku: Anypart can include debs.
[12:12] <ogra_> it pullse the binaries from the ubuntu archive
[12:12] <ogra_> *pulls
[12:12] <ogra_> and unpacks them so you get your depending libs and all
[12:12] <qengho> Son_Goku: "stage-packages: [...]"
[12:13] <Son_Goku> oh, so it's integral to it rather than being a component of it
[12:13] <ogra_> right
[12:13] <ogra_> it could use rpms
[12:13] <ogra_> or fooples ... or shrobs
[12:13] <ogra_> :)
[12:13] <ogra_> whatever helps you to fulfill your requirements to run your snap
[12:14] <ogra_> (even a tarball full of binary blobs you pre-built would work)
[12:16] <qengho> ogra_: package names will not match, so it will matter what kind of system you're building on as to whether a snapcraft.yaml "stage-packages" will work. I think it's safer+better to say "this always gets debian packages".
[12:16] <ogra_> sure ... but nothing stops you to do non-standard hackery
[12:19] <pandaadb> hm. when using the jdk plugin, i need to define a source (i think it is ignored). But when doing snapcraft snap, it doesn't build my snap anymore :/
[12:21] <ogra_> pandaadb, did you run snapcraft clean first ?
[12:21] <pandaadb> no, let me try that
[12:22] <pandaadb> it seems to be updating my repositories and then in the end tells me my security is a "danglink link" i think
[12:23] <ogra_> ah, you need to make sure to not have links that point to somewhere outside the snap
[12:24] <pandaadb> ah that's maybe because I had to add security certificates to my local java
[12:24] <pandaadb> and they are not really needed for the snap i am building, but rather so i can talk to our shitty maven repos
[12:24]  * pandaadb tries to remove link
[12:24] <pandaadb> Or is there maybe a way to have the jdk part be completely independent?
[12:26] <qengho> pandaadb: No. If you need it, you must pick it and ship it in the snap.
[12:26] <pandaadb> oh by that i meant that it should just download everything and not try to link to something local
[12:26] <pandaadb> I think maybe the issue is that I am using the oracle jdk for development, but the snapcraft is downloading the openjdk of a different version
[12:27] <pandaadb> the simlink doesn't even exist (the one it is looking at)
[12:27] <pandaadb> i guess that's what dangling means
[12:29] <pandaadb> seems to be a known issue: https://bugs.launchpad.net/snapcraft/+bug/1500505
[12:31] <Son_Goku> ogra_ actually, I'd suggest that it should be able to handle either debian or rpm packages
[12:32] <ogra_> Son_Goku, well, as qengho said above, then your snapcraft.yaml cant be universall
[12:32] <ogra_> since the names for stage packages will differ
[12:32] <Son_Goku> the output is universal, though
[12:33] <ogra_> well, the idea is also that you can just grab an upstream snapcraft.yaml and it will just build
[12:34] <Son_Goku> so declaring a "from <distro>" is hard?
[12:34] <ogra_> so while other package managers will be possible to hack in, i guess snapcraft as a snap (which would then just use debs) will likely become a default
[12:34] <Son_Goku> :/
[12:34] <ogra_> butu why would you care at all
[12:35] <ogra_> you do snap install snapcraft ... feed it your snapcraft.yaml and out comes a snap
[12:35] <ogra_> what you care for is your source and how to get it to users and running, no ?
[12:35] <pandaadb> Okay - so my snap did not package, because jdk needs a source. But since I didn't get why, i added the string "some source". This is obviously not a location, which is why my snap broke. I set it to "." and now it packages
[12:36] <ogra_> :)
[12:37] <qengho> pandaadb: Are you getting source from somewhere and compiling it, or wrapping up some existing debianubuntu package in a snap?
[12:37] <ogra_> Son_Goku, the execution environment should nnot matter at all in the end
[12:38] <pandaadb> qengho, i am trying to package up my java app (build with gradle) and make it run
[12:38] <pandaadb> the next step will be to write a gradle plugin as I am not using maven
[12:38] <pandaadb> and then i will attempt to build it from source
[12:38] <Son_Goku> I care about the source because it can matter
[12:38] <qengho> Ah, then you can put it next to snapcraft.yaml and say "source: pandaadbdir"
[12:39] <pandaadb> Is te root directory $SNAP or is it @SNAP_DATA ?
[12:39] <pandaadb> oh okay - that is what the source is for
[12:41] <pandaadb> found it, it's SNAP
[12:41] <qengho> pandaadb: SNAP is snap/.   SNAP_DATA is a /var/ something. SNAP_USER_DATA is a /home/~user/ something.
[12:41] <willcooke> I need to provide my own .pro file to build this thing (the one that comes with it is "broken" - I will look at fixing it later).  I had added it in to my git repo in parts/<project>/src/  - but then when I tested it from scratch, of course git wont clone in to a non-empty dir.  So is a suitable hack to have another step in my yaml to copy the file over after the checkout has happened?
[12:41] <pandaadb> perfect :) thanks a lot
[12:41] <qengho> pandaadb: install snap "hello-world" and run hello-world.sh .
[12:41] <willcooke> s/checkout/clone
[12:42] <pandaadb> thanks!
[12:42] <ogra_> Son_Goku, so use source for everything (you can do that) and no binary packages at all
[12:43] <pandaadb> this is awesome. Remind me of docker. But with docker if feel so restricted to the container I built. If I made a mistake or i want to change something inside my container, i am kind of screwed
[12:43] <Son_Goku> but that pulls in ubuntu sources, right?
[12:43] <Son_Goku> I can't use srpms or something else
[12:43] <ogra_> it is just quite some effort and will take extra build time ... but technically nothing stops you from building *all* the bits from source
[12:43] <ogra_> it pulls the sources you point to
[12:43] <ogra_> (it will use ubuntus GCC ... but thats it)
[12:44] <ogra_> i'm talking about upstream tarballs (you can just point to an url) or git trees
[12:45] <ogra_> nothing requires that you actually use stage-packages at all
[12:47] <pandaadb> can snappy packages be run with sudo? i think my server can not start because it does not have permissions
[12:49] <ogra_> if it is a server it already runs as root
[12:49] <ogra_> did you define a daemon line in your snapcraft.yaml ?
[12:49] <pandaadb> oh okay, that may be the certificate dangling stuff then
[12:49] <ogra_> https://github.com/ubuntu/snappy-playpen/blob/master/tinyproxy/snapcraft.yaml
[12:49] <pandaadb> ogra_, no - gradle creates a wrapper that uses java_home and just runs it with the classpath env
[12:49] <ogra_> see how i did it for tinyproxy there
[12:50] <ogra_> ( you need "daemon: simple" in the "apps:" part)
[12:51] <pandaadb> what does the plugs do?
[12:51] <qengho> willcooke: Hmm, you could abstract it a bit. Make a ./Makefile next to snapcraft.yaml , and massage it together in your build-step? pull, pull, cp, and build in the makefile.  So, plugin:make and source:. ?
[12:51] <mhall119> d_ed: are your KDE patches in upstream, or are they only in an Ubuntu or Neon archive?
[12:51] <qengho> willcooke: that^ will not work in out build servers, though.
[12:52] <qengho> only pull stage has access to network.
[12:52] <willcooke> qengho, ah, good point.
[12:52] <willcooke> Can the copy plugin help me I wonder.
[12:52]  * willcooke reads
[12:52] <willcooke> kyrofa, sucessfully built using your new qmake plugin, thank you!!
[12:53] <kyrofa> willcooke, excellent, thank you!
[12:53] <kyrofa> willcooke, it'll probably go through some more renditions, but now I know those variables are the ones you need
[12:53] <kyrofa> willcooke, so you should be good once it lands
[12:53] <willcooke> cool!  I will comment on the PR
[12:54] <kyrofa> I'd appreciate it
[12:54] <mhall119> sergiusens: are you in today?
[12:56] <pandaadb> ogra_, after adding those lines my snap became not startable (e.g. after installing it I can't just type in server.run)
[12:56] <pandaadb> http://pastebin.com/E1GS4Gaj
[12:57] <willcooke> qengho, I could just write a plugin to mangle my source I think
[12:57] <qengho> willcooke: Yes. Ew. :(
[12:58] <willcooke> \o/
[12:59] <willcooke> snapcraft.common.link_or_copy might help me
[13:00] <seb128> kyrofa, sergiusens, is there a snapcraft way/plugin to move files around in the snap before it's packed?
[13:01] <kyrofa> seb128, you can use reorganize
[13:01] <kyrofa> seb128, errr, organize
[13:02] <qengho> willcooke: I'd do some terrible relative thing. ../../otherpart/build/
[13:02] <seb128> kyrofa, thanks
[13:03] <willcooke> qengho, I think it knows where everything will be, so an absolute path should be do-able, and then I can just symlink it
[13:03] <willcooke> oh, seb128 - in this Qt project I'm building I'm seeing errors about pixbuf stuff, like we saw for Gtk.  I'll  hit you up for some hints in a bit if you're free?
[13:04] <seb128> willcooke, sure
[13:04] <seb128> willcooke, I'm iterating over my evince snap
[13:04] <seb128> getting there, good stuff
[13:04] <willcooke> seb128, \o/
[13:05] <seb128> I've a git version starting on xenial and working (can open pdf) including translations (but done in an hacky way)
[13:08] <ogra_> pandaadb, it should just auto-start ... check with journalctl and systemctl
[13:08] <pandaadb> is that what the daemon is for?
[13:08] <ogra_> yeah
[13:08] <ogra_> it makes snapcraft create a systemd unit
[13:08] <pandaadb> and the service name is that smae?
[13:09] <pandaadb> so in my case: sudo service media-server.run start ?
[13:09] <ogra_> snap.tinyproxy.tinyproxy.service
[13:09] <ogra_> thats what i get for tinyproxy
[13:09] <pandaadb> ah i will give it another try
[13:10] <ogra_> systemctl status snap.tinyproxy.tinyproxy.service
[13:10] <ogra_> that gets me info if it runs
[13:10] <seb128> jdstrand, you set bug #1576308 as fix commited but it still doesn't work out of the box due to missing xdg_runtime_dir, do you want to re-use that bug or should we open a new one?
[13:10] <ogra_> (and replacing status with stop or start will then start/stop it)
[13:11] <didrocks> seb128: missing, as, the env isn't exported?
[13:11] <didrocks> (or access)
[13:11] <seb128> didrocks, like the /run dir is not mounted in the snap env
[13:11] <seb128> I guess we could create a new one and set the variable
[13:12] <seb128> unsure if that wouldn't confuse dconf though
[13:12] <pandaadb> ooi - is there a plan to just move away from apt-get to snap completely?
[13:12] <seb128> since the service is the user session one
[13:12] <didrocks> seb128: just for my interest, what is the .pid or .lock that is used?
[13:12]  * didrocks doesn't see anything obvious
[13:13] <seb128> didrocks, in that dir?
[13:13] <didrocks> yep
[13:13] <seb128> iirc desrt said that there was a file writing in there during writes
[13:14] <didrocks> ah, so it can be transient
[13:14] <seb128> which client apps use to know when to read the new value or something
[13:14] <seb128> it's transient
[13:14] <seb128> it's just there during writes
[13:14] <didrocks> yeah, so maybe with separated one, we would have multiple writes…
[13:22] <morphis> mvo_, niemeyer: is there somebody else who can finish reviewing https://github.com/snapcore/snapd/pull/1226 and merge it so we get it released soon?
[13:23] <seb128> slangasek, jdstrand, mvo_, the "socketall/i386" fix|workaround from snapd 2.0.8 isn't right, http://launchpadlibrarian.net/265014833/snapd_2.0.5_2.0.8.diff.gz suggests it's only allowed if network-bind is used, shouldn't be allowed in any case?
[13:25] <matteo> snap-confine is responsible of setting some env vars, like ld library path ot the dynamic loadeer?
[13:27] <morphis> matteo: what do you mean by dynamic loader?
[13:27] <matteo>  /snap/ubuntu-core/current/lib/ld-linux.so.2
[13:28] <pandaadb> mmm snappy does not seem to have permissions to start jetty on part 8085
[13:28] <pandaadb> (and 8081)
[13:30] <morphis> matteo: ah
[13:30] <morphis> matteo: it should or some of the generated scripts
[13:30] <matteo> like /snap/bin/htop
[13:31] <matteo> that's the htop generated script http://pastebin.ubuntu.com/17431353/
[13:32] <matteo> http://pastebin.ubuntu.com/17431370/
[13:32] <matteo> the latter also has the wrapper
[13:33] <pandaadb> I think it might be openjdk being packaged that is not allowed to access any ports?
[13:34] <jbicha> my CPU was running at 100% yesterday
[13:35] <jbicha> I checked my processes and saw that it was java
[13:35] <jbicha> I killed java and it just came back to life
[13:35] <jbicha> and then I realized it was because I had installed the cassandra snap
[13:36] <jbicha> so I removed that because I didn't need it anyway, not sure if that's expected behavior for it or not
[13:37] <jbicha> (cassandra was a featured app briefly in a dev snapshot of Ubuntu's GNOME Software)
[13:38] <jbicha> reported it here because I don't know where to report issues with snaps
[13:39] <seb128> to the packager usually I think
[13:40] <seb128> ev in that case I think?
[13:40] <jbicha> ok I see snap find tells me that
[13:40] <jbicha> I hadn't used the cli, just GNOME Software which doesn't give much info at all
[13:43] <ogra_> olli|, poke .... about the bug reporting link in the topic
[13:44] <matteo> 2.0.9 is the last tag on github?
[13:51] <pandaadb> okay it's really odd, but my java app will not start up. It tells me i have no privileges for the ports it wants to start on
[13:51] <pandaadb> i can use the jvm in /snap and start it manually
[13:51] <pandaadb> i can use the shell scripts that start it manually
[13:51] <pandaadb> that all works, but running it as a service does not
[13:51] <didrocks> pandaadb: did yu install your snap in --devmode?
[13:51] <didrocks> you*
[13:51] <pandaadb> yes
[13:51] <pandaadb> is that bad? :D
[13:52] <didrocks> no, that was a potential issue you may have (like permission issues)
[13:52] <didrocks> something you can try:
[13:52] <pandaadb> so i should move it to strict?
[13:52] <didrocks> no no, you should always start in devmode
[13:52] <didrocks> ah, you declared it that way
[13:52] <didrocks> but when you installed your snap
[13:53] <didrocks> you did run: snap install <snap_name> --devmode
[13:53] <didrocks> right?
[13:53] <pandaadb> no
[13:53] <didrocks> here you go :)
[13:53] <pandaadb> just sudo snap install <name>
[13:53] <didrocks> reinstall it in devmode
[13:54] <pandaadb> you are my hero!
[13:54] <pandaadb> :) :)
[13:54] <pandaadb> thanks!
[13:54] <didrocks> (the declaration in snapcraft.yaml is to enforce people to type the --devmode option in the future once snapd enforces it)
[13:54] <didrocks> yw! :)
[13:54] <didrocks> pandaadb: once you are happy with your snap, you can turn it into strict mode
[13:54] <didrocks> and add confinement
[13:54] <didrocks> http://snapcraft.io/create/
[13:54] <didrocks> you have here a service example
[13:55] <didrocks> you can read "confinement and devmode
[13:55] <didrocks> and "plugs-and-slots: integration with the system and other snaps"
[13:55] <didrocks> which is exactly about web servers, as it seems to be your use case :)
[13:55] <pandaadb> yep :)
[13:56] <pandaadb> yeah, i have to admit, i read about snappy and got so excited that i just started trial-and-error runs while reading at the same time
[13:56] <ogra_> pandaadb, but if you need network, look at my tinyproxy snapcraft.yaml from above
[13:56] <ogra_> just add network and netwro-bind to the plugs line for your daemon
[13:56] <didrocks> ogra_: better to direct people to the documentation, I did hilight the needed section :)
[13:57] <ogra_> didrocks, i dont even know where the documentation lives ... i work by example :)
[13:57] <didrocks> ogra_: you should at least know where it lives to point your community to it :p
[13:57] <ogra_> pandaadb, follow the documentation that didrocks will point you to in a minute ;)
[13:57] <didrocks> ogra_: s/will/did/
[13:57] <pandaadb> ah he did above :)
[13:57] <pandaadb> thanks
[13:57] <didrocks> see above ;)
[13:57] <didrocks> yw!
[13:58] <pandaadb> yes - i am reading about it now. hehe - my next question would have been "it started but i can't curl it" but now I see :)
[13:58] <ogra_> oh, "create" lists the possible plugs ?
[13:59] <didrocks> ogra_: no, just this particular case (webserver)
[13:59] <ogra_> ah
[13:59] <didrocks> let me find the page about plugs and slots
[14:00] <didrocks> https://developer.ubuntu.com/en/snappy/guides/interfaces/
[14:03] <pandaadb> yey :) It runs!
[14:03] <didrocks> confined? excellent :)
[14:04] <pandaadb> still in dev mode for now
[14:05] <ev> jbicha: can you send me (ev@ubuntu.com) the /var/log/syslog file from that machine?
[14:06] <pandaadb> Only learned about snappy today :) I just figured it would be cool to package my application like that
[14:06] <didrocks> yeah, it is! :)
[14:06] <pandaadb> So is it a usecase to have a private snappy repo, so that one can distribute to servers like that
[14:06] <pandaadb> And then handle updating and all with it
[14:06] <pandaadb> it's the awesome version of docker :)
[14:07] <didrocks> pandaadb: you can control channels and also (in the near future), the way that updates will roll to your users from the main store
[14:07] <didrocks> and even have snaps that are private to you or your friends (in devmode IIRC)
[14:08] <pandaadb> ah perfect. Yeah i was missing a couple of things that i could not work out before
[14:09] <pandaadb> e.g. i could not work out how to add authentication to tar-content, so that i could download a zip from my build server
[14:10] <pandaadb> though it seems super easy to write custom plugins or extend some. Or frankly, just use snappy as a build server instead since it builds things automatically
[14:10] <joc_> kyrofa: hi, i'm making slow but steady progress though my snapping project using your plugin, still don't think i've encountered anything missing from the plugin that is blocking me
[14:10] <kyrofa> joc_, great thanks for letting me know!
[14:10] <joc_> kyrofa: my options sections are getting quite big though!
[14:11] <kyrofa> joc_, just because of the project, or are there things you think the plugin should be handling?
[14:12] <didrocks> pandaadb: yeah, you can inherit and write your own public for those use cases
[14:12] <kyrofa> didrocks, you're building snaps in the playpen? Are you just making an lxc on travis and building there?
[14:12] <joc_> kyrofa: this is the yaml https://github.com/jocave/telegram-app-snap/blob/master/snapcraft.yaml
[14:13] <joc_> kyrofa: there is one arch specific lib path in there that i haven't managed to modify in the build
[14:13] <kyrofa> joc_, the L$SNAPCRAFT_STAGE/usr/lib/x86_64-linux-gnu ?
[14:13] <joc_> yep
[14:14] <kyrofa> joc_, you actually shouldn't need that anymore as of yesterday. Can you try removing it and see what happens?
[14:14] <kyrofa> joc_, assuming you're running a current version of my branch anyway
[14:15] <joc_> kyrofa: sure, ill make sure i'm up to date and try it
[14:17] <didrocks> kyrofa: unfortunately, as I have to use docker to ship latest snapcraft (remember that their builders is 14.04 LTS at best), I can't run lxd inside docker
[14:17] <didrocks> kyrofa: that's what I tried today :)
[14:17] <didrocks> (well, this last 30 minutes :p)
[14:17] <didrocks> that would help to do a cleanbuild though
[14:17] <pandaadb> so for my snap, this obviously has to download tje jdk as a dependency, which makes my snap a bit big. Does snappy know about those dependencies (e.g. if i package a second server and install it, will it duplicate the jre?)
[14:18] <kyrofa> didrocks, right, which is why I assumed you were using lxc or something
[14:18] <didrocks> kyrofa: I've not looked at nested lxc
[14:18] <didrocks> (yet)
[14:18] <didrocks> but plan to as option #1 failed
[14:18] <kyrofa> didrocks, talk to elopio_, he's done it
[14:18] <didrocks> and sharing images as well?
[14:18] <didrocks> (would be great to not have to install snapcraft each time)
[14:19] <kyrofa> didrocks, no, I think he spun one up each time
[14:19] <didrocks> would be interesting to ensure we can distribute images
[14:19] <didrocks> even better for people to reproduce any issue
[14:19] <didrocks> let's see, I'll devote some time in looking at this
[14:19] <kyrofa> didrocks, you could also use the launchpadlib from 14.04 to spin up builds in LP
[14:20] <willcooke> seb128, here's what I'm seeing:  http://paste.ubuntu.com/17432569/
[14:20] <kyrofa> didrocks, anyway, this is something that I want as well, so let me know if you need a hand
[14:20] <kyrofa> didrocks, then I'll steal it from you
[14:20] <willcooke> it's a Qt project though, so I dont understand why that is happening.  Pehaps it's normal
[14:20] <didrocks> kyrofa: yeah, we need though to think about credentials :)
[14:21] <seb128> willcooke, let me copy that in a /msg
[14:21] <elopio_> didrocks: we abbandoned travis for more complex thing, because the docker nightmare in there was ugly. Do you want to use our jenkins?
[14:21] <didrocks> kyrofa: same, on my list to see how to have Travis CI handling that correctly, I have used the LP api a lot as you can infer over years ;)
[14:21] <kyrofa> didrocks, for LP? True. I figured we'd create a custom LP user, generate a token, and encrypt it in the .travis.yml
[14:21] <didrocks> elopio_: we need to have the results publically available, is that possible?
[14:21] <kyrofa> Yes I can imagine!
[14:21] <didrocks> elopio: a lot of people in the community as access to it :)
[14:22] <elopio> didrocks: we are moving to jenkaas, which will be public as I understand.
[14:22] <elopio> we can start getting ready the jobs for when the last server details are ready.
[14:22] <elopio> fgimenez: you said jenkaas will be public, right?
[14:22] <didrocks> elopio: would be happy to be on board thus! :)
[14:24] <jbicha> ev: https://paste.fedoraproject.org/380584/
[14:25] <fgimenez> elopio, yes, afaik it's already accessible https://jenkins.canonical.com/ubuntu-core/
[14:25] <joc_> kyrofa: yep you were correct, i don't appear to need that line now
[14:25] <kyrofa> joc_, awesome :)
[14:25] <kyrofa> Thank willcooke
[14:25] <joc_> thaks willcooke
[14:26] <joc_> or thanks
[14:26] <elopio> fgimenez: you also mentioned a way to send back the results to github with the plugin, right? Or I am imagining this?
[14:27] <willcooke> :)
[14:28] <niemeyer> morphis: Yeah, these interfaces are sitting there for too long
[14:28] <morphis> niemeyeryes
[14:29] <morphis> niemeyer: you want to have a look or how are we getting those further?
[14:32] <fgimenez> elopio, we can customize the commit status url and point it to $JOB_NAME/$BUILD_NUMBER/testResults, not sure if we can actually send the results to gh
[14:34] <fgimenez> elopio, we can also show a line in the status with a summary of the results, iirc we had this enabled at some point..
[14:34] <niemeyer> morphis: I'll have a look to see what the next steps should be
[14:35] <elopio> fgimenez: ah, yes, I was imagining things.
[14:36] <morphis> niemeyer: awesome!
[14:37] <niemeyer> morphis: Sorry for the delay on this one.. we must not take so long to get interfaces in
[14:38] <morphis> niemeyer: yes, that would be great
[14:43] <willcooke> dpm, I have a Qt project which also uses gdk pixbuf.  It should be safe to add some pixbuf stuff to the wiki qt5 launch script I think.  Can you point me to where it lives to I can try some local changes first?
[14:45] <dpm> willcooke, actually... there is a branch of qt5conf for those cases, it's the 'qt5conf-with-gtk' launcher as a wiki part, and its code lives here: https://github.com/dplanella/qt5conf/blob/with-gtk/qt5-launch
[14:45] <willcooke> dpm, ah! Awesome! Thanks
[14:46] <dpm> willcooke, it doesn't have the gdk pixbuf bits yet, but I think it's just what you need :)
[14:46] <ev> jbicha: can you snap install cassandra, wait a couple of minutes, then pastebin `journalctl -b`? I think there will be more interesting output there.
[14:46] <willcooke> cool, I can add them, thanks dpm
[14:48] <ev> and anything else you have in logs that points at Cassandra :)
[14:49] <willcooke> seb128, do you know if your gtk launcher script became a wiki part already?
[14:49] <jbicha> ev: do I need to use --devmode?
[14:49] <seb128> willcooke, dpm made one
[14:49] <willcooke> perfect, thanks seb128 dpm
[14:49] <seb128> willcooke, https://wiki.ubuntu.com/Snappy/Parts
[14:49] <seb128> gtkconf
[14:49] <willcooke> aha!
[14:50] <aatchison> Good morning
[14:50] <dpm> willcooke, note the part in the wiki points to the 'devel' branch in github, that's the right one to look at for the launcher
[14:52] <willcooke> has anyone written a script to parse the depends for a deb and convert them in to yaml for copy&paste in to a snapcraft.yaml yet?
[14:52] <kgunn> jdstrand: not sure if you have time, but mir interface PR is really cleaned up
[14:52] <kgunn> not sure if you wanna look one more time
[14:53] <aatchison> I've got my snap building again (I pushed a dependency to pypi.python.org, so no more pip flags are required,) but now I have this issue. http://paste.ubuntu.com/17433513/ Should I be setting some sort of data directory?
[14:54] <aatchison> It looks like it's still trying to run site packages from my build directory
[14:56] <kyrofa> aatchison, yeah it looks like the build process is writing the builddir somewhere, is that possible?
[14:57] <kyrofa> aatchison, as some sort of search path, maybe
[14:59] <aatchison> hmm
[14:59] <aatchison> I'll keep fiddling. Here is my project if anyone would like to take a look: https://github.com/MycroftAI/snapcraft-mycroft-core
[15:03] <jbicha> ev: https://paste.fedoraproject.org/380611/
[15:08] <seb128> it's a bit unclear to me how the apps: section of the snapcraft.yaml works
[15:08] <seb128> if I package calc, can I get a "calc: calc" command?
[15:08] <ChrisWarrick> Does sna[Cp support Fedora 23?
[15:09] <seb128> or does it need to be snapname.calc: ?
[15:09] <seb128> didrocks, ^ do you know?
[15:14] <mhall119> sergiusens: ping
[15:15] <kyrofa> seb128, not sure what the confusion is
[15:15] <kyrofa> seb128, are you asking about the YAML, or about how it's presented to the user after the snap is installed?
[15:15] <seb128> kyrofa, both,sometime it seems renamed in /snap/bin and sometimes not
[15:16] <Chipaca> seb128, if the app is named like the snap, you get to have the barename
[15:16] <seb128> kyrofa, also I created a .desktop with Exec=/snap/bin/cmd
[15:16] <Chipaca> seb128, that is, snap foo have two apps: foo and bar. So you get /snap/bin/foo and /snap/bin/foo.bar
[15:16] <seb128> but the Exec command is missing in the /var/lib/snapd/applications version
[15:16] <kyrofa> seb128, so yeah, in /snap/bin it's typically <snapname>.<appname> unless snapname == appname
[15:16] <seb128> Chipaca, ah, thanks
[15:17] <seb128> Chipaca, kyrofa, do you know any reason why snap would remove the Exec? it's there in the prime dir
[15:17] <kyrofa> seb128, from the desktop file?
[15:17] <Chipaca> ChrisWarrick, I think so? in fact i think in 23 you don't need to turn off selinux (as AIUI the thing in 24 that breaks snapd is not there in 23)
[15:17] <Chipaca> ChrisWarrick, but I could be wrong! zyga knows more, but he's EOW'ed
[15:17] <didrocks> seb128: this is the /create page btw :)
[15:18] <didrocks> but yeah, basically if app name == snap name, it's stripped
[15:18] <ChrisWarrick> Chipaca: I like not having selinux on
[15:18] <seb128> didrocks, thanks
[15:18] <didrocks> otherwise, it's always snap_name.app_name
[15:18] <Chipaca> ChrisWarrick, tut tut :-)
[15:18] <Chipaca> ChrisWarrick, then it should work fine; give it a spin!
[15:18] <seb128> kyrofa, http://paste.ubuntu.com/17434418/
[15:19] <Chipaca> seb128, read the docs?
[15:19] <Chipaca> seb128, https://github.com/snapcore/snapd/blob/master/docs/meta.md#desktop-files
[15:19] <seb128> Chipaca, which ones? http://snapcraft.io/create/ has no mention of it
[15:20] <seb128> Chipaca, that goes back to my previous question, I'm in the case where cmd=snapname
[15:20] <seb128> so I don't have a snap.cmd
[15:20] <seb128> so I can't have a .desktop?
[15:21] <Chipaca> ah, that might need clarifying
[15:21] <Chipaca> seb128, Exec=<the name of the thing in /snap/bin>
[15:22] <seb128> oh, ok
[15:22] <Chipaca> which is, granted, problematic and needs revisiting
[15:22] <seb128> why is the full path invalid?
[15:22] <Chipaca> seb128, that's even more problematic
[15:22] <Chipaca> seb128, what's the full path?
[15:23] <seb128> Chipaca, /snap/bin/evince
[15:23] <seb128> which is what I used
[15:24] <Chipaca> seb128, there could be situations where the binary isn't there
[15:24] <seb128> Chipaca, which is why we have TryExec
[15:24] <Chipaca> bah. THe case for it not being in bin is a bad one, but it could happen
[15:25] <Chipaca> more possible is that the snap is installed in somewhere other than /snap/ but we'd still put the executable it in /snap/bin
[15:25] <Chipaca> seb128, seb128 tryexec is not supported and will be removed, as it says in the docs
[15:25] <seb128> Chipaca, that doesn't make sense to me, but that's an argument for another day
[15:26] <seb128> Chipaca, I don't want to maintain a fork of the .desktop, I just want to use the upstream one with the Exec seded
[15:26] <Chipaca> seb128, and not an argument to be had with me, and not for IRC
[15:26] <seb128> Chipaca, anyway, trying now with "evince" instead of "/snap/bin/evince", thanks
[15:27] <Chipaca> seb128, at some point that'd have to change, but we'll let people know somehow
[15:27] <seb128> k
[15:27] <Chipaca> otherwise you risk it breaking
[15:27] <Chipaca> that is
[15:27] <Chipaca> snap names could change
[15:27] <seb128> you mean the mountpoints?
[15:27] <Chipaca> so if for legal reasons we suddenly have to rename evince to potato or whatever, suddenly the cmd is no longer "evince" but potato.evince
[15:28] <Chipaca> but that work is way in the future still
[15:28] <Chipaca> (and i doubt it'd be a problem for evince in particular!)
[15:28] <seb128> yeah
[15:28] <seb128> but that .desktop is generated at install time
[15:28] <Chipaca> yes
[15:28] <seb128> so in practice it's easy to ensure the Exec is kept in sync
[15:28] <seb128> but let's discuss that on the list another day
[15:29] <Chipaca> +1
[15:29] <Chipaca> especially not this close to eow, and especially not this week
[15:29]  * Chipaca is exhausted
[15:30] <seb128> Chipaca, that works, thanks
[15:31] <seb128> snap replaced evince by /snap/bin/evince for me
[15:31] <seb128> which is a bit ironic :p
[15:31] <seb128> when I did that myself it removed the key
[15:31] <seb128> also something should probably display a warning in that case
[15:31] <Chipaca> seb128, snap is unionized
[15:31] <Chipaca> seb128, you tried to do its job!
[15:31] <seb128> like "exec cmd invalid and removed"
[15:31] <seb128> do you know what component I should open that bug against?
[15:32] <seb128> snapcraft? snappy?
[15:32] <Chipaca> that's snapd itself
[15:32] <seb128> snapcraft could warn about the invalid syntax
[15:32] <Chipaca> certainly
[15:32] <Chipaca> in fact snapcraft could help a lot with writing the .desktop
[15:32] <Chipaca> (i thought it did)
[15:32] <seb128> that's the discussion to have on the list :p
[15:33] <seb128> imho it should automatically use upstream ones when available
[15:33] <seb128> seding the Exec and Icon if needed
[15:40] <pandaadb> Hi - Am I right that snaps are not supposed to share any resources? E.g. with lots of products you'll need things like java installed.
[15:40] <pandaadb> Would you just package a new java lib into each snap?
[15:40] <pandaadb> Or would one rather have a java snap which uses slots (I think that's right) to expose a java interface for others to use?
[15:41] <pandaadb> Or is there a plan to have very common libraries integrated in the framework? Like python and such?
[15:47] <willcooke> seb128, dpm - that pixbuf stuff has stopped the errors
[15:47] <willcooke> thanks!
[15:47] <seb128> great
[15:48] <seb128> yw!
[15:59] <willcooke> dpm, just created a PR - but lemme test one more time...
[15:59] <ev> jbicha: sorry for the delayed reply. The problem, I think, is that you don’t have the mount-observe interface connected, e.g.
[15:59] <ev> snap connect cassandra:mount-observe ubuntu-core:mount-observe
[16:00] <ev> but really the problem is that we put Cassandra in the GUI where it wouldn’t be obvious that you need to manually connect up that interface
[16:00] <dpm> willcooke, awesome. I'm heads down with an e-mail, but I'll merge your PR in a bit, thanks!
[16:00] <ev> apologies there to willcooke, seb128, and attente
[16:00] <willcooke> dpm, no hurry
[16:01] <willcooke> ev, we didn't land that bit yet, so I think we're ok :)
[16:01] <seb128> I think jbicha did beta test the candidate version
[16:01] <willcooke> ahh
[16:01] <ev> jbicha: if you’re curious, mount-observe needs to be manually connected in a confined snap because we want you to explicitly acknowledge letting the snap see your mountpoints
[16:03] <ev> also, I believe snaps are going to grow hooks that fire once an interface is connected. This would let us sleep cassandra until that interface connection dependency was satisfied
[16:39] <gouchi_> hi
[16:39] <gouchi_> is it necessary to provide drirc ?
[16:45] <ev> sergiusens, elopio: looks like we’re good to land https://github.com/ubuntu-core/snapcraft/pull/578 ?
[16:45] <elopio> ev: done.
[16:47] <ev> star, thank you!
[16:52] <elopio> thanks to you.
[16:55] <kyrofa> elopio, are we running any of snapcraft CI on other archs yet?
[16:56] <elopio> kyrofa: I can trigger them. They are not run automatically yet.
[16:56] <elopio> kyrofa: want me to check something?
[16:56] <kyrofa> elopio, no, but this ldd crawling thing is very architecture-dependent... I'm nervous playing with it
[16:58] <elopio> kyrofa: you can trigger a run yourself: http://jenkins.elopio.net:8080/job/github-snapcraft-autopkgtest-cloud/build?delay=0sec
[16:58] <kyrofa> elopio, and they actually pass?
[16:59] <elopio> kyrofa: I'm having one example failing in i386. I haven't seen the rest yet.
[16:59] <elopio> they should pass, mostly :)
[17:00] <elopio> kyrofa: use bos01 as the region, and the available architectures are ppc64el, arm64, amd64 and i386
[17:00] <kyrofa> elopio, alright, thanks :)
[17:01] <elopio> kyrofa: I can also give you access to those slaves, so you can start a machine and ssh into it.
[17:02] <kyrofa> elopio, ah, I may take you up on that once I have a good test case
[17:02] <kyrofa> Messing with this makes me miss C++
[18:04] <g_> hello
[18:07] <elopio> kyrofa: what about getting crazy today and skipping the stand up?
[18:07] <kyrofa> elopio, haha, sure
[18:08] <g_> hey guys
[18:09] <g_> i have a question about using snappy to run services
[18:09] <kyrofa> g_, hey there! Sure, what's up?
[18:12] <g_> so i currently have a suite of programs that i build a single deb to install
[18:12] <niemeyer> jdstrand: Spread rev 6 up for review, for when you have a spare moment
[18:13] <g_> they are made for ubuntu 12.04 and i made upstart scripts for each of them
[18:13] <niemeyer> jdstrand: Any idea of when we'll get home auto-approved?
[18:14] <g_> i saw that snappy has its own daemon starting system
[18:14] <g_> how does that work?
[18:14] <g_> what sort of flexibility does it have for starting after dependent services
[18:15] <g_> it seems pretty simplified from the documentation ive seen at snapcraft
[18:16] <g_> ideally i could build a snap which the user could configure which services to start since one of them would want to be disabled most of the time
[18:17] <g_> also work across different distros
[18:19] <swartzr> Are there any permission sets for snaps that allow accessing mounted devices?
[18:19] <Chipaca> g_, that sounds tricky to do
[18:19] <Chipaca> g_, as you say, it's pretty simplified
[18:20] <Chipaca> swartzr, I *think* that's still TBD but should be coming in the next week or thereabouts (but I could've misunderstood what zyga was going to work on next, as i missed the standup today)
[18:22] <Chipaca> swartzr, there are two separate things, one about giving a snap a directory, and another about giving a snap a device
[18:22] <Chipaca> swartzr, I don't think I've seen something about giving a snap a "mounted device"
[18:22] <Chipaca> swartzr, not sure how that's different from the other two
[18:22] <swartzr> Chipaca Well the device is already mounted so the directory would work
[18:23] <Chipaca> phew :-)
[18:24] <swartzr> Chipaca thanks for the info. Looks like I'll have come back to it in a while when that feature gets added.
[18:24] <Chipaca> swartzr, or get it working in devmode and add the interface and drop devmode when it's ready
[18:25] <Chipaca> that's what devmode is for, fwiw
[18:26] <swartzr> Chipaca yes!! that would work beautifully. It is an internal business app so devmode is really not a problem
[18:26] <Chipaca> swartzr, next week's release would also enable getting devmode snaps from the store
[18:26] <Chipaca> right now you can publish devmode snaps, but snapd doesn't know how to get them
[18:27] <Chipaca> (as the store doesn't hand them out unless asked explicitly)
[18:27] <Chipaca> they also don't appear in searches
[18:27] <swartzr> Chipaca maybe I'll publish it to the store it could be useful to others. Probably will open source it also.
[18:27] <Chipaca> \o/
[18:28] <Chipaca> swartzr, note that a devmode snap can't be in a "stable" channel
[18:28] <Chipaca> just beta and edge
[18:28] <Chipaca> but that shouldn't stop you :-)
[18:30] <tianon> are there any more detailed docs about getting 16-series snaps secured appropriately?  I've been messing with plugs, but I'm working on an updated "docker" snap so it's likely going to require a custom apparmor/seccomp profile anyhow (current old-style snap even allows switching to/from "privileged" mode/profiles via an included script), but I can't seem to find anything substantial about how to do th…
[18:30] <tianon> …at properly (because using "old-security" seems like the wrong approach) so any pointers would be very appreciated (even if they have to be pointers to parsing code or something) :)
[18:31] <kyrofa> g_, indeed, as you rightly pointed out the service system is very simple
[18:32] <kyrofa> g_ you kinda need to synchronize them manually I'm afraid
[18:32] <swartzr> Thanks for the help Chipaca. Looking forward to snappy's future.
[18:32] <swartzr> really impressed by how easy it is to create a snap
[18:33] <Chipaca> tianon, augh, this might be a bad time to take a poke at properly confining docker-style services
[18:33] <tianon> lol
[18:33] <Chipaca> tianon, we know what we have to do, but we're not there yet
[18:34] <tianon> yeah, that's the sense I'm getting while reading docs, etc
[18:34] <Chipaca> tianon, I'm a bit far from the people doing that work (and it's friday and i've already popped open a beer and dinner is in the oven, so grains of salt), but
[18:34] <Chipaca> tianon, basically we want to have something like a vm-manager interface
[18:35] <Chipaca> when i last followed this discussion it wasn't clear whether that was generalisable or whether it'd have to be a docker interface
[18:35] <Chipaca> which would be worse, but perhaps more practical
[18:35] <Chipaca> worse because then any other vm manager would need their own chunk of work
[18:35] <Chipaca> but such is the nature of this
[18:36] <tianon> yeah, that's fair
[18:36] <Chipaca> tianon, jamiebennett might know more, but he's in the same tz as i am
[18:36] <Chipaca> tianon, so if he hasn't kicked back for the weekend i want to know why
[18:37] <tianon> would it be possible to hack something together in the interim with a custom plug or something?  (hopefully I'm not too horribly misunderstanding too many snap concepts O:) )
[18:37] <Chipaca> also the sun is out, which is rare
[18:37] <tianon> :D
[18:38] <tianon> crap, have to go, but appreciate your time <3  (and will idle, so feel free to leave me novels)
[18:38] <Chipaca> tianon, interfaces are written (described?) in go, so the hackage would be very similar to the actual work
[18:38] <Chipaca> tianon, devmode devmode devmode
[18:38] <tianon> ah
[18:38] <tianon> yeah
[18:38] <tianon> was afraid of that
[18:38] <tianon> thanks :)
[18:38] <Chipaca> tianon, also, mailing list
[18:38] <Chipaca> helps us prioritize things if we see the demand
[18:38] <Chipaca> (irc doesn't bring too much visibility to demand, just to firefighting)
[18:39] <Chipaca> smells like dinner is ready
[18:39]  * Chipaca out
[18:53] <johnsno> Hi, any plans or existing forks of snapd for OS X ? Windows ?
[19:10] <jamiebennett> johnsno: No plans but we do welcome patches ;-)
[19:10] <jamiebennett> johnsno: In all fairness, Ubuntu runs on Windows 10 so it is not beyond the realms of possibility
[19:11] <jamiebennett> johnsno: macOS would definitely be interesting
[19:16] <jbicha> ev: thanks for looking into it
[19:17] <jbicha> yes I was just beta-testing, I don't actually know anything about cassandra, I was just clicking buttons :)
[19:17] <ali1234> any plans to make that win10 stuff use snappy core rather than just being a regular filesystem?
[19:17] <jbicha> it's still 'broken' from the cli, in that 'snap install' doesn't run that other cmd or ask the user to run it either
[19:18] <jbicha> sleeping would at least be better than 100% cpu
[19:18] <jamiebennett> ali1234: again, at this time no but anythings possible
[19:19] <ali1234> it seems logical... i mean is it even possible to dist-upgrade the win10 image?
[19:19] <kyrofa> elopio, https://github.com/ubuntu-core/snapcraft/pull/580 is ready for a look
[19:20] <jamiebennett> kirkland knows more than I on this, I've not really played with the Ubuntu on Win 10 stuff yet. Its really cool so definitely something on my todo list.
[19:21] <johnsno> jamiebennett: Ok thank you, I will try to work on macOS support on my free time
[19:21] <jamiebennett> johnsno: That would be awesome, please let me know how you get on
[19:24] <gouchi> what is a snapcraft option to rebuild the snap package if I just modified snapcraft.yaml or my wrapper ?
[19:24] <gouchi> because I tried snapcraft prime && snapcraft snap it doesn't take my modification
[19:24] <gouchi> everytime I need to do snapcraft clean && snapcraft build
[19:25] <kyrofa> gouchi, you can clean individual steps with `snapcraft clean -s <step>` or just clean the whole thing
[19:25] <gouchi> oh ok I will try this thank you
[19:25] <kyrofa> gouchi, which part of the YAML did you change?
[19:25] <ev> jbicha: sure thing, and if you find anything else odd with the Jenkins or Cassandra snaps, do let me know :)
[19:25] <bull> hello guys :)
[19:25] <gouchi> now it ok for the yaml
[19:25] <gouchi> I need to tweak my wrapper
[19:26] <bull> why snapcarft will not pull stage and prime new stuffs if we updated entries in snapcraft file after a build ???
[19:27] <bull> kyrofa, hi ,
[19:28] <bull> anyone know how to force snapcraft pull to check if files was modified and it have to pull  new enteirs ???
[19:30] <bull> i update my snapcraft file and do snapcraft pull and it says already ran as of now , is there a way to do force pull recheck snapcraft entries and do pull for new stuffs ??
[19:31] <kyrofa> bull, you need to clean the pull step
[19:31] <bull> doing snapcraft clean everytime after editing snapcraft.yaml file and redo everything from scratch looks stupid
[19:31] <bull> kyrofa,  is it a bug ???
[19:31] <bull> or i have to fire a new in launchpad ??
[19:32] <kyrofa> bull, you're telling it to pull new and potentially different stuff than what you previously told it. The way it currently makes sure it does what you need is blowing away what was there before and grabbing what you asked for
[19:33] <bull> also stage will not stage new entries after updating entries in yaml file
[19:34] <bull> kyrofa, you not getting me , am saying if i added some new libs to yaml file under parts , why pull will not know tthat i added new stuff there just download new stuff and add it to part dir
[19:35] <bull> why anyone will have to download all the downloaded packages and stuffs that he downloaded before ?? just if he adds something new
[19:36] <kyrofa> bull, you're saying you added brand new parts and snapcraft didn't notice them?
[19:37] <bull> am saying i added new libs under stage-packages and snapcraft did not noticed them
[19:38] <kyrofa> bull, yes, that's a bug
[19:39] <bull> why it need clean everything ?? if added a new entry ?? this is my question , as a normal user am asking this question , this makes me hate snapcraft thousands of people gonna test it , and am sure 500 will notice this !!
[19:39] <kyrofa> bull... we talked about this yesterday, and you already logged a bug for it
[19:40] <bull> my bug was about cleaning downloaded packages after hitting clean command
[19:40] <bull> this is soething different
[19:40] <kyrofa> bull, that's exactly what this is. In order to make sure it fetches the stage packages you updated, it removes the ones that were there already
[19:41] <bull> kyrofa, fox example take our normal ubuntu system , if i added something new in source file , to get some new stuffs , will apt clean my older packages ??? before i issue apt-get update ??
[19:42] <bull> what apt do is get the new updates and merge it into older one and allow you download new content
[19:45] <bull>  am just comparing the methodology am not saying make it apt :D , apt work very efficiently and the reason is its methodology
[19:46] <bull> snapcraft looks much like doing stupid things in this case !!!
[19:49] <bull> i hope you will pass these as a feedback snapcraft is new project and am providing these suggestion to make it better and sensible to users , cause am in social media hate someone criticize ubuntu and its technologies :) like a guy was talking crap about snapcraft - like 1.1gb libreoffice and shit
[19:51] <jcastro> bull: the openoffice snap is like 280 megs, not 1.1gb
[19:55] <ali1234> jcastro: only after everyone complained :)
[19:56] <bull> am not ceo of ubuntu or canonical and not forcing these changes - make snapcraft simple and sensible , people not gonna accept it like am not yet happy with its progress , people do not see what and how hard you guys are working in back , what they see is how they will have their application run on your platform , so they will drop snapcarft and snap at the first when they will spend their whole day making their app to run on ubuntu , for example my application y
[19:56] <bull> esterday i spend my whole day packaging my app which runs fine with normal debian packaging , after successfully packing it into snap it wont run and end up with segmentation faults etc i did all logical things and what i got at end is i spend my whole day packaging an app which still dont runs cause it is packed in snap  format
[19:58] <bull> ali1234, your are right , i read an article about it on a famous website where thousands of linux and ubuntu users visit everyday , i was talking about the same
[19:59] <swartzr> I'm snapping a python app but can't for the life of me figure out how to use a requirements file that is in my source tree. Can anyone help?
[20:00] <swartzr> I added requirements: requirements.txt but snappy doesn't pick it up
[20:00] <bull> simply , since we are dealing with dependencies within our packages and we are writing them in snapcraft.yaml we shpuld be able to change them anytime without dealing with what snapcraft is thinking about them we have to make snapcraft work like that ,
[20:02] <bull> kyrofa, i hope you will be noticing all this , am not a member of your team but consider me as a good tester :) m big fan of snapcraft but i would love to make it simple and sensible
[20:13] <hguant> quick question - is there a good resource for creating custom plugins?
[20:28] <tianon> Chipaca: ah, totally makes sense; thanks so much :)
[20:32] <Chipaca> hguant, not sure if kyrofa is still around for that one
[20:33] <Chipaca> hguant, but either him or sergiusens are the people who might be able to point you in the best direction to look
[20:33] <bull> kyrofa, i filed a bug about that issue , please read it here , is that okay ??? https://bugs.launchpad.net/snapcraft/+bug/1593868
[20:33] <hguant> Chipaca no worries - is there a mailing list I can ask in, or should I just lurk 'round here till one of them is on?
[20:34] <Chipaca> hguant, snapcraft@lists.ubuntu.com
[20:34] <hguant> Chipaca thanks!
[20:34] <Chipaca> hguant, https://lists.ubuntu.com/mailman/listinfo/snapcraft
[20:35] <Chipaca> yw!
[20:39] <bull> Chipaca, hi
[20:39] <Chipaca> bull, hi
[20:40] <bull> i just files a bug against snapcraft on launchpad , as a user of snapcraft do you think my writing is worth ??? https://bugs.launchpad.net/snapcraft/+bug/1593868
[20:40] <Chipaca> bull, i'll let the snapcraft devs dig into that one
[20:40] <bull> ty Chipaca
[20:41] <Chipaca> i'm not sure you're saying snapcraft should cache the old things it downloaded, or track the difference between edits
[20:41] <Chipaca> in either case, it sounds hard :-)
[20:42] <bull> it should not be hard , am just saying - snapcraft should download the new libs and do stage prime again
[20:43] <bull> instead of cleaning everything , and doing things from scratch
[20:44] <Chipaca> bull, and if the libs have interdependencies, such that the presence of libX modifies the way libY builds?
[20:44] <bull> also snapcraft should not delete the downloaded items by apt , deleting those debs and downloading them again make no sense :D
[20:45] <bull> Chipaca, thats why am saying it  should stage and prime again
[20:46] <Chipaca> bull, just in case you forget, i don't dev snapcraft
[20:46] <Chipaca> however
[20:47] <Chipaca> caching debs is the job of apt-cacher-ng or whatever the cool kids use these day
[20:47] <bull> i dont know why developers didn't caught it lol
[20:47] <Chipaca> not sure we want to duplicate that particular effort
[20:48] <bull> Chipaca, currently i dont think snapcraft is a good packaging tool :P
[20:49] <bull> you cant do nothing with that ??
[20:49] <Chipaca> bull, you're entitled to that opinion
[20:49] <bull> lol
[20:50] <bull> developers have to deal with guys like me so that they ca fix the bugs :D
[20:50] <jcastro> is there a clean way to not have snaps show up in tools like df? It's manageable now but the list keeps getting bigger every day
[20:52] <bull> jcastro, df you mean by tool which report file system disk space usage
[20:52] <jcastro> yes
[20:52] <bull> why you wana hide snaps from df ?? if am not getting you wrong
[20:52] <Chipaca> jcastro, does “df -h | awk '$6!~/^.snap/{print}'” count?
[20:53] <jcastro> yeah I was digging around the manpage for something that just will whole hog filter out /dev/loop things
[20:53] <bull> damn :/
[20:54] <Chipaca> jcastro, or “df -hT |grep -v squash”
[20:54] <bull> will one of you will brief me what you guys doing ??
[20:55] <bull> Chipaca, help me :3
[20:56] <Chipaca> bull, with what?
[20:56] <bull> why jcastro wana hide snaps from df??
[20:56] <bull> just for knowledge
[20:56] <Chipaca> bull, because he's installed 200 snaps?
[20:57] <jcastro> http://paste.ubuntu.com/17451287/
[20:57] <Chipaca> bull, or he's obsessively punctilious
[20:57] <jcastro> not quite 200, but at this rate ...
[20:57] <Chipaca> yeh
[20:57] <bull> wow :D
[20:58] <Chipaca> jcastro, I don't think we want to patch df :-) but maybe skipping squashfs with grep is good enough
[20:58] <jcastro> yeah, at first that seemed like a good idea but then I thought it through
[20:58] <bull> jcastro, those /dev/loops are snaps ??
[20:59] <Chipaca> jcastro, yes
[20:59] <Chipaca> um
[20:59] <Chipaca> bull, yes
[21:00] <bull> :)
[21:04] <bull> Chipaca, i will make my qt application opensource tonight , what license should be good if i don't want people to repblish it without asking me or make money from my work .?? thanks
[21:04] <Chipaca> bull, you can't make it opensource and not make it opensource
[21:05] <bull> why ?? i will publish it to github ,
[21:05] <Chipaca> bull, if it's opensource, people can republish it
[21:06] <Chipaca> that's kinda how it works
[21:06] <bull> i wana allow users to learn from it but i dont want anyone to republish it , so that he/she can make money from it  by remob=ving my rights
[21:08] <bull> okay i let them republish it , but how can i stop someone from removing my rights from the code :/ is there any such opensource license ??
[21:09] <Chipaca> bull, what do you mean by "removing your rights from the code"?
[21:09] <bull> Chipaca, that i am the author of that code
[21:09] <bull> :(]
[21:09] <Chipaca> bull, that is an unalienable right
[21:09] <Chipaca> :-)
[21:09] <bull> i should not use any license then :???
[21:10] <Chipaca> bull, so if people remove you as author, they'll be committing a crime of some sort? or doing something bad. i'm not a lawyer.
[21:10] <Chipaca> also if you wrote the code in your own time, you have copyright over the code
[21:10] <bull> its getting offtopic here , sorry guys i have to stop it now
[21:11] <bull> i wrote code myself :D
[21:11] <Chipaca> so any floss license preserves those things
[21:11] <bull> gpl 3 ??
[21:12] <Chipaca> bull, my recommendation would be that you do your research and don't just decide based on what somebody tells you
[21:12] <bull> you are a goof friend :* thanks for help
[21:12] <Chipaca> bull, http://choosealicense.com/ might be a good place to start
[21:13] <bull> i was snapping that app but after snapping it show unreliable output wheni run it
[21:13] <bull> ty :) Chipaca
[21:13] <Chipaca> i'm off for the weekend
[21:13] <Chipaca> o/
[21:15] <bull> i choosed gpl3
[21:16] <bull> Chipaca, can i find you here , when i wana talk to you ?? i will not always seeking help from you i just want you as a friend :P
[21:18] <bull> Chipaca, :/
[21:19] <mhall119> bull: what's going on with your snap?
[21:20] <bull> mhall119,  hi :)
[21:20] <bull> its not working like yesterday
[21:21] <mhall119> where's it stopping today?
[21:21] <bull> so am putting my code in repo so someone can build snap for it :P
[21:21] <mhall119> ok
[21:21] <palasso> bull: check this out as well https://tldrlegal.com/
[21:21] <bull> no network or x11 issues today
[21:22] <mhall119> (no network) issues
[21:22] <mhall119> or no (network issues)
[21:22] <mhall119> ? :)
[21:23] <bull> mhall119,  qt was reporting network issues yesterday
[21:23] <mhall119> but that's fixed now?
[21:23] <bull> palasso, thanks :)
[21:23] <bull> mhall119, yes it is fixed
[21:23] <bull> am keeping all these bugs in mind so i will help someone if he/she faces same :)
[21:24] <bull> mhall119, am publishing the code
[21:24] <bull> under gpl3 license :D
[21:32] <bull> mhall119,  you there ?
[21:45] <mhall119> bull: yeah, end of day already and getting ready for dinner though
[21:46] <bull> i uploaded it here https://github.com/keshavbhatt/Deskie
[21:46] <bull> i want your help creating snap for it please :(
[21:47] <bull> desktop icon also not detected automatically :/ idk whats wrong with it
[21:48] <bull> i will create a new branch there to where i will make snap recipe  for deskie please contribute there ...
[21:52] <sgclark> you have to put the icon in setup/gui atm. I am working on a way to automate that, I have desktop files working ( automated )
[21:52] <sgclark> and it has to have the name of icon.png
[21:57] <bull> sgclark, will you give me a pastebin of your example .desktop file so i can see the icon entry in it??
[21:57] <bull> as i already having the same setup still it dont work mean i need mosify something in .desktop
[21:58] <sgclark> oh. I see. in that case no most kde apps are also missing that entry, I have a pile of bug reports to file when I get home...
[22:00] <bull> okay sgclark
[22:00] <sgclark> which is why my automation for icons is broken :)
[22:26] <bull> good night guys feeling sleepy :( i have uploaded the first snapshot og deskie here https://github.com/keshavbhatt/Deskie
[22:26] <bull> there is a new branch fo snapping the application