[03:13] <mup> PR snapd#6721 opened: tests: new profiler snap used to track cpu and memory for snapd and snap commands <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/6721>
[06:43] <zyga> Hello
[07:00]  * zyga was watching the news about Paris last night 
[07:00] <zyga> a bit sleepy, sorry
[07:06] <mvo> zyga: it looks like the selinux-clean test is unhappy (in master and in the recent PR spread runs). is anyone on it or shall we disable it for now?
[07:09] <zyga> mvo: mborzecki is on it
[07:09] <zyga> we talked about it a lot yesterday
[07:10] <zyga> essentially it keeps finding bugs
[07:13] <mvo> ok
[07:14] <zyga> mvo: there's a fun bug in the kernel and in apparmor breaking disco
[07:14] <zyga> mvo: but apparently only in lxd
[07:14] <zyga> mvo: the security team was on it last evening
[07:14] <pedronis> disco ships on Thu, fun
[07:15] <zyga> yes
[07:16] <zyga> everyone is well aware, lsm stacking landed
[07:16] <zyga> lxd started using shiftfs
[07:16] <zyga> this confused apparmor parser caching
[07:16] <zyga> and no profiles got loaded
[07:16] <pstolowski> mornings
[07:16] <zyga> hey pawel
[07:17] <mvo> pstolowski: good morning
[07:17] <mvo> zyga: woah, sounds like fun indeed
[07:27] <mup> PR snapd#6722 opened: tests: set selinux-clean test to manual for now <Created by mvo5> <https://github.com/snapcore/snapd/pull/6722>
[07:34] <mvo> woah, now travis fails in the static tests even oh boy
[07:35] <mup> PR snapd#6673 closed: cmd,tests: forcibly discard mount namespace when bases change <Created by zyga> <Closed by zyga> <https://github.com/snapcore/snapd/pull/6673>
[07:36] <zyga> oh fun
[07:37] <zyga> mvo: did go change in travis?
[07:38] <mup> PR snapd#6723 opened: cmd/snap-confine: remove unused sc_open_snap_{update,discard}_ns <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6723>
[07:38] <zyga> pstolowski, mvo:  ^ trivial
[07:38] <pstolowski> done
[07:45] <mvo> zyga: you got it as well
[07:45] <zyga> thank you
[07:45] <zyga> aaah
[07:45] <zyga> I see
[07:45] <zyga> the go version fun
[07:46] <mvo> super mysterious as we did not change anything there did we?
[07:47]  * mvo looks
[07:48] <mvo> this looks like a travis issue, we request go1.9
[07:48] <mvo> maybe they dropped it?
[07:49] <mborzecki> morning
[07:49] <mvo> hey mborzecki
[07:50] <mborzecki> mvo: hey
[07:51] <mborzecki> 56 PRs open, better than yday
[07:51] <mvo> mborzecki: yeah, its getting better except master is not happy
[07:52] <mborzecki> mvo: what's the problem with master?
[07:52] <mvo> mborzecki: but we are working on it :) some things could land once this is unbroken
[07:52] <mvo> mborzecki: the selinux-clean test is unhappy more often than not
[07:52] <mvo> mborzecki: also static checks are complaining right now
[07:52] <mborzecki> mvo: heh
[07:52] <mup> PR snapd#6724 opened: travis: fix requested go version <⛔ Blocked> <Created by mvo5> <https://github.com/snapcore/snapd/pull/6724>
[07:52] <mborzecki> mvo: #6718 should help a bit with selinux clean test
[07:52] <mup> PR #6718: spread, tests: do not leave mislabeled files in restorecon test, attempt to catch similar files <SELinux> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/6718>
[07:52] <mvo> mborzecki: static checks have a version mismatch and die very early
[07:53] <mvo> mborzecki: aha, nice, is that green?
[07:53] <mborzecki> mvo: and yesterday i noticed that snapd started calling runuser
[07:53] <mborzecki> is that automatic snapshotting?
[07:53] <pedronis> mborzecki: I think so
[07:53] <mvo> mborzecki: 6718 ironically fails in selinux-clean
[07:53] <pedronis> Chipaca probably knows more about that (runuser)
[07:54] <mborzecki> mvo: yeah, looked at it yday evening and iirc it was because of runuser
[07:54] <mvo> aha, ok
[07:55] <mborzecki> flag provided but not defined: -V, hmm
[07:56] <mup> PR snapd#6724 closed: travis: fix requested go version <⛔ Blocked> <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/6724>
[07:57] <mborzecki> conspiracy theories in the forum
[08:01] <mvo> it looks like version mismatch - go tool asm -V does indeed not exist in 1.9
[08:01] <mvo> so it looks like go vet is driving it the wrong way (or something is)
[08:01]  * mvo has a meeting now so won't look at this
[08:03] <mborzecki> mvo: where do we get vet from?
[08:03] <mvo> mborzecki: I don't know
[08:04] <mborzecki> mvo: go tool vet is part of golang distribution package, and afaik vet is just a frontend, presumably both should be from the same distro package
[08:07] <Chipaca> runuserwha?
[08:07] <Chipaca> g'morning
[08:07] <Chipaca> mborzecki: what's up with runuser?
[08:07] <mborzecki> Chipaca: morning, runuser, we use it to snapshot user's data right?
[08:08] <Chipaca> mborzecki: yes (and hopefully any user data manipulation someday)
[08:08] <Chipaca> mborzecki: why?
[08:09] <mborzecki> Chipaca: cool, we need to extend the selinux policy to allow some actions it does (setgid, writing to audit and so on)
[08:10] <Chipaca> pedronis: starting on coherence, do you have a link to the server-side to hand?
[08:10] <mborzecki> fwiw, the changes look trivial, i should have a PR up soon
[08:10] <pedronis> Chipaca: one sec
[08:10] <Chipaca> mborzecki: i guess we only saw this now because of automatic snapshots?
[08:11] <mborzecki> Chipaca: yes, that would be my guess, wonder why it didn't come up in the travis job of the PR that added automatic snapshots
[08:12] <mborzecki> well, maybe the PR did not include the test back when it was opened
[08:25] <zyga>  re
[08:25] <zyga> sorry, had to clean the office a little
[08:31] <pedronis> Chipaca: sorry, need to have a quick errands, I can give you links after (in ~30 mins)
[08:31] <Chipaca> pedronis: no probs
[08:39] <mup> PR snapd#6725 opened: travis: add some debug to run-checks <Created by mvo5> <https://github.com/snapcore/snapd/pull/6725>
[08:45] <mborzecki> why on earth we use /home/gopath and since it's under /home we treat it like another homedir
[08:46] <mborzecki> but since it's not a homedir (there's no gopath user), none of the selinux transitions take place
[08:46] <mvo> I think I found the issue
[08:46] <mvo> with the status check
[08:46] <mvo> oh well
[08:46] <mvo> I wonder why this ever worked
[08:47] <zyga> mvo: what did you find?
[08:49] <mvo> zyga: PR up in 60s, then it will be obvious
[08:50] <zyga>  thank you :)
[08:52] <mup> PR snapd#6725 closed: travis: add some debug to run-checks <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/6725>
[08:52] <mup> PR snapd#6726 opened: tests: do not hardcode go1.10 in travis <Created by mvo5> <https://github.com/snapcore/snapd/pull/6726>
[08:52] <mvo> zyga: -^
[08:52]  * mvo takes a short break
[08:52] <zyga> looking
[08:53] <zyga> interesting
[08:53] <zyga> mvo: there was a simliar bug in suse
[08:53] <zyga> that is, suse golang stack got updated during startup
[08:53] <zyga> but the environment variables were pointing to the old stack
[08:53] <zyga> with similar insane errors
[09:06] <mborzecki> policy update for runuser is up
[09:06] <mup> PR snapd#6727 opened: data/selinux: allow snapd to execute runuser under snappy_t <SELinux> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/6727>
[09:26] <ilyaigpetrov> Hi. I'm new to Ubuntu Core and I want to boot from it from a usb pendrive without using any device other than my notebook (so I have no device to SSH from) -- what is the easiest way to do this? I don't have VTx support on my CPU and wouldn't prefer using a virtual machine, partly because I have an idea of using ubuntu core as my main desktop system (browser and  a terminal is all I need from it).
[09:32] <mvo> mborzecki: with 6727 can we get rid of 6722?
[09:33] <zyga> ilyaigpetrov: hey
[09:33] <zyga> ilyaigpetrov: I think core is not quire suited for that use case yet
[09:33] <mborzecki> mvo: yes
[09:33] <zyga> ilyaigpetrov: it is mainly usable as virtual machines in the cloud and single-purpose devices in the field
[09:33] <ilyaigpetrov> zyga: I want to learn new things this way
[09:33] <zyga> ilyaigpetrov: support for users and sessions is limited
[09:33] <zyga> ilyaigpetrov: you won't get a graphics session or a browser easily either
[09:34] <zyga> ilyaigpetrov: if you want to learn you can try getting the amd64 ubuntu core image and copy it to a USB drive
[09:34] <zyga> ilyaigpetrov: then instruct your device to boot from it
[09:34] <mborzecki> mvo: #6726 will probably fail on fedora/centos due to selinux, we should merge it anyway
[09:34] <mup> PR #6726: tests: do not hardcode go1.10 in travis <⚠ Critical> <Created by mvo5> <https://github.com/snapcore/snapd/pull/6726>
[09:34] <zyga> ilyaigpetrov: it will work, it's just not a device that one would use for daily stuff IMO
[09:35] <zyga> mborzecki: selinux question, when are semicolons required?
[09:35] <ilyaigpetrov> zyga: yes, I boot from the usb pendrive, enter my ubuntu SSO and it says I need to ssh into it, but I don't have any other notebook to log in via ssh from
[09:35] <zyga> sorry, that's the only way in
[09:35] <zyga> once you ssh you can set a password
[09:35] <ilyaigpetrov> zyga: I think to create a box based on raspberry Pi for kids to learn computers and coding, I want them being able to log in
[09:36] <ilyaigpetrov> zyga: is there any image customization I can do?
[09:36] <mborzecki> zyga: allow <foo> rules require it at the end, interfaces have a bunch of allow rules, each should end with ; already
[09:36] <zyga> ilyaigpetrov: I commend your desire to learn but I don't think core is the best use for that yet, for learing there are much better suited (especially for children) tailored distributions with graphical displays and keyboard / mouse support
[09:37] <zyga> ilyaigpetrov: what kind of customization?
[09:37] <mvo> mborzecki: indeed, so how about I combine 6726 and 6722 and then master should be green again. then we combine your selinux fixes and run it ~10 times or so and if all is green there we enable selinux-clean again? sounds reasonable?
[09:37] <ilyaigpetrov> zyga: replace config launcher on getty (I guess it's called getty)
[09:37] <zyga> ilyaigpetrov: no, that's not something you can do easily
[09:37] <zyga> ilyaigpetrov: and it will be undone by the system on the next update
[09:38] <ilyaigpetrov> *sigh* so sad
[09:38] <zyga> ilyaigpetrov: note that the user has no password
[09:38] <zyga> ilyaigpetrov: you must login via ssh first
[09:38] <zyga> ilyaigpetrov: then you can login interactively on another tty
[09:38] <zyga> (tty1 is special, rest should be regular)
[09:38] <zyga> ilyaigpetrov: core is designed for single use devices without users really
[09:38] <zyga> ilyaigpetrov: you don't expect each streetlight to have an user account, this is what core is aiming at
[09:39] <ilyaigpetrov> zyga: can I install a basic wayland compositor (or a mir server) and from another snap to install a firefox browser -- will they work together?
[09:39] <mborzecki> mvo: sounds good, then we can land 6727 and 6718
[09:40] <ilyaigpetrov> I'm not sure I understand how desktop snap is used by other snaps
[09:40] <mvo> mborzecki: cool, let me prepare things
[09:40]  * zyga quick breakfast
[09:40] <zyga> ilyaigpetrov: there are no snaps that support user sessions on a core system
[09:41] <ilyaigpetrov> zyga: mm, but I have seen egmde confined snap
[09:41] <ilyaigpetrov> https://snapcraft.io/egmde-confined-desktop
[09:41] <zyga> I don’t know about that
[09:41] <mvo> some of my branches need a second review: 6418 (might be interessting for zyga), 6599 and 6603 would be great. also 6627. all remodel related but relatively small and self-contained. *please* :)
[09:42] <zyga> mvo: gladly!
[09:42] <zyga> In 15 minutes
[09:42] <ilyaigpetrov> zyga: thanks for you help, bond appetite
[09:42] <zyga> ilyaigpetrov: you can try core in qemu
[09:42] <zyga> On i386 you don’t need hardware support
[09:43] <ilyaigpetrov> zyga: I really like the idea of using core as my main system, even if virtual tty is all I have with a single user
[09:46] <zyga>  ilyaigpetrov you need a 2nd machine then
[09:47] <popey> ilyaigpetrov: i have a laptop which is running Ubuntu core. It's a touch limiting for normal use.
[09:50] <ilyaigpetrov> popey: I used to use gentoo confining myself to using vttys only for learning purposes, and I learn how to run a single window of a browser on naked xorg server, I think it was useful
[09:50] <popey> It's certainly fun
[10:00] <zyga> back now
[10:00] <zyga> mvo: looking
[10:02] <zyga> mvo: note I will still address the snapd tools directory going stale
[10:02] <zyga> mvo: separately from this PR
[10:06] <zyga> mvo: https://github.com/snapcore/snapd/pull/6418#pullrequestreview-227099069
[10:06] <mup> PR #6418: many: allow core as a fallback for core16  <Created by mvo5> <https://github.com/snapcore/snapd/pull/6418>
[10:06] <zyga> mvo: it should be ok to just push the commit suggestion buttons a few times :)
[10:07] <zyga> mvo: doing another one
[10:08] <zyga> mvo: about 6599, should AddAll just add edges?
[10:08] <zyga> mvo: or fail if edges are present?
[10:09] <cwayne> sil2100: hey, is there anything in the latest core18 that may affect wifi?
[10:10] <zyga> mvo: https://github.com/snapcore/snapd/pull/6599#pullrequestreview-227102274
[10:10] <mup> PR #6599: snapstate,state: add TaskSet.AddAllWithEdges() and use in doUpdate <Created by mvo5> <https://github.com/snapcore/snapd/pull/6599>
[10:10] <pstolowski> zyga, mvo: or do extra iteration to check first?
[10:10] <zyga> hey cwayne, long time no see :)
[10:10] <cwayne> zyga: heya :) how's it goin?
[10:11] <zyga> cwayne: great, swamped under bugs and feature work but feeling positive today :)
[10:12] <cwayne> zyga: I'd rather be swamped than have nothing to do :)
[10:12] <zyga> cwayne: I think we are not at any risk of having nothing to do :)
[10:12] <cwayne> lol true!
[10:16] <sil2100> cwayne: hm, I'd have to dig deeper, but I don't think so
[10:16] <sil2100> We did release a new systemd yesterday, which is why a new core18 was triggered
[10:17] <cwayne> sil2100: ok, will poke on this end, seeing some wifi failures on Pi's which we hadnt seen in awhile
[10:18] <sil2100> Oh, hm
[10:18] <sil2100> cwayne: for a moment I was worried that someone released the new netplan package, but no, at least not for bionic
[10:19] <sil2100> And anyway, Matt said that he addressed the previous networking issue in the current netplan SRU anyway
[10:19] <cwayne> Yeah this isn't the same issue we saw earlier with netplan for sure
[10:19] <sil2100> Ok
[10:20] <zyga> mvo: https://github.com/snapcore/snapd/pull/6603#pullrequestreview-227104276
[10:20] <mup> PR #6603:  snapstate: add new NoReRefresh flag and use in Remodel() <Created by mvo5> <https://github.com/snapcore/snapd/pull/6603>
[10:21] <zyga> mvo: https://github.com/snapcore/snapd/pull/6627 has some unanswered questions
[10:21] <mup> PR #6627: devicestate: deal correctly with the "required" flag on Remodel <Created by mvo5> <https://github.com/snapcore/snapd/pull/6627>
[10:21] <zyga> doing a pass anyway
[10:22] <mvo> zyga: aha, ok, let me double check, maybe I missed something. thank you
[10:22] <sil2100> cwayne: the new systemd SRU we released did address some network bugs, so who knows, maybe there's some regression there
[10:22] <sil2100> cwayne: but the changes didn't seem highly likely to cause wlan-only issues
[10:23] <cwayne> sil2100: ack, well poke around on our end
[10:25] <mvo> zyga: sorry, was in a meeting I see you wrote more. will get back to that in a wee bit
[10:26] <zyga> mvo: no worries, I'm going through the last one you requested
[10:26] <mborzecki> mvo: https://api.travis-ci.org/v3/job/520673622/log.txt 6722 failed in canonical-livepatch test
[10:26] <mup> PR snapd#6728 opened: overlord/devicestate: extra measurements related to populateStateFromSeed <Created by stolowski> <https://github.com/snapcore/snapd/pull/6728>
[10:26] <pstolowski> uhmmm.. unhappy day for travis
[10:26] <mborzecki> mvo:  copied the log here: https://paste.ubuntu.com/p/QnVW7vCqJ6/ i'll restart the travis job
[10:31] <zyga> mvo: https://github.com/snapcore/snapd/pull/6627#pullrequestreview-227110498
[10:31] <mup> PR #6627: devicestate: deal correctly with the "required" flag on Remodel <Created by mvo5> <https://github.com/snapcore/snapd/pull/6627>
[10:31] <zyga> https://github.com/snapcore/snapd/pull/6726 is red
[10:32] <mup> PR #6726: tests: do not hardcode go1.10 in travis <⚠ Critical> <Created by mvo5> <https://github.com/snapcore/snapd/pull/6726>
[10:32] <mborzecki> zyga: yes, it'll land as 6722
[10:32] <zyga> ack
[10:33] <zyga> unless anyone has a review they want to pull me into, I will resume working on tests
[10:34] <mborzecki> hmm canonical-livepatch failed there too :/
[10:35] <zyga> yeah
[10:35] <zyga> one of those days, as they say
[10:35] <mvo> yeah, looking at this now
[10:35] <mvo> looks like something changed there as well
[10:37] <pstolowski> pedronis: re your question to https://forum.snapcraft.io/t/how-to-disconnect-a-snap-from-internet/10901/10 from yesterday - yes, we have a spread test for this - it's main/disable-autoconnect
[10:38] <pedronis> pstolowski: thx
[10:43] <mup> PR snapd#6729 opened: tests: update canonical-livepatch now that -gcp kernels are supported <Created by mvo5> <https://github.com/snapcore/snapd/pull/6729>
[10:45] <mup> PR snapd#6730 opened: tests: fix master <Created by mvo5> <https://github.com/snapcore/snapd/pull/6730>
[10:47] <mborzecki> mvo: looks like we need a one PR to unite all fixes
[10:48] <mvo> mborzecki: yeah, I added this in 6730
[10:48] <mvo> mborzecki: or is it missing something?
[10:49] <mvo> fwiw, I'm also looking at livepatch now, maybe we can make the needle we look for better
[11:08] <Chipaca> huh, store.RefreshCandidate still exists
[11:08]  * Chipaca nukes it
[11:15] <joc> sil2100: so re. the wifi failures you were talking to cwayne about earlier - nothing has changed in core18 but systemd?
[11:38] <mup> PR snapd#6729 closed: tests: update canonical-livepatch now that -gcp kernels are supported <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/6729>
[11:38] <mup> PR snapd#6730 closed: tests: fix master <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/6730>
[11:39]  * zyga hugs everyone who helped to fix master
[11:39] <mup> PR snapd#6722 closed: tests: set selinux-clean test to manual for now <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/6722>
[11:39] <mup> PR snapd#6726 closed: tests: do not hardcode go1.10 in travis <⚠ Critical> <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/6726>
[11:44] <zyga> mvo: so master is fixed now :)
[11:50] <rbasak> https://forum.snapcraft.io/c/release seems out of date. Where do relesae announcements go now?
[11:55] <zyga> rbasak: snapd releases are listed on https://github.com/snapcore/snapd/releases/
[11:56] <isomari_> greetings, how can I hide my ssid using snap wifi-ap?
[11:57] <rbasak> zyga: thanks. I was hoping for a summary of changes though. For example, that page doesn't say what happened in 2.38. I thought that's what the forum topic was for/
[11:57] <rbasak> ?
[11:57] <zyga> rbasak: it used to say that
[11:57] <zyga> rbasak: just not all releases are listed with equal verbosity
[11:57] <zyga> mvo: ^
[11:57] <pedronis> there is also https://forum.snapcraft.io/t/the-snapd-roadmap/1973
[11:58] <rbasak> The bugfix releases are all detailed, but I was wanting to know more about the high level stuff happening in feature releases.
[11:58] <rbasak> pedronis: ah that's useful - thanks!
[12:04] <Chipaca> isomari_: no idea. Are you sure you're in the right place to ask that?
[12:08] <mborzecki> anyone brave enough to do a 2nd review of https://github.com/snapcore/snapd/pull/6688 ? :)
[12:08] <mup> PR #6688: gadget: add validation of cross structure overlap and offset writes <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/6688>
[12:09] <mborzecki> involves familiarizing oneself with gadget.yaml and some hair pulling while reading the code :)
[12:12] <zyga> mborzecki: I can look but only after the standup, trying to wrap up a bigger chunk here
[12:12] <mborzecki> zyga: thanks!
[12:15] <cyphermox> cwayne: mvo: so what issue are we seeing now for core18, is it in any way netplan-related?
[12:18] <isomari_> Chipaca: Was asked to come here from ubuntu.
[12:20] <isomari_> Chipaca: I found the answer. Thanks
[12:27] <mup> PR snapd#6731 opened: overlord: make the store context composably backed by separate backends for device asserts/info etc <Created by pedronis> <https://github.com/snapcore/snapd/pull/6731>
[12:45] <pedronis> mborzecki: what's the status of master? needs 6727 ?
[12:46] <mborzecki> pedronis: master should be green, but selinux-clean test is disabled, 6727 enables the test and carries a fix for the policy
[12:46] <pedronis> ok, thx
[12:49] <mup> PR snapd#6704 closed: overlord/devicestate: measurements around ensure and related tasks <Created by stolowski> <Merged by stolowski> <https://github.com/snapcore/snapd/pull/6704>
[12:57] <mvo> rbasak: sorry, I have not updated for the coming 2.39 features yet. or do you need info about a much older release on the forum? what version are you looking for?
[12:58] <rbasak> mvo: nothing specific, thanks.
[13:29] <jdstrand> mvo: hey, sorry to bother you. what is the trick with either creating a debian/fedora qemu autopkgtest image (autopkgtest-build-qemu unstable debian-sid-64.img fails for me) or accessing google (no access to google:debian-sid-64:tests/main/...)
[13:29] <zyga> hey
[13:29] <zyga> jdstrand: for debian you can get the qemu cloud image they have
[13:29] <zyga> AFAIK it works out of the box
[13:29] <jdstrand> hey zyga :)
[13:29] <zyga> (they == debian)
[13:29] <zyga> the fedora one I don't recall
[13:29] <zyga> if you wait a little I may have some links for you
[13:29] <jdstrand> hmm, googled for it. /me keeps looking
[13:29] <mvo> jdstrand: you can ask gustavo for a google spread key
[13:30] <zyga> jdstrand: in theory there is https://spread.zygoon.pl/images/ but I don't keep it up-to-date
[13:30] <mvo> jdstrand: I don't know how to create fedora images, I suspect its also "just" downloading their cloud image and adjusting the login creds
[13:30] <zyga> jdstrand: ^ mvo's advice is really best
[13:30] <jdstrand> ack. I see in spread.yaml what to change them to. let me see what I can find
[13:31] <jdstrand> I thought I had a google spread key. where is that stored?
[13:31] <zyga> jdstrand: it's essentially this: run any cloud image with cloud-init inside to the point where you have shell, set passwords and you _might_ be ready
[13:31] <zyga> jdstrand: but because google images have customization applied we don't really know
[13:31] <zyga> jdstrand: it's in ~/.config/gcloud
[13:31]  * zyga afk for 15 minutes
[13:31] <jdstrand> I have stuff in that dir
[13:32]  * jdstrand looks for the images
[13:32] <jdstrand> thanks!
[13:32] <sergiusens> ogra: did you happen to look into wireguard on Ubuntu Core?
[13:33]  * jdstrand notes wireguard upstream still says not to use it in production
[13:36]  * jdstrand may just use zyga's images and upgrade
[13:36] <jdstrand> oh those are just ubuntu. I can create those fine
[13:38] <mup> PR snapd#6732 opened: tests: run livepatch on 18.04 as well <Created by mvo5> <https://github.com/snapcore/snapd/pull/6732>
[13:40] <ogra> sergiusens, nope
[13:42] <ogra> sergiusens, there are two snaps in the store touch
[13:42] <ogra> *though
[13:53] <zyga> re
[13:53] <zyga> sorry, I was grabbed into a family lunch
[13:54] <zyga> jdstrand: let me know if I can help
[13:54] <zyga> I can regen and upload fresh images
[13:54] <zyga> I think I can upload some more too, there's a 10GB quota on that directory
[14:15] <mup> PR snapd#6719 closed: many: move auth.AuthContext to store.DeviceAndAuthContext, the implemention to a separate storecontext package <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/6719>
[14:23]  * dot-tobias says hi
[14:30] <dot-tobias> is it possible to print output from hook scripts when they're running? I only get output if it fails, and then it's only the last ~5 lines
[14:34] <mup> PR snapd#6692 closed: interfaces: cleanup internal tool lookup in system-key <Simple 😃> <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/6692>
[14:39] <mborzecki> dot-tobias: redirect the output to some log file under $SNAP_COMMON?
[14:40] <zyga> or /tmp
[14:40] <zyga> though tmp is harder to find
[14:45]  * zyga reviews 6688
[14:46] <zyga> mborzecki: hey
[14:46] <zyga> mborzecki: remark about the gadget work
[14:46] <mborzecki> zyga: hm?
[14:46] <zyga> I think it would be great if you could add some docs , namely the key types Volume, VolumeStructure etc should be documented
[14:46] <zyga> they don't have to be long
[14:47] <zyga> I would put a paragraph or two in the file header, ahead of the docs of other stuff (perhaps package docs) for some quick context
[14:47] <zyga> then individual types can describe their role in the bigger picture
[14:49] <mborzecki> zyga: ok, i'll add something
[14:50] <mup> PR # closed: core-build#11, core-build#22, core-build#26, core-build#37
[14:51] <mup> PR # opened: core-build#11, core-build#22, core-build#26, core-build#37
[14:51] <pedronis> mvo: Chipaca: pstolowski:  store context refactoring has landed
[14:52] <pstolowski> pedronis: great, thx
[15:00] <Chipaca> pedronis: current status: https://pastebin.ubuntu.com/p/2TsZDK3wFZ/
[15:03] <pedronis> cool
[15:19] <cachio> zyga, hey, I see this error when fedora 29 is updated https://paste.ubuntu.com/p/rv9Kzh24m7/
[15:19] <cachio> zyga, any idea what could be causing this?
[15:21] <zyga> cachio: looking now
[15:21] <zyga> no idea, what does the unit do?
[15:21] <zyga> as in, what is systemctl cat man-db-cache-update
[15:22] <zyga> what does jurnald say about that unit?
[15:24] <cachio> zyga, I am regenerating the image to reproduce it because the image is dsicarded after that error
[15:24] <zyga> try to get an interactive shell
[15:24] <zyga> or expand the debug section to know more
[15:26] <cachio> zyga, sure, I am creating a new image to get an interactive shell
[15:52] <mup> PR snapd#6733 opened: state: add possible error return to TaskSet.Edge() <Created by mvo5> <https://github.com/snapcore/snapd/pull/6733>
[16:28] <cachio> zyga, https://paste.ubuntu.com/p/x9s3GtZJgp/
[16:34] <zyga> cachio: hey
[16:34] <zyga> cachio: what does the unit do?
[16:34] <zyga> can you provide the output of "systemctl cat"?
[16:35] <zyga> cachio: from the looks of the log systemctl cannot complete its task
[16:35] <cachio> https://paste.ubuntu.com/p/4swr5qVJKx/
[16:35] <zyga> perhaps our test suite reloading systemd is affecting other units
[16:35] <zyga> cachio: what about "man-db-cache-update service" ?
[16:35] <zyga> could you please cat that one?
[16:36] <cachio> https://paste.ubuntu.com/p/qTDggnMrtW/
[16:36] <zyga> pl
[16:36] <zyga> can you start that service?
[16:36] <zyga> does it fail?
[16:37] <cachio> if I start the image works well
[16:37] <cachio> if I start man-db-cache-update manually works well too
[16:37] <mup> PR snapcraft#2535 opened: build providers: get rid of attribute warnings from pylxd <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2535>
[16:37] <jdstrand> mvo, zyga: fyi, https://blog.strandboge.com/2019/04/16/cloud-images-qemu-cloud-init-and-snapd-spread-tests/
[16:37] <cachio> we are doing something as part of the prepare that is affecting
[16:38] <zyga> based on previous pastebin I would say that it gets interrupted by systemd restart but that's just my theory
[16:38] <zyga> jdstrand: looking
[16:38]  * jdstrand attempts fedora
[16:38] <zyga> jdstrand: nice
[16:38] <zyga> jdstrand: I will cron that on spread.zygoon.pl
[16:38] <zyga> thank you for sharing, this is very useful
[16:39] <jdstrand> np
[16:39] <jdstrand> there were a couple dots to connect with 'just get a cloud image' and 'adjust cloud-init' :)
[16:41] <zyga> jdstrand: indeed, I see you have mastered that
[16:41] <zyga> I was so lazy for too long :)
[16:41] <zyga> jdstrand: given your cloud-init data I could use one (shared) procedure for all systems that support cloud-init
[16:42] <zyga> (with some tweaks for individual systems to allow spread to boot them)
[16:42] <zyga> jdstrand: I have some local spread patches to enhance compatiblity
[16:42] <zyga> jdstrand: and to provide saner qemu command line
[16:43] <jdstrand> zyga: do note it is using whatever the default user is for the distro
[16:44] <jdstrand> there are lots of things cloud-init can do that I'm sure you know more about than I
[16:52] <jdstrand> cool, seems no special hoops for fedora
[17:03] <pedronis> mvo: I added a couple of comments to #6733
[17:03] <mup> PR #6733: state: add possible error return to TaskSet.Edge() <Created by mvo5> <https://github.com/snapcore/snapd/pull/6733>
[17:04] <cachio> zyga, this is interesting https://paste.ubuntu.com/p/GBQ4KDcQ6f/
[17:05] <zyga> cachio: what is dwz?
[17:06]  * zyga sees
[17:06] <zyga> cachio: I'm non the wiser, I think it is a real error but it is unclear if we are the cause
[17:06] <cachio> the part of the journal
[17:07] <cachio> zyga, agree
[17:07] <cachio> I'll go deep on this
[17:07] <cachio> thank
[17:07] <cachio> s
[17:08] <zyga> cachio: I'm sorry I'm not of much help, good luck
[17:08] <zyga> cachio: I'd be curious to see if a vanilla image has this issue
[17:09] <zyga> cachio: perhaps dwz crashed because it is confused by particular behaviour of the go linker
[17:09] <cachio> zyga, np, I'll try it after
[17:42] <mup> PR snapd#6718 closed: spread, tests: do not leave mislabeled files in restorecon test, attempt to catch similar files <SELinux> <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/6718>
[17:43] <mup> PR snapd#6727 closed: data/selinux: allow snapd to execute runuser under snappy_t <SELinux> <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/6727>
[18:23]  * zyga EODs
[18:32] <jdstrand> mvo, zyga: fyi, made some small updates to my blog post to accommodate fedora
[18:58]  * cachio afk
[19:13] <mvo> pedronis: I updated 6603 btw, hope all your comments are addressed
[21:20] <mup> PR snapcraft#2535 closed: build providers: get rid of attribute warnings from pylxd <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2535>
[21:26] <mup> PR snapcraft#2534 closed: Add SNAPCRAFT_PROJECT_DIR environment variable <Created by tonysimpson> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2534>
[22:31] <mup> PR snapd#6723 closed: cmd/snap-confine: remove unused sc_open_snap_{update,discard}_ns <Simple 😃> <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/6723>
[22:53] <mup> PR snapd#6734 opened: advise-snap: add --dump-db which dumps the command database <Created by shawnl> <https://github.com/snapcore/snapd/pull/6734>