[06:04] <mborzecki> morning
[06:05] <mup> PR snapd#6274 closed: cmd, dirs, interfaces/apparmor: update distro identification to support ID="archlinux" (2.36) <Simple 😃> <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/6274>
[06:09] <mup> PR snapd#6277 opened: centos: enable SELinux support on CentOS 7 (2.36) <SELinux> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/6277>
[07:59] <pstolowski> morning!
[08:00] <mborzecki> pstolowski: hey
[08:00] <mborzecki> mvo: welcome back!
[08:01] <mvo> hey pstolowski and mborzecki ! thanks, glad to be back :)
[08:02] <mup> PR snapd#6272 closed: overlord/snapstate: run 'remove' hook before 'auto-disconnect' <Created by stolowski> <Merged by stolowski> <https://github.com/snapcore/snapd/pull/6272>
[08:03] <pstolowski> hey mvo o/, not resting today after travel?
[08:04] <mvo> pstolowski: I pushed that to the end of the week, I feel I need to take care of things first and see what happend while we were away and all that
[08:05] <mvo> zyga: also good morning to you :)
[08:08] <zyga> Good morning :-)
[08:09] <jamesh> mvo: hi.  I tried pushing an update to test-snapd-dbus-service last week that seems to have got stuck.  Launchpad built it okay, but it never published.  Is it waiting for "request manual review" by any chance?
[08:10] <zyga> mvo: how are you feeling? I though you planned on taking a swap day today
[08:10] <mborzecki> zyga: hey
[08:10] <zyga> o/
[08:11] <mvo> jamesh: good morning (evening in your case I guess) - let me check what is going on there
[08:11] <mvo> zyga: I feel better, I will swap end-of-week-ish I want to see what I missed and if there is anything I can help unblocking today
[08:12] <jamesh> mvo: by the way, your original PR was very helpful in putting together mine
[08:12] <mvo> jamesh: \o/ happy to hear that
[08:13] <mvo> jamesh: thanks for working on this feature!
[08:13] <jamesh> mvo: although I've been running into some problems with my current design for activating system services not through systemd units
[08:14] <zyga> what kind of problems?
[08:15] <jamesh> zyga: when doing non-systemd activation, the dbus-daemon-launch-helper program is spawned to start the daemon
[08:15] <jamesh> zyga: it uses a simplified version of the config file parser that ignores the <include> directive.  That means it doesn't know about the extra servicedir I configure
[08:16] <jamesh> everything works fine for session services and systemd activated services (both system and session)
[08:16] <jamesh> in particular, this is a problem for 14.04 where we can't do systemd activated system services
[08:16] <mvo> jamesh: can you give me the url to the snap that was build but is not published please? I will investigate, I don't see anything in the need-review queue right now
[08:17] <jamesh> mvo: the builds were done with this recipe: https://launchpad.net/~mvo/+snap/test-snapd-dbus-service
[08:17] <jamesh> which says it should publish to edge
[08:18] <mvo> jamesh: thank you
[08:19] <jamesh> zyga: one option would be to refactor the branch to comingle the service files in /usr/share/dbus-1/system-services with the rest of the ones from the system -- that might be a bit messier on core systems though
[08:20] <zyga> mborzecki: shall we merge https://github.com/snapcore/snapd/pull/6111 ?
[08:20] <zyga> neal didn't comment further
[08:20] <mup> PR #6111: packaging/opensuse: move most logic to snapd.mk <Created by zyga> <https://github.com/snapcore/snapd/pull/6111>
[08:20] <zyga> mvo: proposal, could we do a 2.36.3 or 2.37 end of this week
[08:21] <mborzecki> zyga: works for me, you can try and ping him one last time today
[08:21] <zyga> it could go to non-stable snap channel and non-ubuntu distributions
[08:21] <zyga> mborzecki: I'm really happy to iterate on top, just not feel like postpoing helps
[08:21] <mborzecki> zyga: ok, so let's land it
[08:21] <mborzecki> zyga: maybe ask pstolowski to take a look too
[08:21] <zyga> that works :)
[08:22] <zyga> pstolowski: would you mind having a look at the PR above, last one before landing, it refactors the build system around opensuse
[08:22] <zyga> and adds a shared element that can be easily reused for arch and fedora
[08:22] <mvo> jamesh: might be something silly like a expired macaroon that prevents the published, the last upload of this snap was >1y ago. anyway, I re-authed and triggered a new build that should do an upload then
[08:23] <pstolowski> zyga: sure
[08:23] <mvo> jamesh: I keep you updated
[08:23] <mvo> zyga: yeah, 2.37++
[08:23] <mvo> zyga: thanks for raising it
[08:23] <zyga> mvo: it would be lower risk
[08:23] <mvo> zyga: unless master is for some reason unfit for this
[08:23] <zyga> since not stable
[08:23] <zyga> mvo: yeah
[08:23] <zyga> mvo: but we could get some casual testing over xmas period
[08:23] <zyga> mvo: and a better feel of what 2.37.1 might look like
[08:24] <jamesh> mvo: awesome.  I've been running spread tests locally modified to use a local copy of the package, but that's only covering a couple of distros.  It'll be good to see results on the others.
[08:24] <mvo> zyga: yeah, having 2.37 in candidate for christmas would be great
[08:24] <mvo> jamesh: yeah
[08:24] <mvo> jamesh: you can always mail/tg me btw in such case, I was at a sprint last week so couldn't be on irc
[08:28] <jamesh> mvo: do you know how important 14.04 compatibility is for new features?
[08:28] <zyga> (on topic): mvo we should ask JamieBennett  or other stakeholders if 14.04 support extends over the extended paid support period
[08:29] <mvo> jamesh: "Store upload failed:
[08:29] <mvo>     Cannot upload new revisions for name=test-snapd-dbus-service
[08:29] <mvo> " (<- not very helpful, I will ask in the store channel)
[08:30] <mvo> jamesh: 14.04 we still need to support until it is EOL if we want support certain desktopish things that is unfortunate but not too terrible, our 14.04 work was always more server/cloud oriented
[08:30] <mvo> zyga: yeah, we were talking about ESM for snapd
[08:31] <jamesh> mvo: on the desktop side, my branch is fine.  However I thought it would be worth generalising it to system services too, and that's where the problems are
[08:31] <jamesh> so that's something that might be interesting to server/cloud
[08:31] <mvo> zyga: its not clear yet, I am personally not a huge fan because of the support burden (I think if we do it we need another push at systemd and update it to at least 205 there). I think it comes down to how many esm users are interessted in snaps
[08:31] <mvo> jamesh: oh, ok
[08:32] <zyga> mvo: I'm in agreement
[08:32] <mvo> jamesh: thats interessting, what is 14.04 missing here? is systemd too old or something else?
[08:32] <jamesh> but at the same time it is a new feature: it's not going to break any existing snaps
[08:32] <mvo> jamesh: thats good
[08:33] <jamesh> mvo: as my branch is currently designed, services directly activated by the system bus fail due to not being able to find the .service files
[08:33] <jamesh> mvo: on 14.04 systems, this means "all system services"
[08:34] <jamesh> on other distros where the system bus is launched by systemd, we could just tell people to make the service a daemon and be done with it
[08:34] <mvo> jamesh: aha, I see. so on 14.04 it is a fundamental problem because the system dbus is launched via upstart?
[08:35] <jamesh> mvo: yes.
[08:35]  * mvo nods
[08:35] <jamesh> mvo: the other option is to refactor the branch to put service files in /usr/share/dbus-1
[08:35] <jamesh> that means we can't assume the directory is entirely under our control
[08:36] <jamesh> and I'm not sure whether that's desirable on an ubuntu core system
[08:37] <mvo> jamesh: yeah, /usr is not writable on ubuntu-core systems
[08:37] <mvo> jamesh: does dbus look at any other dirs for this? /etc or /run ?
[08:40] <jamesh> mvo: the man page seems to indicate <standard_system_servicedirs/> will include /usr/local/share/dbus-1/system-services and /lib/dbus-1/system-services too
[08:41] <jamesh> although both of those could contain other files
[08:41] <mvo> jamesh: the other files I'm less concerned about but all of those will be read-only on core :/
[08:42] <jamesh> mvo: my current approach was to configure an extra <servicedir> through a config file in /usr/share/dbus-1/system.d, but the simplified config parser dbus-daemon-launch-helper uses ignores the include directive so doesn't see it
[08:43] <jamesh> mvo: we're fine for systemd activated services because they don't use launch-helper
[08:46] <mborzecki> anyone up for a 2nd review on https://github.com/snapcore/snapd/pull/6277 ? it's a backport to 2.36
[08:46] <mup> PR #6277: centos: enable SELinux support on CentOS 7 (2.36) <SELinux> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/6277>
[08:46] <zyga> perhaps mvo?
[08:46] <zyga> since it's a stable backport
[08:46] <mborzecki> mvo: ^^ pretty please
[08:47] <mvo> jamesh: aha, I see. hm, I need to look at the PR I think, I don't have enough state loaded right now about the details
[08:47] <mvo> zyga: yeah, will do, let me open it
[08:56] <mvo> jamesh: i386/amd64 of the snap should be available now
[08:57] <jamesh> mvo: thanks.
[08:58] <mup> PR snapd#6277 closed: centos: enable SELinux support on CentOS 7 (2.36) <SELinux> <Created by bboozzoo> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/6277>
[09:12] <Chipaca> moin moin moin
[09:12] <zyga> hello sir
[09:12] <Chipaca> how tings?
[09:12] <zyga> splendid
[09:12] <Chipaca> woo!
[09:12]  * Chipaca runs to the bank with that
[09:31] <mvo> hey Chipaca ! great to "see" you :)
[09:32] <Chipaca> mvo: I'd say the same, except you shouldn't be here :-)
[09:34] <mvo> Chipaca: nah, its fine, I will bugger off at the end of this week instead :)
[10:14] <zyga> Chipaca: idea, on a small terminal, snap list doesn't show revision and doesn't wrap
[10:14] <zyga> revision is really least useful part we show
[10:29] <Chipaca> zyga: I had adaptive output for things and it got -1'ed
[10:30] <zyga> boooo
[10:30] <zyga> I'm making a quick PR to look at
[10:30] <zyga> very dumb
[10:30] <zyga> but maybe enough :)
[10:30] <Chipaca> zyga: I tried to write it up in the forum, to explore finding a way out of it
[10:36] <cachio> mvo, hey
[10:36] <mvo> cachio: hey, great to see you - how are things?
[10:36] <cachio> 2.36.2 is ready to stable
[10:37] <mvo> cachio: \o/ if all is green and the store is happy I would say: lets do it :)
[10:37] <mvo> cachio: did we get some feedback from the desktop team, did they had a chance to try it as well?
[10:37] <cachio> mvo, nice, I'll ping store people
[10:37] <mvo> cachio: I know we got some +1 from advocay
[10:37] <mup> PR snapd#6278 opened: cmd/snap: modularize snap list processing <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6278>
[10:38] <cachio> mvo, I didn't get any feedback
[11:08] <mvo> cachio: ok, thanks, should be fine, they should run beta anyway :)
[11:09] <mvo> zyga: do you think you could look at 5845 again? iirc I addressed a lot (most?) of your comments
[11:09] <cachio> mvo, I was trying to reproduce the error installing the failing.snap in the failover test
[11:10] <cachio> mvo, https://paste.ubuntu.com/p/RF3SSzgNG8/
[11:10] <cachio> mvo, it is failing and the test exits
[11:11] <mvo> cachio: thanks, looking
[11:11] <cachio> mvo, no extra info, then the system reboots
[11:12] <mvo> cachio: hm, this is interessting: "Dec 08 23:42:33 dec082230-921432 snapd[1773]: daemon.go:670: Waiting for system reboot" and then "Dec 08 23:45:07 dec082230-921432 systemd[1]: snapd.service: Watchdog timeout (limit 5min)!"
[11:13] <mvo> cachio: what is the name of the test again? and does it always fail or is this sometihng new?
[11:14] <cachio> failover
[11:14] <cachio> mvo, it was failing since some weeks
[11:15] <cachio> sporadically
[11:15] <mup> PR snapd#6279 opened: interfaces: tweak deny-auto-connect policy tests <Created by mvo5> <https://github.com/snapcore/snapd/pull/6279>
[11:16] <cachio> mvo, 2.36.2 is stable
[11:17] <cachio> running smoke test now
[11:18] <pstolowski> mvo: hey, will you find some time for review 1 or 2 of my hotplug PRs?
[11:21] <mvo> pstolowski: I hope so
[11:21] <mvo> pstolowski: there is some more going on (some core18 work and prepareing 2.37) but I will put this on my list
[11:30] <pstolowski> mvo: thanks
[11:30] <mup> PR # closed: core-build#11, core-build#22, core-build#26, core-build#37
[11:31] <mup> PR # opened: core-build#11, core-build#22, core-build#26, core-build#37
[11:31] <zyga> brb
[11:31] <pstolowski> mvo: fyi, it's #6100 and #6114
[11:31] <mup> PR #6100: overlord/ifacestate: hotplug-remove-slot task handler <Hotplug 🔌> <Created by stolowski> <https://github.com/snapcore/snapd/pull/6100>
[11:31] <mup> PR #6114: overlord/ifacestate: handler for hotplug-disconnect task <Hotplug 🔌> <Created by stolowski> <https://github.com/snapcore/snapd/pull/6114>
[11:32] <zyga> mvo: https://github.com/snapcore/snapd/pull/6279/files is broken
[11:32] <mup> PR #6279: interfaces: tweak deny-auto-connect policy tests <Created by mvo5> <https://github.com/snapcore/snapd/pull/6279>
[11:32] <mvo> zyga: uh, sorry, looking
[11:33] <zyga> does it pass for you locally
[11:33] <zyga> unit tests
[11:40] <Wimpress> mvo Chipaca We had an adhoc update from zyga last week about the status of the fontconfg cache fixes. What is the ETA for that landing in stable?
[11:42] <mvo> zyga: silly me, I will fix the issue
[11:43] <mvo> Wimpress: all validations are done and core is ready, cachio  will do the release once he gets green light from the store
[11:43] <cachio> mvo, I already did the release
[11:44] <mvo> cachio: \o/
[11:44] <mvo> Wimpress: ^- here is your answer :)
[11:44] <popey> did 2.36.2 *just* hit stable?
[11:45] <cachio> popey, yes
[11:46] <popey> ok, I was confused. just updated and looked at wikipedia which said it was released last week
[11:48] <zyga> mvo: ah, FYI we learned that the fixes don't work on fedora
[11:48] <zyga> mvo: mborzecki has the details
[11:48] <cachio> 12:48, 29 November 2018‎ Herakleitoszefesu (talk | contribs)‎ m . . (6,865 bytes) +316‎ . . (Version 2.36.2; infobox formatting improvement) (undo | thank) Tag: 2017 wikitext editor
[11:49] <cachio> popey, I updated the release 2.36.1, then on 11/29 there was another update
[11:49] <popey> \o/ I love me some fresh updates
[11:50] <cachio> popey, I don't know who did it
[11:50] <popey> I usually do, glad someone else is :)
[11:50] <mvo> zyga: uh, that is sad
[11:50] <mvo> mborzecki: can you fill me in with the details what is missing on fedora?
[11:51] <zyga> mvo: fedora has cache in /usr/share/something
[11:51] <zyga> but I'll let you draw your own conclusions
[11:51] <mborzecki> mvo: aah yes, fedora has fc cache in different location, /usr/lib/fontconfig/cache iirc
[11:51] <mvo> mborzecki: woah, that is a strange location for a cache. very unfortunate as well :(
[11:51] <mborzecki> mvo: heh :P
[11:52] <zyga> mvo: note that the impact on strict and classic snaps is different
[11:52] <zyga> and some classic snaps also differ in impact
[11:53] <zyga> depending on how they are made
[11:53] <mborzecki> mvo: yeah, it's unfortunate, afaik it's only fedora (and rhel probably), arch uses /var/cache, zyga can tell something aboue opensuse, but iirc it's /var/cache too
[11:53] <zyga> tnere
[11:54] <zyga> there's no /usr/lib/fontconfig on opensuse for sure
[11:57] <zyga> pstolowski: replied to your questions on opensuse PR
[11:57] <pstolowski> thx
[12:00] <zyga> pstolowski: with the binary options we can also estimate the number of configurations that we need to support
[12:00] <mvo> zyga, mborzecki: I wonder what we can do, could we play tricks in snap-confine  ? i guess that won't help with clasic confned snaps
[12:00] <zyga> mvo: my opinion is as follows:
[12:00] <mvo> zyga, mborzecki or will a relocatable format v7+uuid help?
[12:00] <zyga> mvo: the issue affects graphical snaps made on top of fedora29 base, our fc cache work doesn't help there
[12:00] <zyga> mvo: strict snaps based on core and core18 are not affected
[12:01] <mvo> zyga: aha, good point
[12:01] <zyga> mvo: but our extra cache may be seen as undesired, we could look at hiding it
[12:01] <zyga> mvo: the issue also affects some classic snaps
[12:01] <zyga> mvo: classic snaps that link with host fontconfig will not be affected by negative performance as cache will be populated by the host mechanism, they will also use the right cache, wherever that might may be
[12:02] <zyga> mvo: we MAY consider a system where where the native package with snapd has the equivalent of your cache mechanism
[12:02] <zyga> that always links to the native libraries
[12:02] <zyga> for the purpose of triggering that cache refresh
[12:02] <zyga> mvo: classic snaps that link to core snap will remain affected
[12:02] <zyga> mvo: but they will benefit from your mechanism
[12:02] <zyga> mvo: to make sure we fully improve the situation I would do the following:
[12:03] <zyga> (some of which are probably optional)
[12:03] <zyga> mvo: 1) we should run different cache mechanism for classic snaps and different for strict snaps
[12:03] <zyga> mvo: 2) for classic snaps we should run the host provided cache and the snapd provided cache
[12:03] <zyga> mvo: 3) the snapd provided cache *should* move to the base snap instead
[12:04] <zyga> mvo: and we should run the one matching the base snap of the classic snap being operated on
[12:04] <zyga> mvo: this would fix all the issues
[12:04] <zyga> mvo: let me know what you think
[12:04] <mvo> zyga: yeah, that sounds sensible
[12:04] <mborzecki> zyga: sgtm
[12:04] <zyga> I especially think 3 is important
[12:04] <zyga> since it means we can deprecate old cache and grow new ones
[12:05] <zyga> and solve the hypothetical f29 based apps in the same go
[12:05] <zyga> I would say that we may make it generic enough that snapd doesn't know it's fonts
[12:05] <zyga> maybe /meta/hooks/snap-installed
[12:05] <zyga> and then that does whatever is needed
[12:05] <zyga> it would be special because base snap hooks may run unconfined
[12:05] <zyga> but base snaps are privileged already
[12:06] <zyga> so I think this is reasonable, it is the same mechanism you implemented but associated with the correct entity
[12:25] <mup> PR snapd#6280 opened: cmd/snap: make 'snap warnings' output yamlish <Created by chipaca> <https://github.com/snapcore/snapd/pull/6280>
[12:41] <Son_Goku> zyga, I felt like garbage all weekend (and Simon Peter did not help...) but I did manage to look over your yak-shaving PR
[12:43] <zyga> and?
[12:46] <zyga> hmm
[12:46] <zyga> prepare error on opensuse https://www.irccloud.com/pastebin/crnFHL37/
[12:47] <zyga> some SNAFU
[12:54] <mup> PR core18#94 closed: hooks: add cloud-init <Created by mvo5> <Merged by sil2100> <https://github.com/snapcore/core18/pull/94>
[13:10] <mborzecki> ehh import cycles
[13:10] <mborzecki> refactoring selinux package, got a cycle snap -> dirs -> release -> selinux -> osutil -> dirs
[13:11] <mborzecki> off to pick up the kids
[13:49] <Son_Goku> zyga, I left feedback
[13:49] <zyga> thanks, I will chec
[13:49] <zyga> check*
[13:49] <Son_Goku> zyga, also, wtf is up with the opensuse golang compiler?
[13:49] <zyga> no idea
[13:49] <Son_Goku> isn't -std a normal flag?
[13:49] <zyga> not broken on opensuse
[13:50] <zyga> er
[13:50] <zyga> on tumbleweed
[13:50] <zyga> at least since I updated this morning
[14:17] <mup> PR snapcraft#2419 closed: project: state file path change <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2419>
[14:25] <ackk> hi, I'm having an issue with multipass on xenial: https://paste.ubuntu.com/p/7HrZTvBh3k/
[14:25] <ackk> it mentions incompatible openssl version
[14:29] <sergiusens> ackk: I pinged someone who can help you with that
[14:29] <sergiusens> mvo: we need to discuss the `.snapcraft` thing. Can you add the reasons for needing it to https://bugs.launchpad.net/snapcraft/+bug/1805219 ?
[14:29] <mup> Bug #1805219: .snapcraft <19.04> <19.04-external> <Snapcraft:Triaged> <https://launchpad.net/bugs/1805219>
[14:30] <sergiusens> mvo: I think I want to go with `snapcraft.yaml` at the root of the project and allowing a `.snapcraft` as the root for assets likes hooks, gui and such
[14:40] <ackk> sergiusens, thanks
[14:49] <Saviq> ackk: hey, while our snap is confined "classic" we might stumble upon such problems, but we're moving towards strict confinement very soon so those should go away
[14:50] <ackk> Saviq, does multipass currently only work on bionic?
[14:50] <ackk> (this is a xenial host)
[14:50] <Saviq> ackk: in any case, it should work on xenial, can you please file an issue here https://github.com/CanonicalLtd/multipass/issues/new and we'll try and fix asap
[14:53] <ackk> Saviq, https://github.com/CanonicalLtd/multipass/issues/518
[14:53] <Saviq> ackk: thank you!
[14:53] <ackk> Saviq, np
[15:04] <mvo> sergiusens: in a meeting, I opened the bug and have a look
[15:04] <dot-tobias> Hi alan_g , short question concerning mir-Kiosk: I‘m running the chromium-mir-Kiosk snap on mir-Kiosk. After mir-Kiosk gets refreshed, the browser snap does not get restarted automatically. This leaves my device (meant to be always-on) with a black screen until I manually restart the chromium snap. Is this a problem specific to the chromium snap (Xwayland) or in general? And can I do something abo
[15:04] <dot-tobias> ut it? Thanks!
[15:09]  * zyga -> quick context switch for taxes and dinner
[15:19] <ackk> Saviq, does multipass currently pick proxy options from the hosts' /etc/environment ?
[15:20] <ackk> Saviq, from the log I see it can't access cdimage.ubuntu.com, and this host has a proxy set
[15:23] <Saviq> ackk: it's a systemd service, so no, it doesn't see that environment, you have to `snap set multipass proxy.http …` and similarly for https
[15:23] <ackk> Saviq, ah I see, thanks
[15:23] <alan_g> dot-tobias, I'd imagine that's a problem with the chromium-mir-kiosk example. You do realise that's an example to work from, not a stable, supported snap?
[15:25] <ackk> Saviq, ah, so setting the proxy the daemon runs, but those opensssl errors are stil three
[15:26] <Saviq> ackk: yeah it won't be able to access any https resources most likely
[15:27] <ackk> Saviq, fwiw I have the same errors on my cosmic machine
[15:27] <dot-tobias> alan_g : Yes, I read that in the Ubuntu forums. Sorry to keep pestering you about that, it’s just I do not have a lot of understanding about the graphics stack and thus not the faintest idea where to start improving / integrating this into my snap … and regarding my question today, wanted to make sure it’s not a known issue with mir-Kiosk before I start sinking hours into debugging the chromium sn
[15:27] <dot-tobias> ap 😊 again, sorry to keep bothering you.
[15:27] <ackk> Saviq, multipass seems to be working though
[15:32] <Saviq> ackk: as long as it (multipass itself) doesn't need to access any https resources, it should work indeed
[16:05] <mup> PR snapd#6281 opened: interfaces/builtin: add Multipass interfaces <Created by gerboland> <https://github.com/snapcore/snapd/pull/6281>
[16:28]  * Chipaca loves that unplugging the headset now disables the trackpad
[16:28]  * Chipaca does not actually love it
[16:28]  * Chipaca needs to reboot
[16:30] <cachio> mvo, hey, is it any way to set the StartLimitInterval for a snap service?
[16:30] <okamis> Hello, I installed slack and ran it as root by mistake, how do I purge the configuration files?
[16:39] <Saviq> okamis: /root/snap/slack should be everything it saved
[16:40] <Saviq> or, if ran through sudo, it might be /home/your_user/snap/slack - sudo doesn't change $HOME normally
[16:41] <cachio> mborzecki, do you kbiw if it is any way to set the StartLimitInterval for a snap service?
[16:51] <Saviq> cachio: not according to https://docs.snapcraft.io/snapcraft-app-and-service-metadata/8335
[16:52] <mvo> cachio: I think not :/
[16:52] <mborzecki> cachio: afaik there's no way currently
[16:52] <cachio> mvo, ok, so I need to make it manually
[16:53] <cachio> mvo, i SEE https://paste.ubuntu.com/p/NdFRpYHHzP/
[16:53] <cachio> on boards
[16:54] <cachio> at least on pi3
[16:54] <mvo> cachio: what does journalctl -u  test-snapd-daemon-notify.notify say?
[16:54] <mborzecki> cachio: the service shouldn't fail, provided the interface is connected at this stage
[16:55] <cachio> mvo, I am executing it again
[16:56] <cachio> mborzecki, not sure if when it fails the interface is connected
[16:56] <cachio> because part of this test is with the interface diconnected
[16:56] <mup> PR snapcraft#2422 closed: clean: user friendly message when cleaning <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2422>
[16:57] <mborzecki> cachio: yup, there should be an echo before, or maybe extend debug to show snap interfaces?
[16:57] <cachio> when the test fails the interface is disconnected
[16:58] <cachio> I already check that
[16:58] <cachio> mborzecki, could that be affecting?
[16:59] <sergiusens> joc: hey, what does this mean? https://www.irccloud.com/pastebin/Nh31ajqw/
[17:01] <mborzecki> cachio: maybe, do you have a log from spread?
[17:02] <cachio> I have a debug session here
[17:02] <cachio> mborzecki, I just created it
[17:02] <cachio> mborzecki, what info could help?
[17:03] <cachio> mborzecki, this is the spread log
[17:03] <cachio> https://paste.ubuntu.com/p/dq7JgX7RmF/
[17:05] <cachio> mvo, external:ubuntu-core-16-arm-32 .../tests/main/interfaces-daemon-notify#  journalctl -u  test-snapd-daemon-notify.notify
[17:05] <cachio> -- No entries --
[17:06] <cachio> mvo, this could help
[17:06] <cachio> https://paste.ubuntu.com/p/CcmqqPsx34/
[17:06] <cachio> mvo, this shows the start-limit-hit
[17:11] <Chipaca> cachio: if a test is breaking a service and such, and it doesn't do reset-failed, it'll sometimes not start
[17:11] <Chipaca> not sure if that's what you're seeing though
[17:11] <Chipaca> cachio: but that's what i had to do with the nfs-support test
[17:12] <cachio> Chipaca, the test is disconnecting the interface and trying to start the service
[17:12] <cachio> and checking the log contains denials
[17:12] <cachio> but those denials don't appear so the test fail
[17:13] <cachio> Chipaca, and the problem is that we are hitting the start limit
[17:13] <Chipaca> cachio: right
[17:13] <cachio> and it is just happenning on core for arm
[17:14] <cachio> Chipaca, what do you mean with "breaking a service"?
[17:14] <Chipaca> cachio: what's stopping the service, in this case?
[17:16] <mborzecki> cachio: about that fedora 29 bug, i think we'll have to remote the kernels manually
[17:17] <cachio> mborzecki, ok
[17:17] <cachio> I'll do that
[17:18] <mborzecki> cachio: something like this:  `dnf autoremove -y $(rpm -qa kernel-core | sort -r | tail -1)`
[17:18] <cachio> Chipaca, the test stops the service
[17:19] <cachio> disconect -> stop -> loop with start
[17:19] <cachio> we check that snap logs contains denials
[17:19] <Chipaca> cachio: but
[17:20] <Chipaca> cachio: it seems the service is exiting with error after getting the permission denied
[17:20] <Chipaca> ah
[17:20] <Chipaca> cachio: the snap is buggy
[17:21] <Chipaca> cachio: the daemon says it's "simple", but it's not a daemon at all
[17:22] <cachio> Chipaca, this is the snap.yaml https://paste.ubuntu.com/p/NxtnkdYVjy/
[17:22] <Chipaca> yes i'm looking at it here
[17:22] <cachio> Chipaca, why it is not a daemon?
[17:22] <Chipaca> it says "daemon: simple"
[17:22] <Chipaca> cachio: because it just runs a command and exits?
[17:22] <cachio> Chipaca, ahh, ok
[17:23] <Chipaca> cachio: and
[17:23] <Chipaca> cachio: a shell script exits with the exit status of the last command it executed
[17:23] <Chipaca> cachio: which means that this thing exits with error
[17:23] <Chipaca> so systemd tries to restart it a few times, and then gives up
[17:23] <Chipaca> so the test is a race between systemd restating the thing, and spread running the test
[17:25] <Chipaca> cachio: easiest fix, probably, is to add a "true" after the systemd-notify call in the script :-), and (optionally? but probably best) set "daemon: oneshot"
[17:25] <cachio> Chipaca, so we should make sure we exit 0
[17:25] <cachio> I'll try with oneshot
[17:26] <Chipaca> k
[17:26] <cachio> Chipaca, thanks
[17:26] <Chipaca> cachio: let me know how it goes
[17:44] <cachio> Chipaca, one shot does not work
[17:44] <cachio> I think I made it work
[17:45] <cachio> oneshot fails to start
[17:45] <cachio> because the interface is not connected
[17:45] <cachio> so it exits with status 1
[17:45] <Chipaca> cachio: you made the script not exit with error first?
[17:45] <cachio> Chipaca, no
[17:45] <Chipaca> cachio: you did the optional thing, and not the non-optional thing
[17:45] <Chipaca> :-)
[17:45] <cachio> I just installed and connected to the interface
[17:46] <cachio> together
[17:46] <cachio> because between the snap is installed in prepare and the interface is connected during the execution
[17:46] <cachio> systemd is retrying the service
[17:47] <cachio> Chipaca, what do you suggest'
[17:47] <cachio> ?
[17:48] <Chipaca> cachio: add an '|| true' to the systemd-notify call, or a 'exit 0' after it or something
[17:51] <cachio> Chipaca, 0
[17:51] <cachio> ok
[17:51]  * Chipaca 1
[18:04] <cachio> Chipaca, well this also works well
[18:04] <cachio> I'll create the PR
[18:08] <roadmr> sergiusens or kyleN : what's the expected Ubuntu version to host snapcraft development? (kind of a trick question - I tried bionic but some of the deps don't exist as noted in the docs, so I went down to xenial) Is it xenial?
[18:10] <mup> PR snapd#6282 opened: tests: force test-snapd-daemon-notify exit 0 when the interface is not connected <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/6282>
[18:33] <sergiusens> roadmr: it is xenial, given away by the debian/changelog still there and the lack of a base in snapcraft.yaml 😉
[18:34] <roadmr> sergiusens: nice - so how do you guys get black (which requires python 3.6) to run on xenial (which has python 3.5)?
[18:34] <roadmr> I disabled the black portion of ./runtests.sh for now, am just curious, this is not blocking me or anyting
[18:34] <sergiusens> roadmr: `snap install black --edge --devmode`
[18:35] <roadmr> sergiusens: ah, perfect :) thanks!
[18:35] <roadmr> having two ways to install stuff is confusing. Hopefully soon there'l be only one :D
[18:35] <sergiusens> I intend to make all our devtools a single snap to bootstrap faster, but haven't gotten around to it yet
[18:35] <roadmr> sergiusens: it didn't take me a long time to bootstrap in any case, just black was baffling me
[18:37] <sergiusens> roadmr: yeah, but imagine not needing to ask me which dev environment is the expected one and have a snap with the interpreter, the required dependencies and tools 😉
[18:37] <roadmr> sergiusens: \o/ I like that future heh
[22:27] <mup> PR snapcraft#2423 opened: Do not use `bash` package name in staging <Created by jdahlin> <https://github.com/snapcore/snapcraft/pull/2423>
[22:27] <jdahlin> ^ we found some issues related to the `bash` package name already being registered on staging