[00:26] <blake_r> sergiusens: nvm figured it out
[06:14] <mborzecki> morning
[06:23] <zyga> Hi
[06:23] <zyga> Looking after kids
[06:24] <zyga> Will start in about an hour maybe
[06:24] <mborzecki> zyga: hey hey
[07:22] <mborzecki> #7702 needs reviews
[07:22] <mup> PR #7702: tests: adding fedora 31 to google-unstable backend <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/7702>
[07:40] <mborzecki> mvo: hey
[07:41] <mvo> hey mborzecki
[08:00] <pstolowski> mornings
[08:22] <mborzecki> pstolowski:  hey
[08:36] <zyga> back now
[08:36] <zyga> so
[08:36] <zyga> what shall I do
[08:37] <zyga> mvo: after Vancouver I will have 4 swap days: for last Friday, for next Monday which is a holiday and two more for travel
[08:37] <zyga> how will I ever use that :/
[08:40] <mvo> zyga: we will find a way
[08:41] <ogra> take 8 half days :P
[08:44] <mborzecki> zyga:  come to work on monday and start your weekend on tuesday
[10:43] <Saviq> cachio: hey, is there a focal image yet? could we have one, if not? :)
[10:44] <cachio> Saviq, hey, there is not one yet, let me take a look
[10:44] <Saviq> thanks :)
[10:44] <Saviq> cachio: would it be easy to have a -devel one, like LXD has, so we don't have to play catch-up after a release?
[10:47] <cachio> Saviq, there are few of them
[10:47] <cachio> I am testing one right now
[10:49]  * zyga is afk
[10:52] <Saviq> cachio: yeah, but I mean one that is *called* ubuntu-devel-64
[10:53] <Saviq> which is always what the latest devel image is :)
[10:53] <Saviq> s/is/would be/
[10:54] <cachio> Saviq, so, if you want to use the last image published the best way is
[10:54] <cachio> image: ubuntu-os-cloud-devel/ubuntu-2004-lts
[10:54] <Saviq> cachio: well, but that means for 2010 I'll have to change spread.yaml
[10:55] <Saviq> could there be one like ubuntu-os-cloud-devel/ubuntu-devel ?
[10:55] <Saviq> lxc has "ubuntu-daily:devel", which automagically points to the latest development release
[10:55] <cachio> the one I sent is the last of devel
[10:56] <Saviq> cachio: but it is explicit
[10:56] <Saviq> cachio: upon 2004 release
[10:56] <Saviq> that won't be the last of devel
[10:56] <cachio> when they publish a new one spread will take that last one
[10:56] <cachio> Saviq, currently there are 3
[10:56] <cachio> daily-ubuntu-2004-focal-v20191022                     ubuntu-os-cloud-devel  ubuntu-2004-lts                               READY
[10:56] <cachio> daily-ubuntu-2004-focal-v20191028                     ubuntu-os-cloud-devel  ubuntu-2004-lts                               READY
[10:56] <cachio> daily-ubuntu-2004-focal-v20191029                     ubuntu-os-cloud-devel  ubuntu-2004-lts                               READY
[10:56] <Saviq> cachio: I don't think you get what I mean :)
[10:57] <Saviq> I don't want to explicitly call out 2004
[10:57] <Saviq> just because that is current devel
[10:57] <cachio> Saviq, ahh
[10:58] <cachio> Saviq, the images are organized by release
[10:59] <cachio> Saviq, these are all the images https://paste.ubuntu.com/p/383XJfp3Ty/
[10:59] <Saviq> cachio: thanks, so there isn't a "devel" alias, meh :|
[10:59] <Saviq> we'll deal with that, thanks
[11:00] <cachio> Saviq, exactly
[11:00] <cachio> Saviq, once every 6 months you need to make the change in the spread.yaml
[11:01] <cachio> once 2004 is released you also need to update the image
[11:01] <cachio> Saviq, move from ubuntu-os-cloud-devel to ubuntu-os-cloud
[11:02] <cachio> Saviq, you could propose this "devel" image to the cloud team
[11:02] <cachio> Saviq, seems to be useful
[11:02] <cachio> for them it is just a name
[11:04] <Saviq> cachio: will do, now I realize it's them building those images :)
[11:05] <cachio> Saviq, :)
[11:49] <mborzecki> off to pick up the kids
[11:52] <mvo> mborzecki: I updated the TestRemodelSwitchCoreToBase test - this is passing now too, was incomplete simulation
[11:52] <mvo> mborzecki: in the remodel-switch-core-to-base PR
[11:53] <mvo> mborzecki: eh, s/PR/branch/
[12:15] <popey> mvo: Chipaca i have nothing for our meeting today.
[12:20] <mvo> popey: suits me, let's skip then
[12:34] <mborzecki> re
[12:34] <mborzecki> mvo: thanks!
[12:38] <sergiusens> blake_r: hey, sorry for not getting back to you, just getting started today
[12:50] <mborzecki> cachio: can you take a look at the changes in pushed to #7702 ?
[12:50] <mup> PR #7702: tests: adding fedora 31 <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/7702>
[12:51] <woutervb> Hi there, I posted a request to get an interface autoconnected some days ago (https://forum.snapcraft.io/t/autoconnect-juju-client-observe-for-cloud-status/14025) could I get some votes on this?
[13:06]  * Chipaca breaks a take
[13:11] <zyga> Chipaca break take # RPN
[13:44] <mborzecki> and my isp suck today
[13:58] <Chipaca> zyga: is the zygoon lab still a thing?
[13:58] <Chipaca> zyga: in particular wrt armhf and/or arm64
[13:59] <Chipaca> hmm
[13:59] <Chipaca> ogra: any chance your qemu-virgil could grow a "be a raspberry pi" command?
[14:00] <Chipaca> ogra: (I don't know how to get a working system from just qemu-virgil.arm :) )
[14:02] <zyga> Chipaca: it can be
[14:03] <zyga> Chipaca: but I turned everything off since I was not using it
[14:03] <zyga> Chipaca: but I can prepare the arm64 nvidia board
[14:03] <Chipaca> zyga: no worries, I'm trying the qemu approach now
[14:03] <zyga> Chipaca: it's pretty good
[14:03] <zyga> Chipaca: fast and lots of ram
[14:03] <Chipaca> zyga: qemu, or nvidia? :)
[14:03] <zyga> Chipaca: both :D
[14:03] <Chipaca> when/if i get more than a black screen in qemu i'll agree
[14:04] <zyga> Chipaca: let me know by EOD today please
[14:04] <Chipaca> zyga: sure
[14:04] <zyga> Chipaca: but no worries otherwise, I'll happily prepare it
[14:04] <zyga> it's a hw prep day anyway
[14:30] <ogra> Chipaca, i dont think it can run as Rpi ... it probably could run as beaglebone or begale XM ... properly implemented arm board in qemu are rare ... the best bet is always vexpress
[14:30] <ogra> *boards
[14:31] <ogra> but for vexpress we indeed have no core images
[14:32] <mborzecki> ijohnson: mvo: trying to find the bug about opening the urls from a slack snap, it was a similar problem, windows would get associated with the slack application, rather than an already open firefox instance
[14:32] <ogra> Chipaca, qemu-virgil.arm -machine help
[14:32] <mborzecki> ijohnson: mvo: https://bugs.launchpad.net/snapd/+bug/1835024
[14:32] <mup> Bug #1835024: Links triggered within most snap apps open in a separate browser session <snapd:Confirmed> <xdg-utils (Ubuntu):New> <https://launchpad.net/bugs/1835024>
[14:32] <ogra> Chipaca, the raspi2 in there is very rudimentary
[14:33] <ogra> (i.e. it gets you to boot half a kernel on a very hand-made image)
[14:34] <ijohnson> Nice thanks mborzecki feel free to respond if you like before I get to it
[14:35] <mborzecki> ijohnson: already responded there before ;) i did see thig happen on 18.04.3, it'd be great to double check on 19.04/10, iirc it seemed to work correctly there
[14:39] <zyga> ah, I wanted to mention something to maciek
[14:41] <mborzecki> another reboot, and bluetooth is back, right when i don't need it anymore
[14:46] <mup> PR pc-amd64-gadget#23 closed: Add missing partitions and improve grub.cfg-recovery <Created by mvo5> <Merged by xnox> <https://github.com/snapcore/pc-amd64-gadget/pull/23>
[15:10] <b_b> hi
[15:22] <b_b> i haven't been here for a while
[15:22] <b_b> and i'm discovering base: items
[15:23] <b_b> anyone know if i can't find a concise tutorial about upgrading a legacy snap ?
[15:23] <b_b> i'm maintening this one : https://github.com/thetimelineproj/timeline_snap
[15:29] <b_b> well, not a good start i'm still on ubuntu 16.04
[15:38] <Chipaca> b_b: 1604 should still be fine
[15:38] <b_b> 'k
[15:38] <Chipaca> b_b: get snapcraft as a snap
[15:38] <Chipaca> b_b: remove the apt one
[15:39] <Chipaca> b_b: and then try to run snapcraft as you did before
[15:39] <Chipaca> b_b: it's got a 'legacy' mode where it _should_ work just as it did, no (or minimal) changes needed
[15:39] <Chipaca> b_b: but, as soon as you add a base: to your snapcraft.yaml it's no longer in legacy mode
[15:40] <Chipaca> b_b: the good thing is, the non-legacy snapcraft, running on 1604, can build core:18 snaps
[15:40] <Chipaca> base:core18 *
[15:40] <b_b> i've found that sudo snap install --classic snapcraft could do the job to start
[15:40] <Chipaca> b_b: right, that and multipass and you should be golden
[15:41] <Chipaca> (multipass only for non-legacy mode though)
[15:41] <b_b> so i have to apt remove snapcraft too ?
[15:42] <Chipaca> b_b: i think otherwise it'll not be using the snap one
[15:42] <b_b> 'k doing this
[15:43] <b_b> thise base thing could finally make the timeline snap use the gtk theme \o/
[15:47] <b_b> thx for the help Chipaca
[15:47] <Chipaca> b_b: you'll want to connect to gtk-common-themes for that i suspect
[15:47] <Chipaca> b_b: i don't think it's got to do with bases :) but i'm not an expert on that side of things
[15:47] <b_b> 'm reading this https://snapcraft.io/docs/t/desktop-app-support-gtk/6834
[15:48] <b_b> so the base is "just" needed
[15:48] <Chipaca> b_b: 👍
[15:48] <Chipaca> well, it does say there are other approaches but that core18 is the recommended one
[15:48] <mup> PR snapd#7675 closed: release: preseed mode flag <Preseeding 🍞> <Simple 😃> <Created by stolowski> <Merged by stolowski> <https://github.com/snapcore/snapd/pull/7675>
[15:50] <b_b> 'xactlly
[15:51] <b_b> so i still got snapd 2.40 installed from apt, is it ok ?
[15:52] <Chipaca> b_b: what does 'snap version' say?
[15:52] <b_b> snap    2.42.1
[15:52] <b_b> snapd   2.42.1
[15:52] <b_b> series  16
[15:52] <b_b> ubuntu  16.04
[15:52] <b_b> kernel  4.15.0-52-generic
[15:52] <b_b> and snapcraft --version => snapcraft, version 3.8
[15:53] <Chipaca> b_b: you should be fine then :)
[15:53] <b_b> nice, still got to install multpass
[15:53] <b_b> "However, if you have previously packaged snaps using LXD and have not used bases, you may have some initial transition issues, and it is good to know how to handle the new development environment in a seamless manner."
[15:53] <b_b> ↑ this is clearly my state :p
[15:54]  * cachio lunch
[15:56] <b_b> hmmm
[15:56] <b_b> error: snap "multipass" is not available on stable but is available to install on the following
[15:56] <b_b> let's go for a beta first
[15:57] <Chipaca> :-) sage
[15:57] <b_b> claro, i have to test the transition of the actual snap
[15:57] <b_b> and bump it to latest 2.0.0 of the app
[15:58] <b_b> don't want to pass hourrs on this, since i don't use the app as a snap but from source...
[21:21] <genii> Hm
[21:26]  * cachio eow