[00:11] <nacc> kyrofa: ... ok
[00:11] <nacc> sergiusens: if you can confirm, i can do it
[00:24] <nacc> kyrofa: thannks, i see it in the snapcraft yaml and also saw it earlier with conjure-up. Will try that!
[00:57] <nacc> kyrofa: ok, now i'm confused, if i build my own python != ubuntu python (e.g., 3.6 instead of 3.5 in xenial), how do i ensure the parts that depend on it use that python? it seems like it's usinng the packaged python3 to build the modules
[05:35] <lool-> kyrofa: shoot!
[05:36] <lool-> kyrofa: I'm on the west coast for the week, not watching IRC much though
[05:47] <mup> PR snapd#3967 closed: release: release snapd 2.28 <Created by mvo5> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3967>
[05:47] <mup> PR snapd#3969 closed: hooks: rename refresh hook to post-refresh <Created by stolowski> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3969>
[05:50] <mup> PR snapd#3968 closed: daemon: use client.Snap instead of map[string]interface{} for snaps <Created by chipaca> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3968>
[05:51] <mup> PR snapd#3962 closed: tests: Increase SNAPD_CONFIGURE_HOOK_TIMEOUT to 3 minutes to install real snaps <Created by sergiocazzolato> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3962>
[05:52] <mup> PR snapd#3960 closed: travis: switch to container based test runs <Created by mvo5> <Closed by zyga> <https://github.com/snapcore/snapd/pull/3960>
[06:32]  * zyga-ubuntu -> breakfast
[07:24]  * zyga-ubuntu bisects snap-seccomp regression
[08:20] <zyga-ubuntu> doko: hey
[08:21] <zyga-ubuntu> doko: not sure if you are at the rally or at home
[08:21] <zyga-ubuntu> doko: I ran into something that I don't understand and I think you could shed some light on it
[08:21] <zyga-ubuntu> doko: I summarized the problem here: https://forum.snapcraft.io/t/snap-seccomp-fails-tests-on-artful-is-it/2263/4?u=zyga
[08:21] <zyga-ubuntu> doko: a small test program doesn't compile
[08:21] <zyga-ubuntu> doko: and fails with the following error
[08:21] <zyga-ubuntu> /usr/include/stdlib.h:25:10: fatal error: bits/libc-header-start.h: Nie ma takiego pliku ani katalogu
[08:21] <zyga-ubuntu> (no such file or directory, sorry about that last fragment)
[08:31]  * zyga-ubuntu moves to another task, not sure how to do this 
[09:21] <mup> PR snapd#3970 opened: interfaces/mount,cmd/snap-update-ns: move change code <Created by zyga> <https://github.com/snapcore/snapd/pull/3970>
[09:31] <zyga-ubuntu> man, this is a lonely week here
[09:39] <Neeraj> "Issues while validating snapcraft.yaml: Additional properties are not allowed ('grade', 'confinement' were unexpected)" in snap classic
[09:39] <Neeraj> can anybody help
[09:41] <zyga-ubuntu> Neeraj: hey
[09:41] <zyga-ubuntu> Neeraj: drop grade, I think it's not used anymore
[09:41] <zyga-ubuntu> Neeraj: what was the value of "confinement"?
[09:42] <Neeraj> confinement is "strict"
[09:42] <zyga-ubuntu> Neeraj: not sure what the latter part of the message is about
[09:43] <zyga-ubuntu> try again and tell me what you get
[09:43] <Neeraj> Issues while validating snapcraft.yaml: Additional properties are not allowed ('confinement' was unexpected)
[09:44] <Neeraj> is it ok to drop confinement
[09:44] <Neeraj> (classic)admin@GTXQB02:~/TSE$ snapcraft Issues while validating snapcraft.yaml: Additional properties are not allowed ('confinement' was unexpected)
[09:44] <Neeraj> I am in classic mode
[09:45] <zyga-ubuntu> Neeraj: what do you mean you are in classic mode?
[09:46] <Neeraj> --beta --devmode classic
[09:47] <zyga-ubuntu> Neeraj: do you mean that the snap you've installed is in that mode and that somehow affects how it validates in snapcraft?
[09:47] <Neeraj> yes
[09:48] <Neeraj> zyga-ubuntu : is you are correct
[09:49] <Neeraj> zyga-ubuntu: snapcraft executes only in classic mode
[09:50] <zyga-ubuntu> Neeraj: hmm, I doubt that how snapcraft is installed affects how it validates other snaps
[09:51] <zyga-ubuntu> Neeraj: in any case, I'm not a snapcraft developer, please ask when US wakes up :/ I don't know what the problem might be
[09:51] <zyga-ubuntu> Neeraj: if you pastebin the snapcraft.yaml and open a forum thread it will be easier to get an answer in other timezones
[11:29] <mup> PR snapd#3971 opened: interfaces/mount: make Change.Perform testable and test it <Created by zyga> <https://github.com/snapcore/snapd/pull/3971>
[12:30] <kalikiana_> o/
[12:43]  * zyga-ubuntu -> break
[12:45] <Son_Goku> >_>
[13:51] <__chip__> zyga-ubuntu: good morning sah
[14:19] <jdstrand> sergiusens: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1598309/comments/5
[14:19] <mup> Bug #1598309: The aplay command doesn't work <snapd-interface> <xenial> <snapd (Ubuntu):Fix Released by jdstrand> <https://launchpad.net/bugs/1598309>
[14:21] <jdstrand> sergiusens: fyi, two people in this room hit this issue and were annoyed by it, in fact, considering classic confinement
[14:46] <Chipaca> zyga-ubuntu: o/?
[14:50] <jdstrand> sergiusens: https://forum.snapcraft.io/t/snap-and-executable-stacks/1812
[14:51] <zyga-ubuntu> Chipaca: hey
[14:51] <zyga-ubuntu> Chipaca: how are things?
[14:52] <zyga-ubuntu> jdstrand: hello
[14:52] <apol> sergiusens: https://bugs.launchpad.net/snapcraft/+bug/1719928
[14:52] <mup> Bug #1719928: snapcraft update won't fetch from SNAPCRAFT_PARTS_URI  <Snapcraft:New> <https://launchpad.net/bugs/1719928>
[15:05] <mup> PR snapd#3972 opened: repo: sanitize plugs and slots early in ReadInfo <Created by stolowski> <https://github.com/snapcore/snapd/pull/3972>
[15:08] <jamesh> zyga-ubuntu: hi.  Thanks for the review of my user-mounts PR.  There were a few change suggestions (moving code to snap-update-ns, persisting mount namespaces, etc).  Want to discuss?
[15:08] <zyga-ubuntu> jamesh: hi
[15:08] <zyga-ubuntu> jamesh: yes!
[15:08] <zyga-ubuntu> jamesh: I think mvo was trying to set up a hangout
[15:09] <zyga-ubuntu> jamesh: can you guys get together and join, say, the daily standup HO?
[15:09] <jamesh> zyga-ubuntu: mvo said he didn't necessarily need to be in the hangout.  Let me find some place quiet
[15:09] <zyga-ubuntu> aha, that's fine
[15:10] <zyga-ubuntu> I'm ready as you are, just give me the word
[15:26] <zyga-ubuntu> https://github.com/snapcore/snapd/pull/3973
[15:26] <mup> PR #3973: cmd/snap-confine: put processes into freezer hierarchy <Created by zyga> <https://github.com/snapcore/snapd/pull/3973>
[15:26] <mup> PR snapd#3973 opened: cmd/snap-confine: put processes into freezer hierarchy <Created by zyga> <https://github.com/snapcore/snapd/pull/3973>
[15:29] <apol> kalikiana_: http://www.proli.net/2017/05/23/kdevelop-runtimes-docker-and-flatpak-integration/
[15:36] <mup> PR snapd#3974 opened: Recognise Solus as a classic Linux distribution <Created by ikeydoherty> <https://github.com/snapcore/snapd/pull/3974>
[15:38] <zyga-ubuntu> ikey: thank you!
[15:38] <ikey> np bud
[15:39] <ikey> more to come probably
[15:39] <ikey> we need snapd/polkit for the solus SC to work
[15:39] <ikey> so im taking us to git which means making git support solus :P
[15:40] <ikey> i considered changing the conditional to if distro == ubuntu but then i remembered everyone mangles their os-release/lsb_release for branding ..
[15:40] <zyga-ubuntu> "taking us to git" ?
[15:40] <ikey> taking solus snapd package to git in unstable
[15:40] <ikey> vs released pkg
[15:40] <ikey> so that i can get SC working
[15:40] <Son_Goku> zyga-ubuntu: this check really needs to be reworked
[15:40] <ikey> Son_Goku, it would break ubuntu derivatives that rebrand
[15:40] <ikey> and others
[15:40] <ikey> i had the same thought
[15:40] <ikey> but i dont see it as viable
[15:41] <ikey> which is why its "explicitly not ubuntu" vs "is ubuntu"
[15:41] <Son_Goku> ikey: well, if we check for ID and ID_LIKE for particular values to enable ubuntu-ish behavior
[15:41] <ikey> assuming derivs arent derping that already
[15:41] <Son_Goku> then default to not enabling ubuntu-ish behavior, it's more likely to work properly
[15:41] <ikey> and im not aware of many using ID_LIKE
[15:41] <ikey> tbh
[15:42] <Son_Goku> most derivatives of the major distributions use ID_LIKE
[15:42] <ikey> yknow what'd simplify it all together?
[15:42] <Son_Goku> for example, even RHEL identifies as "like Fedora"
[15:42] <ikey> if the snapd package in the repos contains a file saying a reexec is OK
[15:42] <Son_Goku> ikey: runtime detection? :)
[15:42] <ikey> so its determined at packaging level
[15:42] <ikey> and all derivs implicitly use it
[15:42] <ikey> unless they repackage
[15:42] <Son_Goku> ikey: in Fedora, I do that for re-exec
[15:43] <Son_Goku> that's the /etc/sysconfig/snapd
[15:43] <Son_Goku> because otherwise derivatives are busted
[15:43] <ikey> stateless it! :P
[15:43] <ikey> lol
[15:44] <Son_Goku> well, I was talking to mvo earlier about making it so snapd didn't depend on environment variables to do this
[15:44] <Son_Goku> and instead read a config file in /etc/ and in /usr/share
[15:44]  * ikey likey
[15:44] <Son_Goku> (with /etc/ overriding /usr/share values, obviously)
[15:44] <ikey> :D
[15:44] <Son_Goku> well, this scheme is something we've been moving to as a whole in Fedora
[15:44] <ikey> ah good
[15:44] <Son_Goku> it's why we don't recommend doing dumb things like using environmentfiles
[15:45] <ikey> heh
[15:45] <Son_Goku> but the Go community explicitly recommends controlling by environment files
[15:45] <ikey> and then systemd was like hey - lets reinvent pam_env xD
[15:45] <Son_Goku> well, at least the pam_env works with packager -> override by admin model
[15:45] <ikey> mm
[15:45] <Son_Goku> err, the systemd version
[15:45] <Son_Goku> the pam_env doesn't
[15:45] <ikey> ya no that ones bork
[15:45] <Son_Goku> everything lives in bloody /etc
[15:46] <Son_Goku> my ideal is that /etc/ would be drained of things shipped by packages
[15:46] <ikey> yeo
[15:46] <ikey> *yep
[15:46] <ikey> i think we need to align all distros on the new wheres though
[15:46] <ikey> in clr and solus we went for /usr/share/defaults for renamespaced config fallbacks
[15:46] <ikey> and if sensible, /usr/share/$pkg
[15:47] <ikey> like pulseaudio
[15:47] <Son_Goku> ikey: I was starting to use /usr/share/$pkg/sysconfig
[15:47] <ikey> ew
[15:47] <ikey> its not config :p
[15:47] <Son_Goku> well, it is
[15:47] <ikey> its default stuff lol
[15:47] <ikey> (oh we also use /usr/share/xdg/* )
[15:47] <Son_Goku> well, the idea is that /etc/sysconfig would override /usr/share/*/sysconfig
[15:47] <ikey> plus having a single namespace is nicer for tooling
[15:47] <ikey> /usr/share/defaults/*
[15:48] <Son_Goku> though if I could have my way, I'd flip it to /usr/share/sysconfig and /etc/sysconfig as the override
[15:48] <ikey> yeah
[15:48] <ikey> easier for autotools too tbh
[15:48] <Son_Goku> yeah
[15:48] <Son_Goku> the reason I didn't call it defaults is because in many cases, applications don't support partial overrides
[15:49] <ikey> shpose
[15:49] <Son_Goku> and that the whole config files have to be overridden
[15:49] <ikey> a lot of our stateless patches end up being something like:
[15:49] <ikey> const char *cfg = NULL;
[15:49] <ikey> if (access(SYSTEM_CONFIG, F_OK) == 0) {
[15:49] <ikey>     cfg = SYSTEM_CONFIG;
[15:49] <ikey> } else {
[15:50] <ikey>     cfg = VENDOR_CONFIG;
[15:50] <ikey> }
[15:50] <ikey> In a nut shell ^
[15:50] <Son_Goku> right
[15:50] <Son_Goku> and that does make sense
[15:50] <ikey> older applications are harder to do merges on
[15:50] <Son_Goku> and that's pretty much why I went with sysconfig as the directory name
[15:50] <ikey> yeah
[15:50] <Son_Goku> IMO, it's more obvious to people what it means
[15:50] <ikey> reason i disagree with the name is because the relation to SYSCONFDIR
[15:51] <Son_Goku> ah
[15:51] <ikey> When there is the mental separation of sys vs vendor
[15:51] <Son_Goku> I didn't think of that
[15:51] <ikey> or rather, os / data
[15:51] <Son_Goku> right
[15:51] <ikey> + config
[15:52] <ikey> its a tough one for sure but id love for us all to go the same path
[15:52] <ikey> whatever that path is
[15:52] <ikey> and then start prodding all the relevant projects to follow
[15:52] <Son_Goku> so another thought I had was /usr/share/vendorcfg
[15:52] <Son_Goku> and /etc/sysconfig for the admin version
[15:53] <Son_Goku> but I didn't like that so much because it's not as obvious for the mental map
[15:53] <ikey> as long as the package upstreams are onboard with the possibility of their vendorcfg being replaced by us
[15:53] <ikey> which is the issue i guess
[15:53] <ikey> we're the vendors they're the upstreams
[15:53] <Son_Goku> yeah
[15:53] <Son_Goku> well, the idea is that /etc/sysconfig is where users make their own configs
[15:53] <ikey> right
[15:53] <ikey> local sysadmin
[15:53] <Son_Goku> and /usr/share/vendorcfg is where the packages ship them
[15:54] <ikey> (you can see why we ended up with 'defaults' eh? :P)
[15:54] <Son_Goku> yeah
[15:54] <ikey> tbh its almost like "fallback" is the more appropriate term
[15:54] <Son_Goku> I threw away that name almost immediately because the implications that the name has
[15:54] <ikey> just sounds lame
[15:54] <ikey> yer
[15:54] <Son_Goku> naming things is hard :)
[15:54] <ikey> oh dont i know it
[15:55]  * ikey is the author of such wonders as 'Dave2' and 'libthingamabob'
[15:55] <kalikiana_> https://bugs.launchpad.net/snapcraft/+bug/1590599
[15:55] <mup> Bug #1590599: snapcraft prerequites are slow to resolve <eco-team> <Snapcraft:Fix Released by sergiusens> <https://launchpad.net/bugs/1590599>
[15:56]  * ikey looks at related snapcraft pull and hugs ypkg
[15:57] <kalikiana_> ikey: thinking of adding a snapcraft backend for ypkg? :-D
[15:58] <nacc> kyrofa: sorry to bother, but did you see my last messages from yesterday? how do I ensure that if I have a python3 part (e.g., for 3.6.2, while xenial has 3.5.x), that the subsequent parts use that python? (otherwise, there doesn't seem to be any modules installed by the subsequent part for 3.6)
[16:04] <ogra_> davidcalle, hrm .. all the links at the bottom of https://docs.ubuntu.com/core/en/reference/gadget#examples-of-production-ready-gagdet-snaps are wrong ...
[16:05] <davidcalle> ogra_: ok, what are the more recent ones?
[16:06] <ogra_> davidcalle, they are on GH ... i'd open a PR but that page doesnt seem to be in https://github.com/CanonicalLtd/ubuntu-core-docs/tree/master/en/guides/build-device
[16:06] <ogra_> boo
[16:07] <ogra_> because i'm in the wrong dir :P
[16:07] <davidcalle> ogra_: https://github.com/CanonicalLtd/ubuntu-core-docs/blob/master/en/reference/gadget.md
[16:07] <davidcalle> :D
[16:07] <ogra_> yeah, got it
[16:07] <ikey> kalikiana_, probably could
[16:07] <ikey> emit .snap's easily enough
[16:07] <ikey> id leave it until i have a solus base snap though
[16:08] <nacc> stokachu: --^ you might have a comment on my earlier point. As I thinkn you also have 3.6.2 in your snap as a part
[16:09] <nacc> also, why does `snapcraft pull` build stuff.
[16:10] <apol> SNAPCRAFT_PARTS_URI=http://metadata.neon.kde.org/snap/parts.yaml
[16:10] <apol> git://anongit.neon.kde.org/applications/kate.git
[16:12] <nacc> kyrofa: fwiw, if the 'fix' is to build python in a classic snap, that should be a hard requirement (it seems like this is 'known')?
[16:12] <nacc> sergiusens: --^
[16:13] <Chipaca> augh, no zyga now :-(
[16:13] <Chipaca> niemeyer: https://github.com/snapcore/snapd/pull/3964/files#diff-784fe30c70e6724012b7d456d65d97acL152
[16:13] <mup> PR #3964: many: implement our own ANSI-escape-using progress indicator <Created by chipaca> <https://github.com/snapcore/snapd/pull/3964>
[16:14] <Chipaca> niemeyer: :-D but also :-D
[16:15] <ogra_> davidcalle, https://github.com/CanonicalLtd/ubuntu-core-docs/pull/37
[16:15] <mup> PR CanonicalLtd/ubuntu-core-docs#37: point to proper repos for gadget examples <Created by ogra1> <https://github.com/CanonicalLtd/ubuntu-core-docs/pull/37>
[16:16] <davidcalle> ogra_: merged, thanks
[16:16] <ogra_> <3
[16:20] <mup> PR snapd#3975 opened: snap-confine: Only attempt to copy/mount NVIDIA libs when NVIDIA is used <Created by ikeydoherty> <https://github.com/snapcore/snapd/pull/3975>
[16:28] <Son_Goku> kalikiana_: https://gitlab.com/Conan_Kudo/snapcore-mkrpmtree & https://gitlab.com/Conan_Kudo/snapcore-mkrpmtree/pipelines/12211338
[16:28] <Son_Goku> :D
[16:30] <nacc> kyrofa: nm on the how to use the staged python, PEBKAC
[16:33] <apol> kalikiana_: https://bugs.launchpad.net/snapcraft/+bug/1719951
[16:33] <mup> Bug #1719951: SNAPCRAFT_PARTS_URI doesn't work with cleanbuild <Snapcraft:New> <https://launchpad.net/bugs/1719951>
[16:58] <ondra> ogra_ ping
[17:00] <mup> PR snapd#3976 opened: snap-confine: Support biarch Linux distribution confinement <Created by ikeydoherty> <https://github.com/snapcore/snapd/pull/3976>
[17:24] <mup> PR snapd#3977 opened: interfaces: Enhance full-confinement support for biarch distributions <Created by ikeydoherty> <https://github.com/snapcore/snapd/pull/3977>
[17:34] <magicaltrout> alright folks, how do i request a 2 track snap repo?
[17:37] <mup> PR snapd#3978 opened: cmd: Correctly name the "Ubuntu" and "Arch" NVIDIA methods <Created by ikeydoherty> <https://github.com/snapcore/snapd/pull/3978>
[17:42] <ogra_> ondra, moop
[17:48] <mvo> jdstrand: if you could have a quick look at https://github.com/snapcore/snapd/pull/3979 that would be great
[17:48] <mup> PR #3979: snap-confine: update apparmor rules for fedora based base snaps <Created by mvo5> <https://github.com/snapcore/snapd/pull/3979>
[17:48] <mup> PR snapd#3979 opened: snap-confine: update apparmor rules for fedora based base snaps <Created by mvo5> <https://github.com/snapcore/snapd/pull/3979>
[18:02] <ikey> looks like 3979 is covered by my PR
[18:02] <ikey> more completely
[18:03] <ikey> conflicts at least. :p
[18:03] <ikey> (3976)
[19:08] <zyga-ubuntu> Chipaca: hey
[19:08] <zyga-ubuntu> how's stuff in NYC?
[19:08] <Chipaca> zyga-ubuntu: hi!
[19:08] <Chipaca> zyga-ubuntu: not bad
[19:09] <zyga-ubuntu> I saw your PR, neat stuff
[19:09] <Chipaca> zyga-ubuntu: i pinged you yesterday and then was busy when you got back to me
[19:09] <zyga-ubuntu> oh, what about?
[19:09] <Chipaca> yes, i'm addressing your review now, thank you
[19:09] <zyga-ubuntu> :-)
[19:09] <zyga-ubuntu> travis is a bit slow today
[19:10] <Chipaca> zyga-ubuntu: I'm geting a "cannot perform operation: mount --bind yadda/yadda/etc/alternatives: permission denied"
[19:10] <Chipaca> zyga-ubuntu: so I thought maybe you'd know what i broke :)
[19:11] <Chipaca> zyga-ubuntu: (my base does have etc/alternatives)
[19:12] <zyga-ubuntu> Chipaca: yes, it's a non-generalized rules
[19:12] <zyga-ubuntu> *rule
[19:12] <zyga-ubuntu> Chipaca: can you show me the real denial (dmesg | grep DENIED)
[19:12] <zyga-ubuntu> Chipaca: I thought we fixed that, if not I can correct quickly if you confirm
[19:12] <Chipaca> zyga-ubuntu: PM
[19:13] <zyga-ubuntu> Chipaca: I had a productive day today so there's a few things up there but I'd like one thing merged
[19:13] <zyga-ubuntu> ack
[19:14] <zyga-ubuntu> https://github.com/snapcore/snapd/pull/3966
[19:14] <mup> PR #3966: cmd/snap-seccomp,osutil: make user/group lookup functions public <Created by zyga> <https://github.com/snapcore/snapd/pull/3966>
[19:14] <zyga-ubuntu> I'd love to land this so that I can iterate
[19:14] <zyga-ubuntu> Chipaca: I'll get some tea and propose a PR for that
[19:20] <ogra_> a PR for tea ... mmmm
[19:36] <roadmr> jdstrand: hey, tools r934 are in production now.
[20:29] <nacc> is there a 'best practices' for testing snaps as-installed?
[20:48] <mup> PR snapd#3980 opened: snap-confine: Ensure lib64 biarch directory is respected <Created by ikeydoherty> <https://github.com/snapcore/snapd/pull/3980>
[20:49] <kyrofa> nacc, not really, since it depends on what the snap is
[20:49] <kyrofa> nacc, for a webapp, I like running a capybara suite against it
[20:50] <nacc> kyrofa: e.g., we have dep8 that understands (from the src) how to run tests. It feels like we should have something, perhaps onnly for classic snaps, that allows a pivot to the classic and run a test suite
[20:50] <nacc> *to the classic snap
[20:52] <kyrofa> nacc, that might make sense to do as the part is being built, but perhaps less sense once the snap is assembled, as things might be completely reorganized and contain _several_ parts
[20:52] <nacc> kyrofa: yeah that's possibly true
[20:53] <nacc> i guess i also think there are some apps taht are being built, and the expectation is some behavior on them, e.g., asserted with unit tests. It would make sense to make it 'easy' to test in the snap as-installed, that the behavior is what you want
[20:53] <kyrofa> nacc, and I'm not sure how much sense it makes on a whole. For example, consider the Nextcloud snap. I'm not really interested in running MySQL's test suite, or Apache's
[20:53] <nacc> sure
[20:53] <kyrofa> But I sure want to test that the whole thing works in concert
[20:53] <kyrofa> Which is a different set of tests
[20:53] <nacc> but let's say you want to know that mysql accepts your statements, via a unit test.
[20:53] <nacc> yeah, I think we're actaully saying the same thing :)
[20:54] <kyrofa> But I can't even communicate with mysql from outside the snap. If mysql's unit tests don't pass I have other problems
[20:54] <kyrofa> You need some sort of higher-level acceptance tests
[20:54] <nacc> in classic you could, right?
[20:54] <nacc> i'm referring to classic in my case
[20:54] <nacc> i agree with confined snaps it's not easy to solve
[20:54] <nacc> or it's too snap-specific
[20:55] <kyrofa> nacc, so you're thinking you would bundle some sort of tests in the final snap?
[20:55] <nacc> yeah
[20:55] <nacc> that is intended to run in the same env as the sanp
[20:55] <nacc> and runs the tests in that env
[20:56] <kyrofa> nacc, that doesn't bloat the snap?
[20:56] <nacc> classic snaps are *really* easy to break
[20:56] <nacc> :)
[20:56] <kyrofa> Hahaha
[20:56] <nacc> with mixed hosts
[20:56] <nacc> (mixed = not all the same host OS)
[20:56] <kyrofa> nacc, so sort of a "am I sane" app
[20:56] <nacc> yeah, exactly
[20:56] <nacc> it's like a self-check
[20:56] <nacc> i guess that's what i can do
.selftest
[20:56] <nacc> i have the tests in my source
[20:56] <nacc> yep
[20:57] <nacc> kyrofa: thanks! that's a godo idea
[20:57] <kyrofa> nacc, seems reasonable!
[20:57] <nacc> rbasak: --^
[20:57] <kyrofa> nacc, I'm not sure I'd call it general guidance, but if that seems doable for your snap I think it seems nice a nice idea
[20:57] <kyrofa> Uh. seems like a nice... you get the idea
[20:57] <kyrofa> So braindead :P
[20:58] <nacc> kyrofa: yeah, it might not be generally useful. I think classic snaps need it more than confined. classic's runtime is far less well-defined
[20:58] <kyrofa> nacc, are you at the rally, by the way?
[20:58] <nacc> kyrofa: unfortunately not
[20:58] <kyrofa> nacc, agreed
[20:58] <kyrofa> nacc, darn, would have liked to meet
[20:58] <nacc> i'd be in the snappy room yelling otherwise :)
[20:58] <kyrofa> Ha!
[21:01] <ikey> im having issues with snap-update-ns from snapd git
[21:02] <ikey> snap-update-ns failed with code 1: No such file or directory
[21:02] <ikey> leaving note more as a reminder to myself tomorrow to bring it up
[21:06] <Son_Goku> zyga-ubuntu: https://bugs.launchpad.net/snappy/+bug/1719747
[21:06] <mup> Bug #1719747: Fedora 26 LXD container: cannot load apparmor profile <Snappy:New> <https://launchpad.net/bugs/1719747>
[21:08] <mup> PR snapd#3960 opened: travis: switch to container based test runs <Created by mvo5> <https://github.com/snapcore/snapd/pull/3960>
[21:08] <jdstrand> roadmr: oh! yay :)
[21:09] <jdstrand> oSoMoN: ^ (14:36 < roadmr> jdstrand: hey, tools r934 are in production now.)
[21:09] <jdstrand> roadmr: thank you :)
[21:09] <jdstrand> oSoMoN: that has the chromium fix
[21:09] <roadmr> jdstrand: np! we did an unrelated rollout but the tools update piggybacked on it :)
[21:09] <jdstrand> music to my ears :)
[21:09] <jdstrand> I <3 piggybacking
[21:10] <oSoMoN> jdstrand, yeah I noticed, my latest build went through without the need for a manual review, thanks!
[21:12] <roadmr> whee :)
[21:33] <jdstrand> ogra_: fyi, the issue with avahi is that ond ra uploaded the snap ahead of the feature that allows it to work. aka, update to 2.28 and it works fine
[21:33] <jdstrand> ogra_: I'm letting Til know now
[21:56] <mup> PR snapd#3979 closed: snap-confine: update apparmor rules for fedora based base snaps <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3979>
[22:05] <ikey> ow. my PR up in flames. :P
[22:16] <mup> PR snapd#3981 opened: release: 2.28.1 <Created by mvo5> <https://github.com/snapcore/snapd/pull/3981>
[23:28] <mcphail> ikey: +1 for including "whereby" in a pr