[05:09] <mborzecki> morning
[07:03] <zyga> Good morning
[07:04] <zyga> mvo: no apparmor changes in that window would cause that. For now this is unknown, perhaps other parts of the kernel did change
[07:07] <mvo> zyga: hm, hm
[07:08] <mvo> zyga: thank you
[07:09] <mborzecki> zyga: mvo: hey
[07:09] <mborzecki> zyga: something fishy going on in #5566
[07:11] <mvo> mborzecki: hey
[07:16] <zyga> I need to prepare breakfast for my daughter first
[07:16] <zyga> mvo: also the stop signal test had one more bug!
[07:16] <zyga> I sent a PR but perhaps not fully correct
[07:17] <mvo> zyga: ok
[07:17] <mvo> zyga: woah, yet another bug :(
[07:22] <Chipaca> in other news, people keep on using 'disable' and finding bugs
[07:22] <Chipaca> :-)
[07:23] <mvo> Chipaca: thanks for tackling them!
[07:24] <Chipaca> mvo: :-)
[07:24] <Chipaca> I fixed them and no tests broke
[07:24] <zyga> ok, ttyl, really need to make that bfast
[07:24] <Chipaca> so, er, need to write tests :-)
[07:24] <mvo> Chipaca: /o\
[07:24]  * mvo hugs Chipaca 
[07:25] <Chipaca> anyway, off to the gym before the day gets melty
[07:25] <Chipaca> ttfn
[07:25] <mvo> good plan! ttfn
[08:12] <pedronis> Chipaca: reviewed the snapshotstate PR, looks good overall
[08:15] <mvo> pedronis: I updated 5563 to add more checks
[08:18] <pedronis> mvo: so the bit of bad new is that so far we tried to not import snap into asserts
[08:18] <pedronis> (because asserts is used in places that are not snapd)
[08:22] <mvo> pedronis: ok, I can revert that part and just parse manually
[08:22] <mvo> pedronis: its not that much its needed for
[08:23] <pedronis> but we will have the problem going forward
[08:23] <mvo> zyga: OMG 5560 is green
[08:24] <mvo> pedronis: either way is fine with me, for this particular case its easy enough to do the checks without importing the channel parser
[08:24] <pedronis> mvo: that would be easier, I think if we need the struct later we can make a subpackage of snap
[08:25] <mborzecki> pedronis: pushed some updates to #5452, switching between this and #5561 makes it a bit like brain surgery unfortunately
[08:25] <mvo> pedronis: ok, I will undo the import and just parse the relevant bits by hand
[08:29] <pedronis> mborzecki: I'm a bit confused,  5561 is not based on 5452 ?
[08:30] <mborzecki> pedronis: no there are sort of in parallel
[08:30] <pedronis> mborzecki: I'm not sure I'm up to that
[08:30] <pedronis> it sounds confusing to me
[08:30] <mborzecki> pedronis: otherwise the diff would be much larger
[08:32] <mborzecki> pedronis: i suppose i can merge master into 5452 and rebase 5561 on top of it if it makes it easier to review
[08:33] <pedronis> I don't know
[08:33] <pedronis> I'm just getting confused by some of the last comments in 5452
[08:36] <zyga> rere, bfast and housework done, let's hack
[08:36] <mvo> pedronis: this is updated now
[08:37] <zyga> mvo: see, the world is not on fire ;)
[08:37] <zyga> mvo: approved
[08:37] <zyga> mvo: I need to focus on image factory, I spoke with upstream developers about my plans and got some super useful advice
[08:38] <mvo> zyga: nice
[08:38] <mborzecki> pedronis: which ones? i'll clear it up
[08:38] <zyga> mvo: as for https://github.com/snapcore/snapd/pull/5564
[08:39] <zyga> mvo: we need some before/after
[08:39] <mvo> zyga: what does before/after mean?
[08:40] <mvo> zyga: also what is the link the forum topic about the apparmor issue again? sorry, I misplaced it
[08:41] <mvo> zyga: found it, nevermind
[08:41] <zyga> no worries, it is
[08:41] <zyga> https://forum.snapcraft.io/t/apparmor-profile-caching/1268/17
[08:41] <zyga> before / after as in "without this patch and with this patch"
[08:42] <zyga> jamie wanted to see the cost
[08:42] <zyga> TBH based on jamie's question I would say the boot performance is exactly identical
[08:42] <zyga> because without core refresh the system key is in sync
[08:42] <zyga> and that means that startup is totally identical
[08:42] <pedronis> mborzecki: I answered,  it seems you did the change in the follow up but it sounded like you didn't, but a bit unclear why you cannot do it here first
[08:42] <mborzecki> pedronis: i've merged master to 5452 and rebased #5561 on top (force pushed there too)
[08:44] <pedronis> mborzecki: I'm talking about  https://github.com/snapcore/snapd/pull/5561/files#diff-147f53d4ad040ca82e13d36e9fdd4e18R145
[08:45] <zyga> mvo: so, I don't know, I think we should reboot the pi with stable kernel/core
[08:45] <zyga> use systemd's boot analyzer to just measure the tiem
[08:46] <zyga> do this 3-5 times and get some numbers out
[08:46] <zyga> then apply this patch
[08:46] <zyga> and do the same
[08:47] <zyga> but as I said, since the patch doesn't change anything in the case when system key is stable
[08:47] <zyga> I don't expect to see any difference
[08:48] <pedronis> mborzecki: the best thing would be to get Chipaca to reivew #5452 today
[08:48] <mborzecki> pedronis: will ping him
[08:49] <mborzecki> pedronis: see your response now now, so you're saying f.snap() is like the store then? so with this instance key should be added in the caller rather than inside
[08:49] <pedronis> yes
[08:49] <pedronis> that's just my mental model
[08:49] <pedronis> but that's where I'm coming from
[08:50] <pedronis> also because snapSpec has a Name field atm
[08:50] <pedronis> at least
[08:50] <mborzecki> pedronis: got slightly confused as there's snapSpec coming in but snap.Info coming out
[08:50] <pedronis> mborzecki: we had store.SnapSpec at some point
[08:50] <pedronis> mborzecki: actually we still do
[08:50] <pedronis> that's why it would be good to keep it working similarly
[08:51] <pedronis> mborzecki: fakeStore.snap corresponds to store.SnapInfo
[08:51] <pedronis> to some extent
[08:51] <mborzecki> pedronis: i'm quite sure i replaced snapSpec with store.SnapSpec at some point and then dropped that change
[08:51] <pedronis> we might change that at some point
[08:51] <pedronis> but we haven't
[08:51] <pedronis> it would be good to be somewhat consistent
[08:51] <pedronis> it's all already all a bit confusing as it is :)
[08:52] <mborzecki> pedronis: makes sense now, thanks for clearing it up
[08:52] <pedronis> mborzecki: also for clarity  we had code in snapstate at some point that used SnapInfo and then snap was used to fake SnapInfo
[08:53] <pedronis> we don't anymore, but we might later
[08:53] <pedronis> (hopefully not)
[08:53] <pedronis> anyway just to give more context
[08:54] <Chipaca> pedronis: thanks for the review!
[08:54] <zyga> hey Chipaca
[08:54] <zyga> how have you been?
[08:54] <Chipaca> zyga: 'sup
[08:54] <Chipaca> zyga: hot :-)
[08:54] <zyga> have the streets melted into canals of asphalt yet?
[08:54] <zyga> yes, it's hot
[08:55] <mborzecki> pedronis: i'll update 5452 then and leave 5561 hanging there for a while until we land the store part first
[08:56] <mborzecki> zyga: did it rain at your place yesterday?
[08:56] <zyga> mborzecki: not a drop of water
[08:56] <zyga> I really want some now
[08:56] <zyga> *except not when the moon thing happens
[08:56] <zyga> that would suck
[08:56] <mborzecki> zyga: it rained here during the night, but then the morning was south east asian style, you more twice and you're all sweaty
[08:57] <zyga> yummy
[08:57] <zyga> why take a shower when you can just get out of bed
[08:58] <Chipaca> brb (reboot)
[08:59] <pedronis> mborzecki: btw   this also means we should double check the places in api.go that use Store.SnapInfo they should always use a snap-name,  if we start from an instance name we need to split it, might it's alright right
[09:01] <pedronis> mborzecki: I'm switching to something else that needs a bit of wrapping up for a bit, I will get back to reviews in the afternoon
[09:03] <mborzecki> pedronis: sure, thanks for the help
[09:15] <ogra> mvo, did you consider to rename the pi kernel to just be pi-kernel instead of pi2-kernel with the switch to 4.15 ? (i think this is probably the best time to do it and the versioning in the na is completely pointless )
[09:15] <ogra> *s/na/name/
[09:17] <mvo> ogra: can you hop into #stable-kernel to see if that is much work for them?
[09:17] <ogra> on freenode ?
[09:17]  * zyga agrees with mvo and ogra
[09:18] <zyga> pi-kernel is so much better with tracks
[09:18] <zyga> it'd be only better if we could call it "IOT kernel"
[09:18] <ogra> with everything
[09:18] <zyga> and it would work on all the boards at once -)
[09:18] <zyga> haha, right
[09:18] <ogra> haha
[09:19] <mvo> ogra: we also need sign-off by niemeyer if we want to rename pi2-kernel to pi-kernel for core18. but I think this is pretty uncontroversial
[09:19] <ogra> yeah, it was pi2 only for probably 6 months since it exists
[09:19] <zyga> yeah, it's super nice
[09:19] <zyga> ogra: btw, I saw that pi3 has gotten much more aarch64 friendly?
[09:20] <zyga> ogra: is it the moment where pi could be either armv7 or aarch64 in our images? (that both arches work)
[09:20] <ogra> and toigether with a generalized gadget that runs on all pi'S you can then build an image (and model assertion) a lot easier
[09:21] <ogra> zyga, it cant "get more aarch64 freindly" until it has actual ram to make use of aarch64 :P
[09:21] <zyga> yeah but stuff and ponies and PRs
[09:21] <ogra> aarch64 on 1G is extremely wasteful
[09:21] <ogra> and you really dont benefit from anything 64bit on it
[09:22] <ogra> unless you do big math computations or some such ...
[09:22] <ogra> ... but for that you are lacking RAM again :)
[09:23] <ogra> currently all binaries allocate about 1.5x the RAM ... the same binarides, simply built for arm64 ... so even running the idle core image will bump the ram footprint from 40 to 60MB
[09:24] <zyga> ogra: yeah but it would mean people can use inexpensive pi to play with aarch64 on ubuntu
[09:24] <zyga> now they need to find something more exotic
[09:24] <zyga> or just use arch/fedora
[09:25] <ogra> well, i dont mind if they try out OOM on arch or fedora and we dont get bad press :P
[09:25] <mvo> zyga, mborzecki, pedronis there will be a snapd 2.34.3 to fix the apparmor cache problem - anything you want to have backported that is a) low-risk b) high-impact?
[09:25] <zyga> mvo: easter eggs that play yankie-doodle are not in that set
[09:25] <zyga> mvo: I think that's all for now
[09:25]  * ogra admits he is exaerating ... just a little :)
[09:26] <ogra> *exaggerating
[09:26] <zyga> brb
[09:26] <t1mp> can I open a shell into a snap container? For debugging
[09:27] <mborzecki> mvo: nothing new, just the nvidia thing which is already 2.34 branch
[09:27] <mvo> mborzecki: ta
[09:27] <ogra> t1mp, snap run --shell <snapname>.<appname>
[09:27] <t1mp> ogra: great, thanks! I'll try it.
[09:27] <ogra> t1mp, for any installed snap
[09:29] <zyga> t1mp: note that this will drop you into a confined shell
[09:29] <zyga> t1mp: there's also a way to run an unconfined shell if you have sudo on your device
[09:32] <t1mp> my device is my laptop :) I'm packaging a desktop app.
[09:33] <t1mp> hmm, I'm a bit confused. The shell it gives me has the homedir in /home/tim/snap/qmenta-app/x37 but I don't have, for example, /bin/desktop-launch which I need
[09:34] <zyga> t1mp: the home directory is not as relevant perhaps, the big thing is that /bin/desktop-launch exists on your machine but not in the snap container
[09:34] <zyga> t1mp: what does desktop-launch do?
[09:35] <ogra> desktop-launch comes from a desktop helper
[09:35] <zyga> aha
[09:35] <zyga> then it is probably in $SNAP/bin/desktop-launch
[09:35] <ogra> your snapcraft.yaml needs to define some [after] statement to get it
[09:35] <zyga> since /bin is the /bin directory from the core snap, not from your application snap
[09:35] <ogra> it should be in your PATH by default
[09:35] <ogra> (if the snap includes it that is)
[09:36] <t1mp> right. desktop-launch is indeed there, but $SNAP/... is not in my PATH
[09:36] <t1mp> tim@tim-XPS-13-9350:~$ snap run --shell qmenta-app
[09:36] <t1mp> To run a command as administrator (user "root"), use "sudo <command>".
[09:36] <t1mp> See "man sudo_root" for details.
[09:36] <t1mp> tim@tim-XPS-13-9350:/home/tim$ echo $SNAP
[09:36] <t1mp> /snap/qmenta-app/x37
[09:36] <t1mp> tim@tim-XPS-13-9350:/home/tim$ echo $PATH
[09:36] <t1mp> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
[09:36] <zyga> ogra: that's not exactly accurate
[09:36] <zyga> the PATH is changed by per-app wrappers for now
[09:37] <zyga> so if you run --shell you get a shell but not the wrapers
[09:37] <zyga> look at $SNAP/ and at the wrappers there
[09:37] <zyga> and see what they do
[09:37] <ogra> ah
[09:37] <zyga> this will be fixed with the incoming work around snapcraft templates and layers
[09:37] <zyga> sorry, not layers
[09:37] <zyga> there is some new term for that
[09:37] <ogra> layovers :P
[09:38] <zyga> but essentially snapd will know about the sandwiched helpers
[09:38] <t1mp> so how do I change my / now to $SNAP inside the snap shell. I need that so that python will be able to find the python libs that are installed in the snap
[09:39] <zyga> t1mp: just 'cd $PYTHON'
[09:39] <zyga> er
[09:39] <ogra> zyga, btw, do we have an ETA foe layouts ? (i have a bunch of packages that would benefit from being able to  provide /opt/vc on Rpi)
[09:39] <zyga> cd $SNAP
[09:39] <zyga> ogra: next cycle for sure, sorry about the lag
[09:39] <ogra> *for
[09:39] <t1mp> python looks directly in /lib/python3.5/site-packages/ if there is no PYTHONPATH set
[09:39] <zyga> t1mp: yeah, you can set PYTHONPATH in environment: section in your snapcraft.yaml
[09:40] <ogra> zyga, well, its fine for me, its just awkward having to ask jamie for manual approval for each upload
[09:40] <zyga> I believe that is per-app so you can customize this
[09:40] <zyga> and it will be picked up by snap run --shell as well
[09:40] <t1mp> in this case, I want to execute 'desktop-launch python3 -m my-lib.my-app', and it automatically reads the lib from /lib/python3.5/site-packages/my-lib (no need for PYTHONPATH if it is in that directory)
[09:41] <ogra> butu it wont be in that directory :)
[09:41] <ogra> *but
[09:41] <ogra> since that directory is in your core snap ... which is most likely not shipping "my-lib" :)
[09:42] <t1mp> right, it is in $SNAP/lib/python3.5/...
[09:42] <ogra> so your PYTHONPATH needs to point to $SNAP/...
[09:42] <ogra> right
[09:42] <t1mp> I did that now.
[09:42] <t1mp> ImportError: libxcb-dri3.so.0: cannot open shared object file: No such file or directory
[09:42] <t1mp> so there are a bunch of other env vars to set... I suspect a whole bunch, before it works from the shell.
[09:43] <t1mp> (just running the snap works fine)
[09:43] <ogra> ... and your LD:LIBRARY_PATH needs to point to the right dirs too ...
[09:43] <ogra> typically done by the wrapper
[09:43] <t1mp> somehow that is already working for me when I run the snap. Or does it chroot to $SNAP or something like that?
[09:43] <zyga> or in the environment section (more future proof, less shell to run)
[09:43] <zyga> t1mp: the snap uses a bunch of  wrappers from snapcraft
[09:43] <zyga> those are not active in --shell
[09:43] <ogra> thats the bit that zyga referred top above ... if you use --shell, the wrappers arent executed
[09:44] <ogra> s/top/to/
[09:44] <t1mp> ah, right. command-qmenta-app.wrapper works
[09:44] <t1mp> in $SNAP
[10:06] <t1mp> which version of Ubuntu does the Snap use inside the images? (lsb_release is not installed in it)
[10:07] <t1mp> it has python 3.5, and my app was tested as working with python 3.6
[10:08] <ogra> xenial
[10:09] <t1mp> which xenial? 16.04.1? I have 16.04.5 on my system and it has a newer python than the snap
[10:16] <thresh> how do I go about restricting the number of snaps saved in /var/lib/snapd/snaps?  I probably only need the latest one +1.
[10:17] <thresh> no fun having three libreoffice snaps each 500meg
[10:17] <t1mp> oh, right, the system has python35 (my py36 was in a virtualenv)
[10:17] <Chipaca> thresh: that's a feature that's in 2.34
[10:18] <Chipaca> thresh: snap set system refresh.retain=2
[10:19] <Chipaca> thresh: meanwhile, snap list --all thesnap, and snap remove --revision=revno thesnap
[10:20] <zyga> thresh: you can get it early by refreshing to another channel
[10:21] <pedronis> Chipaca: the comment about "snapshots" name is not super constructive I know,  maybe Gustavo will have input about that, it might just be fine and a matter of habit,  they can be interpreted as  collections or namespaces those top state entries
[10:22] <thresh> thanks Chipaca, zyga
[10:22] <thresh> trying candidate core now
[10:22] <zyga> :-)
[10:22] <Chipaca> pedronis: https://github.com/snapcore/snapd/pull/5187#discussion_r196223469
[10:22]  * zyga is super happy about what snaps can do
[10:22] <thresh> ya
[10:23] <thresh> I guess the changes will kick in (as in actually removing the file) on the next snapped package update?
[10:23] <Chipaca> still wanting to add ‘snap remove --disabled’
[10:23] <Chipaca> thresh: yeah
[10:23] <thresh> makes total sense, thanks!
[10:24] <Chipaca> thresh: you  could hurry it along by doing a 'snap refresh --revision=<an old revision you have> thesnap' and then a 'snap refresh thesnap'
[10:25] <Chipaca> although at that point 'snap remove --revision' is probably quicker :-) but if you want to check it works, you can do the above
[10:30] <zyga> Chipaca: can you +1 and merge https://github.com/snapcore/snapd/pull/5566 please
[10:30] <zyga> one less flaky test
[10:37] <Chipaca> zyga: that was a tough review
[10:37] <zyga> I know
[10:37] <Chipaca> i think i need a break
[10:37] <zyga> haha
[10:37]  * zyga hugs Chipaca 
[10:37] <Chipaca> maybe some ice cream
[10:37] <zyga> though a bit too hot for that
[10:37] <zyga> I was thinking
[10:37] <zyga> can we install a c-n-f handler
[10:37] <zyga> and fail tests if it fired
[10:37] <Chipaca> yeah, hug me but from a meter away dude
[10:37] <Chipaca> things are sticky
[10:37] <zyga> would catch things like tpyo || true
[10:37] <zyga> icky sticky
[10:38] <zyga> believe me, I don't know where to go to have less heat
[10:38] <Chipaca> zyga: Córdoba, Argentina
[10:38] <Chipaca> zyga: (cachio said it was <0C yesterday)
[10:38] <zyga> is there winter there?
[10:38] <zyga> hmm hmm
[10:38] <zyga> that's settled then
[10:38] <zyga> bye!
[10:38] <Chipaca> also winter is dry season
[10:39] <Chipaca> on the other hand, the president just authorized the army to intervene for "internal security"
[10:39] <Chipaca> so … maybe stay away for a bit
[10:42]  * zyga looks at an oldish python codebase 
[10:42] <zyga> with iffy bits here and there
[10:43] <zyga> but docs make no sense
[10:43] <zyga> so deep dive required
[10:43] <Chipaca> zyga: you get all the fun
[10:44] <zyga> it depends if upstream is happy to take patches
[10:44] <zyga> it's the kind of code that makes you ask "python was about style?" questions
[10:44] <zyga> definitely written by a C coder
[10:44] <zyga> if(stuff): ..
[10:45] <zyga> also try: ... except: print "drat"
[10:45] <zyga> this enterprise vibe
[10:46] <zyga> also, no tests
[10:46] <Chipaca> zyga: “I'm sorry zyga the tests are in another castle^Wrepo”
[10:46] <zyga> hahaha
[10:49] <zyga> also no __future__ imports anywhere
[10:49] <zyga> la la la
[10:49] <zyga> python 2.6 required
[11:20] <zyga> la la la
[11:20] <zyga> it's so hot I cannot think
[11:28] <Chipaca> zyga: find a fox in the woods, and use it as a hat
[11:28] <Chipaca> zyga: you will then no longer be worried about the heat
[11:28] <zyga> have I told you the story of the peeing bunny?
[11:28] <Chipaca> zyga: if you don't have foxes, a brace of ravens will do
[11:29] <Chipaca> anything that will try to gouge your eyes out really
[11:29] <Chipaca> zyga: … no
[11:33] <Chipaca> zyga: I'm going to have some lunch. No bunnies though.
[11:37] <mvo> 5555 needs a second review, easy win
[11:37] <mvo> (and a nice number!)
[11:37] <zyga> with a number like that
[11:37] <zyga> who can resist
[11:49] <mborzecki> Chipaca: bunnies for lunch?
[11:50] <mvo> 5562 is also an easy win
[12:00] <mvo> cachio: could you please test the latest pi2-kernel and dragonboard kernel on edge when you have a free slot? we have an initrd update there and once its good we can move it up to candidate/stable
[12:03] <Chipaca> mborzecki: I haven't sourced bunnies, no
[12:05] <cachio> mvo, is there any plan for beta today?
[12:06] <mvo> cachio: yes, probably after the standup
[12:06] <cachio> mvo, nice
[12:27] <zyga> back from lunch
[12:27] <zyga> and back to image factory
[12:27] <zyga> mvo: how is core18, are we green?
[12:29] <cachio> mvo, niemeyer I have to take my son to the doctor, I'll try to be for standup
[12:29] <zyga> cachio: ack
[12:29] <zyga> mvo: kernel is green, is stuff safe-ish for 1st?
[12:30] <cachio> mvo, tests runnign for db and pi2 with edge kernels
[12:30] <zyga> mvo: is the current release (.3) also the one that will enable c18?
[12:31] <zyga> mvo: or is that for 2.35?
[12:37] <ogra> zyga, hmm... would it be possible to have a layouts entry the re-maps $SNAP_USER_DATA to /home or is that too recursive to work ?
[12:37] <zyga> yes, but not yet
[12:37] <zyga> it's on the roadmap for this cycle
[12:37] <zyga> I'll get it done
[12:38] <ogra> (i'm wordering if i could make an openbox-session snap with a handfull of defult apps to run on top of mir-kiosk with XWayland to run a desktop on core
[12:38] <ogra> )
[12:38] <zyga> let's sync in 3 weeks after my holidays and flock
[12:39] <ogra> you would indeed only e able to operate inside confinement so the re-mapping should make it possible to use dotfiles in home in that case
[12:40] <ogra> ... without having to tinker a lot with serach paths for configs etc in the binaries
[12:45] <mborzecki> heh, managed to break tmux by resizing gnome-terminal :(
[12:50] <Chipaca> tea? why yes
[12:52] <mborzecki> nah, coffee, 3rd one today and still sleepy
[12:56] <Chipaca> mborzecki: at this point I think sleep won
[12:56] <thresh> hmm
[12:58] <mvo> zyga: c18 is 2.35, 2.34.3 is just to unblock us
[12:58] <thresh> is it just me having issues with firefox? http://thre.sh/stuff/ff-crash.txt
[12:58] <Chipaca> kenvandine: ^ ?
[12:59] <zyga> mvo: ack
[13:32]  * Chipaca hugs mvo 
[13:33]  * Chipaca sells mvo a universal random number generator
[13:33] <mvo> Chipaca: hahaha
[13:33]  * mvo hugs Chipaca 
[13:35] <mvo> Chipaca: I have enough of random numbers for this week
[13:35] <pedronis> mborzecki: are you going to merge #5452 and then update #5561 ?
[13:35] <Chipaca> mvo: but this one comes with a yellow duck, and a plane ticket for four to canarias
[13:35] <Chipaca> but ok, i'll throw it away
[13:35]  * Chipaca throwws it away
[13:36] <mborzecki> pedronis: merging right now
[13:36] <juliank> mvo: Here's a joke wishlist bug from debconf for you to amuse: https://bugs.launchpad.net/ubuntu/+source/vrms/+bug/1783986
[13:36] <Chipaca> niemeyer: pedronis: so, about snapshots' state entry, currently it's {"snapshots": {"last-set-id": 42}}
[13:37] <Chipaca> juliank: clearly there needs to be a vrms snap
[13:37] <juliank> There were rumours about a flatpak snap
[13:38] <juliank> I'm also still waiting for the apt snap
[13:38] <zyga> Chipaca: what would vrms say when invoked form a snap?
[13:38] <Chipaca> juliank: was the flatpak snap distributed as an appimage
[13:38] <juliank> Chipaca: Hmm, could be
[13:38] <mvo> juliank: heh! I like that
[13:39] <ogra> a classic apt snap should actually be trivial :)
[13:39] <Chipaca> zyga: “starting microsoft office 2019...”
[13:39] <juliank> I'd do one on core18
[13:39] <ogra> (wouldnt work on ubuntu core sadly)
[13:39] <juliank> current core needs to many backports
[13:41] <niemeyer> Chipaca: I guess the downside of that state entry is that if we ever decide to have a per-snapshot state, this would be the obvious key
[13:42] <pedronis> niemeyer: that was my remark as well
[13:42] <Chipaca> niemeyer: I think that is pedronis's point
[13:42] <niemeyer> Ah, I didn't see that
[13:42] <Chipaca> niemeyer: pedronis: I could do the simplest thing, and have it be a toplevel "last-snapshot-set-id"
[13:42]  * cachio back
[13:42] <Chipaca> cachio: kid ok?
[13:43] <cachio> Chipaca, with fever
[13:43] <Chipaca> cachio: aw
[13:43] <cachio> 39°
[13:43] <cachio> Chipaca, as usual seek on weekends
[13:44] <cachio> it is a virus
[13:44] <mvo> cachio: uh, good luck
[13:44] <pedronis> Chipaca: it would work for me, we do have toplevel ones from snapstate for example
[13:44] <niemeyer> Chipaca, pedronis: Conceptually okay.. it's just a mouthful.. let me grep a bit to see what else we've got
[13:44] <Chipaca> k
[13:44] <cachio> Chipaca, mvo I got a call from the kinder garden telling me he was with fever, so I took him the doc
[13:44] <pedronis> we have last-refresh and last-refresh-hints
[13:45] <Chipaca> cachio: good luck
[13:45]  * niemeyer finds "ubuntu-core-transition-last-retry-time" :)
[13:45] <mvo> cachio: yeah, I read, all the best that he gets well quickly
[13:45] <cachio> Chipaca, mvo tx
[13:46] <cachio> mvo, db and pi2 so far so good
[13:46] <mvo> cachio: great, thanks
[13:46] <cachio> running about 60 tests without any error
[13:46] <cachio> using edge kernels
[13:46] <Chipaca> niemeyer: "once-upon-a-time-a-snapshot-set-id-decided-they-wanted-to-know-what-lay-beyond-the-dark-forest"
[13:47] <ogra> beavers ?
[13:47] <niemeyer> Chipaca: Cool, sounds fine
[13:49] <niemeyer> cachio: Aw.. sucks.. take your time if you need to take care of him
[13:50] <Chipaca> ogra: https://www.youtube.com/watch?v=ZqH4rc0E1fc
[13:50] <ogra> lol
[13:51] <mborzecki> pedronis: and 5561 is updated now
[13:53] <cachio> niemeyer, tx, he is sleeping now
[13:54] <zyga> Chipaca: LOL
[13:54] <pedronis> mvo: the things you added in snap/channel.go in #5563 ar not used anymore/yet ?
[13:56] <mvo> pedronis: yeah, I can kill those off again, I left it mostly because we talked about that we might want to allow snap install foo=edge bar=stable but YAGNI and all that (easy enough to add again when needed)
[13:56] <pedronis> mvo: that seems preferable
[13:56] <pedronis> but yes keep the code around
[13:56] <mvo> pedronis: sure, let me do that
[14:01] <mvo> pedronis: I removed the relevant commit
[14:10] <mvo> zyga: did you see the latest comment from jamie about skipCache when loading snap-confine?
[14:10] <zyga> nope
[14:10] <zyga> looking
[14:11] <zyga> mvo: ah, nice
[14:20] <pedronis> mvo: I think we do need the test you removed in some form, unless I'm confused
[14:22] <mvo> pedronis: let me double check which got removed
[14:30] <mvo> pedronis: you mean the tests in image ? I can add them back they will fail on model assertion assmbly time already though
[14:30] <mvo> pedronis: or am I missing something?
[14:31] <pedronis> mvo: I don't you have  a test  where   there's  "kernel: foo"  without track now
[14:31] <pedronis> you have either kernel with track
[14:31] <pedronis> or not kernel at all
[14:32] <pedronis> I mean in asserts
[14:32] <pedronis> not image
[14:32] <pedronis> * I don't think
[14:33] <pedronis> mvo: making sense?
[14:34] <pedronis> mborzecki: I'll try to give a look at 5561,  let's see how far I get
[14:35] <mvo> pedronis: indeed, thank you, let me add this one
[14:41] <mvo> pedronis: updated
[14:41] <t1mp> how long does the automated review of a new snap package normally take?
[14:43] <Chipaca> t1mp: seconds
[14:43] <pedronis> mborzecki: Chipaca: btw I was thinking that maybe in a follow up we should rename though they are called "instance-key" on the wire the various JSON InstanceKey in store,  it's a bit confusing that we have Info.InstanceKey and those  but they don't have the same value
[14:44] <t1mp> Chipaca: thanks. It was actually minutes for me. Maybe just the first upload.
[14:48] <Chipaca> t1mp: ah, maybe if it's a biggun
[14:48] <Chipaca> pedronis: agreed
[14:48]  * Chipaca falling asleep, takes a break
[14:51] <mvo> niemeyer, cachio good news, MATCH is fixed - #5539 no longer fails. I will close this PR now
[14:52] <niemeyer> \o/
[14:53] <cachio> mvo, great news
[14:53] <cachio> mvo, thanks for the fix
[14:54] <mvo> cachio: yeah, good news indeed - my pleasure
[14:56] <t1mp> Chipaca: 216 MB. It includes a full Qt
[15:00] <mvo> 5563 needs a second review, should be easy
[15:18] <pedronis> mborzecki: I did a first pass on #5561,  I saw some issues
[15:19] <pedronis> afaict
[15:34]  * pedronis calls it a week, will be around on monday tough
[15:34] <Chipaca> mborzecki: where does the "10" come from in mon-wed,fri,9:00-11:00/2 -> Monday to Wednesday and on Friday, twice between 9:00 and 11:10 ?
[15:34] <pedronis> niemeyer: safe travels and move!
[15:34] <Chipaca> pedronis: have a good one
[15:34] <pedronis> thx
[15:34] <niemeyer> pedronis: Thanks! Have a good rest there too
[15:38] <mborzecki> Chipaca: that's discourse emojis, 💯 makes it particularly hard to write those times
[15:38] <mvo> pedronis: yeah, have a good weekend, thanks for the reivews!
[15:38] <Chipaca> mborzecki: doesn't the backtick stop that from happening?
[15:38] <t1mp> I'm running a test and build pipeline for my app inside a Docker image on Jenkins... Does it make sense to use 'snap cleanbuild' there then? The docker image should already be clean.
[15:39] <mborzecki> Chipaca: nope
[15:39] <mborzecki> pedronis: thanks for the review!
[15:39] <Chipaca> t1mp: is the docker image on the same libc as your base?
[15:40] <t1mp> the base is always Ubuntu 16.04?
[15:40] <Chipaca> t1mp: unless you requested a different one, yes
[15:40] <t1mp> I'm using python:3 as the docker base image. So chances are that libc is not the same. Possibly I have to change the docker image to an ubuntu one.
[15:41] <t1mp> ah, I didn't know you can choose the base image
[15:41] <mborzecki> cachio: regarding https://github.com/snapcore/snapd/pull/5552#discussion_r205799622 iirc storage: .. does not work at particular system level, i recall spread complaining about that
[15:41] <Chipaca> t1mp: only 16.04 is supported right now, but more are emerging and should be supported soon
[15:42] <Chipaca> t1mp: supported does not mean works (and viceversa) :-)
[15:42] <t1mp> 16.04 is fine for me now
[15:43] <cachio> mborzecki, ok
[15:43] <cachio> it could be a problem inthe future
[15:43] <mborzecki> cachio: this is what I get https://paste.ubuntu.com/p/yGQq5P9QT4/
[15:45] <cachio> mborzecki, let me review spread and try that
[15:45] <cachio> mborzecki, it should work
[15:46] <mborzecki> cachio: maybe i'm missing something or misplaced it
[15:51] <cachio> mborzecki, well, storage is not defined at system level
[15:51] <cachio> that's why it doesn't work
[15:51] <cachio> you can define it just at backend level
[15:52] <mborzecki> cachio: yeah, we could probably fix it though, but that's a pr to spread
[15:52] <cachio> mborzecki, so, we can go with it but we have to know that it could be a problem in the future
[15:52] <cachio> I'll create a pr for spread with this change
[15:52] <cachio> but it will take a time to land
[15:53] <cachio> so lets go with the storage defined at backend level
[15:53] <mborzecki> cachio: ok
[15:54]  * cachio lunch
[16:16] <zyga> jdstrand: FYI: https://github.com/snapcore/snapd/pull/5564#discussion_r205823848
[16:23] <kyrofa> niemeyer, I'm not sure how up-to-speed your team is on https://github.com/snapcore/snapd/pull/5569, but I linked the forum proposal in there as well. Do you want to take a look before you head out?
[16:24] <niemeyer> kyrofa: Sure, will have a look
[16:45] <Chipaca> I think I'm heading out
[16:46] <mvo> Chipaca: have a great weekend
[16:46] <Chipaca> where "heading out" means "getting a beer" becaue the sky is tumbling onto our heads
[16:47] <Chipaca> mvo: you too! also, go
[16:47] <Chipaca> mvo: i mean: you too, get out of here :-)
[16:47] <Chipaca> mvo: but also, have a great weekend
[16:47] <mvo> Chipaca: heh, very soon, just one upload
[16:47] <Chipaca> mvo: i'll allow it
[17:17] <zyga> jdstrand: https://github.com/snapcore/snapd/pull/5564#issuecomment-408483112
[17:17] <zyga> mvo: merge it!
[17:17] <zyga> jdstrand: tl;dr; its good :)
[17:21] <jdstrand> nice :)
[17:29] <mvo> cachio: 2.34.3 will be ready in ~1h, ppa is building as we speak
[18:18] <zyga> Everyone: remember about the eclipse today
[18:19] <zyga> :-)
[18:19] <zyga> It starts very soon and will take several hours
[18:19] <zyga> Going through various phases
[18:20] <Chipaca> zyga: of course the sky is now overcast for the first time in weeks
[18:20] <Chipaca> not complaining mind you, the houses aren't built for 30C+ weather here
[18:22] <zyga> Chipaca: I’ll send annoyingly nice photos
[18:22] <Chipaca> zyga: ok
[18:22] <Chipaca> zyga: I'll take out your internet
[18:22] <zyga> UK houses are built for being perpetually wet, no?
[18:22] <Chipaca> deal with 15C like champs
[18:23] <zyga> By drinking grog
[18:23] <Chipaca> you don't need to turn on the heating until temps are <10C
[18:23] <Chipaca> (outside i mean)
[18:23] <Chipaca> but in none of the houses i've rented so far has there been a way to ventilate the top 20cm of a room for ex
[18:24] <Chipaca> so the heat just lurks there (and in the whole attic!)
[18:25] <Chipaca> anyway, enjoy the eclipse :-)
[18:25] <Chipaca> i'll enjoy the coolth
[18:25] <Chipaca> (first time in weeks i'm not having dinner on the deck though)
[18:27] <Chipaca> o/ eow
[18:27] <mvo> cachio: 2.34.3 is ready in beta
[18:28] <cachio> mvo, great
[18:28] <zyga> Thank you guys!
[18:28] <cachio> I'll start
[18:28] <mvo> cwayne: 2.34.3 is ready in beta :)
[18:28] <mvo> cachio: thank you!
[18:28] <zyga> ogra: try the beta on your pi
[18:28] <zyga> :-)
[19:00] <mvo> oh joy! uevent_test.go fails on s390x
[19:00] <mvo> invalid data offset
[19:00] <mvo> oh boy
[19:00] <zyga> Uh
[19:00] <zyga> Can you just rete
[19:09] <zyga> I meant to say “retry”
[19:10] <mvo> zyga: its failing for some time
[19:10] <mvo> zyga: I think there is something wrong
[19:10] <mvo> zyga: anyway, will dig monday
[20:11] <ogra> zyga, "the beta" ?
[20:12] <ogra> oh, of snapd ....
[20:12] <ogra> will do onthe WE
[20:39] <zyga> :)
[22:29] <ffejj> howdy folks... i have a snap application with a lot of *.desktop files in its common/app-data/applications directory-  how can i set that directory where the ubuntu mate desktop menu will see it ?