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