[10:31] <mup> Issue snapcraft#2044 opened: snap install process creates empty dirs on Home folder <Created by mmartinortiz> <https://github.com/snapcore/snapcraft/issue/2044>
[12:09] <petan> how can I register an URI protocol so that my app is launched when someone clicks a link in browser?
[12:09] <petan> is there any snappy option for this?
[12:09] <petan> my app is irc client so I want to register irc:// and ircs://
[14:18] <Mavrik> Hi, I'm having trouble finding in documentation on how to exclude a part from the final snap when defining snapcraft.yaml - I have parts that are essentially only build dependencies and their binaries shouldn't be included in the final snap. Any ideas?
[14:22] <kyrofa> Mavrik, definitely-- you want to use the `prime` keyword to filter the entire part out
[14:22] <kyrofa> Mavrik, let me find you an example
[14:23] <kyrofa> Mavrik, here, boost is a part only needed to build mysql, and shouldn't be shipped in the final snap. Using the `prime` keyword, it is filtered out like this: https://github.com/nextcloud/nextcloud-snap/blob/master/snap/snapcraft.yaml#L246
[14:23] <Mavrik> oh, hmm, lemme try this
[14:24] <Mavrik> Yup, that did it. Thanks!
[14:25] <kyrofa> Sure thing
[14:25] <kyrofa> Mavrik, the syntax for these keywords is here, for future reference: https://docs.snapcraft.io/build-snaps/syntax
[14:25] <kyrofa> Er, documentation, rather
[14:27] <Mavrik> Yeah, I found that, I just didn't think of just wildcarding everything out.
[14:29] <mup> PR snapcraft#2041 closed: kernel plugin: add kmod as build-package <Created by kyrofa> <Merged by kyrofa> <https://github.com/snapcore/snapcraft/pull/2041>
[14:35] <mup> PR snapcraft#1930 closed: lxd: friendly errror with suggestions if network is broken <Created by kalikiana> <Merged by kyrofa> <https://github.com/snapcore/snapcraft/pull/1930>
[14:46] <Mavrik> Hmm, another question - binary in my snap has to invoke a binary in /usr/local/bin or /usr/share/bin of the installed system. As I see, "strict" confinement prevents this. Any way to ask for access ?
[14:54] <mup> Bug #1746710 opened: Snap creates redundant duplicate directories in home folder <amd64> <apport-bug> <artful> <bionic> <Snappy:New> <snapd (Ubuntu):Confirmed> <https://launchpad.net/bugs/1746710>
[14:58] <kyrofa> Mavrik, no, that sort of defeats the purpose of confinement. Is there a reason you can't bundle these applications within the snap itself?
[14:58] <kyrofa> You can use a different confinement type if necessary, but that depends on the use-case
[14:59] <Mavrik> My tool is invoking "adb" from Android SDK which spawns a daemon on first invocation.
[14:59] <Mavrik> And there's a plethora of problems if you invoke different versions of adb one after another.
[14:59] <kyrofa> How do you ensure adb is actually installed?
[15:00] <Mavrik> So if I package adb with my snap and the user is an Android developer, it'll interfere with their Android Studio IDE
[15:00] <Mavrik> Hmm, the documentation implied I should use stage-packages: android-tools-adb for this
[15:00] <Mavrik> To basically add system dependency.
[15:00] <kyrofa> Mavrik, stage-packages get placed into the snap
[15:00] <Mavrik> (I'm also opening a forum thread to see if there's a better way.)
[15:00] <Mavrik> Ah.
[15:00] <Mavrik> Hrmf.
[15:01] <kyrofa> You can use classic confinement (i.e. unconfined) if such access is required, but that's subject to a more thorough review
[15:02] <Mavrik> yeah, that's fine with me for now
[15:04] <mup> PR core-build#11 closed: remove cruft from the writable-paths <Created by mvo5> <https://github.com/snapcore/core-build/pull/11>
[15:04] <mup> PR core-build#22 closed: unit testing for sync_dir() <Created by mvo5> <https://github.com/snapcore/core-build/pull/22>
[15:04] <mup> PR core-build#26 closed: move most of the customization into the core snap build <Created by mvo5> <https://github.com/snapcore/core-build/pull/26>
[15:04] <Mavrik> I'll open a topic as the review system demands and see what the conclusion is :)
[15:05] <mup> PR core-build#11 opened: remove cruft from the writable-paths <Created by mvo5> <https://github.com/snapcore/core-build/pull/11>
[15:05] <mup> PR core-build#22 opened: unit testing for sync_dir() <Created by mvo5> <https://github.com/snapcore/core-build/pull/22>
[15:05] <mup> PR core-build#26 opened: move most of the customization into the core snap build <Created by mvo5> <https://github.com/snapcore/core-build/pull/26>
[16:03] <mup> PR core-build#22 closed: unit testing for sync_dir() <Created by mvo5> <https://github.com/snapcore/core-build/pull/22>
[16:03] <mup> PR core-build#26 closed: move most of the customization into the core snap build <Created by mvo5> <https://github.com/snapcore/core-build/pull/26>
[16:04] <mup> PR core-build#11 opened: remove cruft from the writable-paths <Created by mvo5> <https://github.com/snapcore/core-build/pull/11>
[16:04] <mup> PR core-build#22 opened: unit testing for sync_dir() <Created by mvo5> <https://github.com/snapcore/core-build/pull/22>
[16:04] <mup> PR core-build#26 opened: move most of the customization into the core snap build <Created by mvo5> <https://github.com/snapcore/core-build/pull/26>
[16:12] <mup> Issue snapcraft#2044 closed: snap install process creates empty dirs on Home folder <Created by mmartinortiz> <Closed by kyrofa> <https://github.com/snapcore/snapcraft/issue/2044>
[16:52] <kyrofa> jdstrand, I'm getting a store review failure I've never seen before, and I haven't changed anything in the snap: found errors in file output: unusual mode 'rwxr-sr-x' for entry './error/include', unusual mode 'rwxr-sr-x' for entry './icons/small' security-snap-v2_squashfs_files
[16:53] <kyrofa> The snap is being built on launchpad
[16:53] <kyrofa> Any ideas?
[17:00] <kyrofa> They're all failing that way, now
[17:03] <kyrofa> Also, when I download the snap, I don't see that: drwxr-xr-x 2 kyrofa kyrofa  4096 Apr  2 09:48 include
[17:04] <kyrofa> drwxr-xr-x 2 kyrofa kyrofa  12288 Apr  2 09:48 small
[17:09] <jdstrand> kyrofa: you are shipping setgid files. don't do that
[17:09] <jdstrand> hmm
[17:09] <kyrofa> jdstrand, not that I can see
[17:09] <jdstrand> kyrofa: what is the snap?
[17:09] <kyrofa> jdstrand, here's a failed rev: https://dashboard.snapcraft.io/snaps/nextcloud/revisions/6106/
[17:13] <jdstrand> kyrofa: by 'download the snap', you mean you are running unsquashfs and then examining? if so, unless you do that as root, the setgid bit is stripped. you can use 'unsquashfs -lls <snap>'
[17:13] <jdstrand> kyrofa: $ unsquashfs -lls /home/jamie/Desktop/njObIbGQEaVx1H4nyWxchk1i8opy4h54_6106.snap | grep error/include
[17:13] <jdstrand> drwxr-sr-x root/root                81 2018-04-02 11:48 squashfs-root/error/include
[17:13] <jdstrand> ...
[17:15] <kyrofa> Ah, yes that's what I meant
[17:16] <kyrofa> Huh. jdstrand did we just add that check?
[17:16] <kyrofa> I haven't changed anything, I'm not even sure which part is providing these files
[17:16] <jdstrand> kyrofa: no. been there for ages
[17:16] <kyrofa> How odd
[17:16] <jdstrand> snapcraft is supposed to clean those up afaik
[17:16] <jdstrand> maybe that cleanup changed?
[17:17] <kyrofa> That's possible
[17:18] <kyrofa> Not because anything changed of which I'm aware, but because a new snapcraft was released relatively recently
[17:19] <kyrofa> Oh, Apache is doing this
[17:20] <kyrofa> Yeah, what the heck-- the Apache tarball ships with setgid dirs
[18:03] <mup> PR core#83 closed: move most of the ubuntu-core config deb into the snap snap build <Created by mvo5> <https://github.com/snapcore/core/pull/83>
[18:04] <mup> PR core#38 opened: Add another pi-config option <Created by sergey-borovkov> <https://github.com/snapcore/core/pull/38>
[18:04] <mup> PR core#83 opened: move most of the ubuntu-core config deb into the snap snap build <Created by mvo5> <https://github.com/snapcore/core/pull/83>
[18:34] <mup> PR # closed: snapd#3963, snapd#4358, snapd#4369, snapd#4387, snapd#4399, snapd#4416, snapd#4443, snapd#4497, snapd#4504, snapd#4509, snapd#4510, snapd#4538, snapd#4545, snapd#4551, snapd#4562, snapd#4588, snapd#4600, snapd#4700, snapd#4750, snapd#4767, snapd#4790, snapd#4805, snapd#4832,
[18:34] <mup> snapd#4833, snapd#4840, snapd#4844, snapd#4845, snapd#4868, snapd#4873, snapd#4880, snapd#4889, snapd#4900, snapd#4911, snapd#4917, snapd#4930, snapd#4938, snapd#4940, snapd#4942, snapd#4951, snapd#4957, snapd#4965, snapd#4967
[18:35] <mup> PR # opened: snapd#3963, snapd#4358, snapd#4369, snapd#4387, snapd#4399, snapd#4416, snapd#4443, snapd#4497, snapd#4504, snapd#4509, snapd#4510, snapd#4538, snapd#4545, snapd#4551, snapd#4562, snapd#4588, snapd#4600, snapd#4700, snapd#4750, snapd#4767, snapd#4790, snapd#4805, snapd#4832,
[18:35] <mup> snapd#4833, snapd#4840, snapd#4844, snapd#4845, snapd#4868, snapd#4873, snapd#4880, snapd#4889, snapd#4900, snapd#4911, snapd#4917, snapd#4930, snapd#4938, snapd#4940, snapd#4942, snapd#4951, snapd#4957, snapd#4965, snapd#4967
[18:54] <cwayne> jeeze mup
[18:55] <popey> cwayne: do you know who 'owns' the network-manager snap?
[18:56] <cwayne> popey: abeato I think (or more generally, anewman's team)
[18:56] <popey> ah okay.
[18:56] <popey> anewman: hello. :) is it possible to get nmtui added to the network-manager snap?
[18:56] <cwayne> Is there an issue with it?
[18:56] <cwayne> Ah
[18:57] <popey> nmtui is a great UI for connecting to networks, nmcli is not
[18:57] <anewman> popey: is this for use on Ubuntu Core?
[18:58] <popey> yes
[18:59] <anewman> Okay. The most common user of network manager is a management system of some sort speaking d-bus so we haven’t been super focused on UI. We also have some snap configure hooks for basic settings.
[18:59] <popey> ok. I have installed core on a laptop and am using it like a weird person might
[19:01] <anewman> Is nmtui part of network-manager itself? If so, that seems pretty straightforward.
[19:03] <popey> on ubuntu proper it's in the network-manager package
[19:05] <anewman> So we probably just stripped it out to keep the dependencies at a minimum. Sounds simple.
[19:06] <anewman> popey: reckon you could file a bug here: https://launchpad.net/snappy-hwe-snaps
[19:06] <popey> sho thang
[19:08] <popey> done
[19:20] <popey> jdstrand: i am getting the snap review fail for emoj. It's a command line tool and I added x11 because it uses xsel, but doesn't need a desktop file
[19:20] <popey> https://dashboard.snapcraft.io/snaps/emoj/revisions/19/
[19:34] <mup> Bug #1746710 changed: Snap creates redundant duplicate directories in home folder <amd64> <apport-bug> <artful> <bionic> <snapd (Ubuntu):Confirmed> <https://launchpad.net/bugs/1746710>
[20:50] <popeycore> huzzah. irssi on ubuntu core.
[20:51] <popey> jdstrand: do you know what the plan is for a classic interface?
[20:52] <popey> https://forum.snapcraft.io/t/classic-interface/4806 :)
[20:56] <mup> PR snapcraft#2045 opened: many: add override-pull scriptlet <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/2045>
[21:27] <jdstrand> popey: not any more than what you asked about, no
[21:27] <popey> ah okay.
[21:28] <popey> it's a bummer not being able to run more than one thing at once on a core system
[23:07] <Caelum> zyga: ping
[23:09] <Caelum> zyga: guy I know from linux gaming discord who is deeply involved in oS suggested another addition to your canonical-docs PR, also update Leap version from 42.2 to 42.3