[05:41] <seb128> good morning desktopers
[06:03] <didrocks> good morning
[06:45] <duflu> Morning seb128 and didrocks
[06:46] <didrocks> hey duflu
[06:46] <Wimpress> o/
[06:53] <oSoMoN> good morning desktoppers
[06:53] <duflu> Hi oSoMoN and Wimpress
[06:54] <oSoMoN> hello duflu
=== pstolowski|afk is now known as pstolowski
[07:13] <didrocks> salut oSoMoN
[07:16] <seb128> hey duflu, Wimpress, how are you?
[07:16] <seb128> lut didrocks oSoMoN en forme ?
[07:16] <duflu> Trevinho, excellent work with CI
[07:16] <Trevinho> duflu: thanks :)
[07:16] <duflu> seb128,  I am finally feeling mostly good. How are you?
[07:16] <seb128> I'm good
[07:16] <Trevinho> hopefully there it will catch also some memory errors we randomly were getting
[07:17] <Trevinho> hi seb128
[07:17] <seb128> quite some rain, I'm glad I took the umbrella to go to drop the kid for the day
[07:17] <Trevinho> so far valgrind runs quite happily in the test suite either
[07:18] <duflu> Valgrind with exit 1 on errors
[07:18] <duflu> ?
[07:18] <duflu> --exit-on-first-error=yes
[07:18] <duflu> or similar, Trevinho?
[07:19] <duflu> or just --error-exitcode=1
[07:19] <didrocks> seb128: ça va, et toi ?
[07:19] <seb128> ça va !
[07:20] <Trevinho> duflu: mh, I've been just using meson test with `--wrap` valgrind
[07:20] <duflu> Trevinho, I would recommend --error-exitcode=1 or else it might pass still with errors
[07:21] <Trevinho> duflu: well, looking at the logs of the errors, no one was related to mutter though, all lower level stuff which are probably false positive
[07:21] <oSoMoN> salut didrocks, seb128
[07:21] <duflu> OK, too soon
[07:21] <Trevinho> but in general `MALLOC_CHECK_` does the same these days
[07:22] <duflu> MALLOC_CHECK_ is a weak and fast check, not as useful as Valgrind
[07:22] <duflu> The former is also delayed, so might not crash in the location of the error
[07:24] <duflu> MALLOC_CHECK_ is most useful on the customer's machine in production when you don't have other debugging tools
[07:25] <duflu> or can't afford a major slowdown
[07:33] <marcustomlinson> morning seb128 didrocks duflu Wimpress oSoMoN Trevinho
[07:33] <duflu> Morning marcustomlinson
[07:34] <duflu> and marcustomlinson_
[07:34] <seb128> hey marcustomlinson, how are you? had a good long w.e?
[07:34] <marcustomlinson> yeah was great thanks! Have a good average length weekend seb128?
[07:34] <oSoMoN> good morning marcustomlinson
[07:35] <seb128> yeah, w.e was nice. We didn't do anything fancy but it was relaxing
[07:35] <marcustomlinson> much the same yeah
[07:36] <marcustomlinson> "relaxing" with a 3 year old is not quite what relaxing used to be though... :P
[07:36] <didrocks> hey marcustomlinson!
[07:45] <didrocks> zfs 0.8 is out \o/ quite some good timing :)
[07:49] <seb128> enjoy the update :)
[07:50] <didrocks> wondering if we should handle it directly, I'll ask cking, debian also has rc4 in unstable (missed rc5 apparently)
[07:50] <didrocks> if we have good relationship on that package, I don't want to go over other people :)
[07:51] <didrocks> (also, there are some big changes, so ensuring the update is correct is tricky)
[07:51]  * didrocks cross fingers as well that not too many changes in the golang binding will be needed for libzfs
[07:51] <cking> i'm going to get the current 0.7.x version working with 5.2 first, then once the debian version 0.8 is out I'll sync them up. I'm concerned about regressions moving to 0.8-rc versions
[07:52] <seb128> we are not in an hurry to land it in the archive so yeah it makes sense to let the time to let Debian&co to look at it/comment first
[07:52] <didrocks> cking: hey! So you think that 0.8 final will be quickly packaged in debian, the maintainance is active there?
[07:53] <didrocks> cking: yeah, I was wondering if you wanted to backport the 5.2 patches in 0.7, they landed post-release for 0.8
[07:53] <cking> I'm backporting the 5.1/5.2 kernel compat fixes to 0.7.12 first and then move to 0.8 once it's in debian
[07:54] <didrocks> cking: thanks! Let's see how it goes, if you need any help, jibel and I looked at the generator and the new systemd units which are fixing some races on boot
[07:54] <cking> normally there are also some regression fixes to new releases a little while after a new release, so I'm always very careful not to jump to the latest release until I know it's OK
[07:54] <didrocks> yeah ;) as people only start to test after releases on real system and not RC… :)
[07:54] <cking> I hate file systems eating data :-)
[07:54] <didrocks> or it makes you loving your backups :p
[07:55] <cking> heh
[07:55] <didrocks> do not hesitate if you need any help!
[07:55] <didrocks> seb128: yeah, the only thing I'm a little bit scared of is incompatibility in the bindings, but we can figure that out (just not too close from FF)
[07:55] <cking> didrocks, ok, i hope to get zfs with the 5.2 kernel out this week, but it takes me a day or so to ensure it passes all the regression tests
[07:56] <didrocks> cking: are there some automated tests out of autopkgtests? I'm wondering if we add systemd units/change initramfs if there are some stuff in addition to autopkgtests we can run
[07:56] <cking> didrocks, I can send you my testing howto
[07:57] <didrocks> that would be great, thanks!
[08:02] <Laney> yo de yo
[08:04] <didrocks> morning Laney, how was your week-end?
[08:05] <oSoMoN> yo Laney
[08:06] <seb128> hey Laney, how are you? had a nice long w.e?
[08:08] <RAOF> Oooh, a release of zfs 0.8? Time to look at what it would take to integrate encryption with lxd!
[08:09] <RAOF> Hello all!
[08:09] <Laney> moin didrocks oSoMoN seb128
[08:09] <Laney> yes very good, we went to the beach on saturday and there was even some sun :>
[08:15] <Laney> what about you? can you even remember it or is it too far in the past?
[08:15] <Laney> sorry, got distracted by j_uliank
[08:16] <didrocks> Laney: sounds nice! Martin is sick since Friday and so, plans were cancelled, can't wait for him to feel better again
[08:16] <didrocks> RAOF: hey! Yeah, native encryption \o/
[08:16] <didrocks> also can send directly encrypted dataset for backup :p
[08:17] <Laney> :(
[08:19] <RAOF> didrocks: yeah, I built an encrypted storage pool for a test LXD system. It worked! Although you needed to manually poke LXD a bit.
[08:20] <RAOF> (with 0.8rc3)
[08:23] <seb128> Laney, w.e was good, most relaxing. It was really nice and sunny here on saturday as well :)
[08:26] <didrocks> RAOF: sounds nice!
[08:27] <didrocks> cking: thx for the notes!
[08:28] <seb128> marcustomlinson, do you know what's the status of snaps that need gtk 3.24? do we change them to build gtk themself for now? I'm trying to figure out if we can update epiphany, upstream is unhappy about us shipping an outdated version (which has a bug which makes some menu items not available on Disco)
[08:28] <marcustomlinson> seb128: hmm, yeah we have to build gtk in for a later version
[08:29] <marcustomlinson> but it's a bit of a b**tch
[08:29] <seb128> well I guess we had it figured it out for some snaps so it's a simple copy/paste exercice at this point?
[08:30] <duflu> Tis the time of day for LP to time out
[08:30] <marcustomlinson> I'm not sure that we've completely worked it out just yet, I'm in the process of that now
[08:30] <marcustomlinson> seb128: but yeah, one could copy it from the build-snap
[08:30] <duflu> Morning Laney
[08:30] <duflu> Evening RAOF
[08:30] <marcustomlinson> seb128: https://gitlab.gnome.org/Community/Ubuntu/gnome-3-28-1804-sdk/blob/master/snapcraft.yaml
[08:31] <marcustomlinson> line 291
[08:31] <seb128> ah
[08:31] <seb128> we don't have any snap on 3.24 today?
[08:32] <marcustomlinson> kenvandine would know the answer to that
[08:32] <seb128> k, let's wait for him to be up then
[08:32] <seb128> thx marcustomlinson
[08:35] <marcustomlinson> seb128: https://forum.snapcraft.io/t/support-for-gtk-3-24/9782/9
[08:36] <marcustomlinson> from that response, looks like the build snap does aim to be the example. But ken will know if anything has changed over the last 3 months
[08:37] <seb128> right
[09:34] <Laney> seb128: did you mean to upload that epiphany to debian too, or did you use the wrong version number?
[10:40] <GunnarHj> Hi seb128, after a long chat and some additions to the test case, sil2100 is willing to review bug #1768166 on behalf of the SRU team. Do you have time to sponsor? https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
[10:40] <ubot5> bug 1768166 in libpinyin (Ubuntu Cosmic) "Random crashes " [Medium,In progress] https://launchpad.net/bugs/1768166
[10:43] <GunnarHj> seb128: Btw, we concluded that it should be uploaded for now to both bionic and cosmic.
[10:55] <sil2100> Cosmic as well since even though we don't really care 'much' about it since it's EOL, but backports like these have higher versions and I'm worried about upgrade paths through cosmic to disco
[11:21] <seb128> Laney, crap, I first meant to update to Debian but then I realized the situation was weird in Debian with a 3.32 hacked and not in experimental, so I changed to upload to Ubuntu and forgot to change the version, sorry
[11:22] <seb128> GunnarHj, hey, I'm a bit busy today/tomorrow, if you can try another sponsor that would be nice, otherwise I try to have a look once I'm done catching up with my current todolist
[11:24] <seb128> Laney, are you looking at those updates as well now/going to do the bionic SRU? or just asking?
[11:24]  * seb128 doesn't want to dup work
[11:24] <Laney> seb128: no
[11:25] <seb128> k, thx
[11:26] <Laney> that would be worth trying to get into buster
[11:26] <seb128> how does one do that?
[11:27] <seb128> I've been disconnected enough from Debian that I don't know the process for freeze exception
[11:27] <seb128> (unsure I've been active around a Debian freeze ever in fact)
[11:29]  * seb128 reads https://release.debian.org/buster/freeze_policy.html
[11:31] <Laney> that's the one
[11:38] <GunnarHj> seb128: Ok, I'll ask tsimonq2.
[11:38] <GunnarHj> tsimonq2: Hi Simon! Wondering if you can sponsor bug #1768166? It has been carefully pre-reviewed by the SRU-team. Proposed uploads in https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin . Ask you to upload to both bionic and cosmic.
[11:38] <ubot5> bug 1768166 in libpinyin (Ubuntu Cosmic) "Random crashes " [Medium,In progress] https://launchpad.net/bugs/1768166
[12:41] <kenvandine> seb128: the gtk branch?  That was there to prevent it from trying to build gtk4
[12:41] <kenvandine> at least at the time
[12:42] <kenvandine> i'm sure there's a newer stable branch now
[12:42] <kenvandine> marcustomlinson: ^^
[12:46] <seb128> kenvandine, hey, the question was gtk 3.24 (which was have since cosmic), that's apparently what is blocking us from update epiphany-browser (didi you see the upstream blog post about Ubuntu shipped outdated/buggy version, that included the snap)
[12:51] <kenvandine> ah
[12:51] <kenvandine> yeah, i probably pinned that branch back during the cosmic cycle :)
[12:52] <marcustomlinson> kenvandine: that is the latest stable branch
[12:52] <seb128> no it's not?
[12:56] <kenvandine> yes it is
[12:57] <kenvandine> 3.24.8 is the latest in the 3 series
[13:27] <seb128> kenvandine, sorry, I though that comment was about epiphany-browser, not gtk :)
[13:27] <seb128> so can we update that one?
[13:30] <seb128> ok, it's that time of the week
[13:30] <seb128> #startmeeting Desktop Team Meeting - 2019-05-28
[13:30] <meetingology> Meeting started Tue May 28 13:30:08 2019 UTC.  The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:30] <meetingology> Available commands: action commands idea info link nick
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/uEut6bfN/ubuntu-desktop-1910-cycle | Desktop Team Meeting - 2019-05-28 | Current topic:
[13:30] <seb128> Roll call: didrocks, duflu (out), jamesh (out), jibel (out), kenvandine, laney, marcustomlinson, oSoMoN, tkamppeter, trevinho, robert_ancell (out)
[13:30] <kenvandine> o/
[13:30] <marcustomlinson> present
[13:31] <oSoMoN> ol/
[13:31] <Trevinho> 0/
[13:31] <seb128> hope everyone is having a good start of week
[13:31] <seb128> let's get started :)
[13:31] <seb128> oh, earlier morning Marco!
[13:31] <seb128> #topic rls-bb-bugs
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/uEut6bfN/ubuntu-desktop-1910-cycle | Desktop Team Meeting - 2019-05-28 | Current topic: rls-bb-bugs
[13:31] <didrocks> hey
[13:31] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[13:31] <seb128> no desktop material
[13:32] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[13:33] <seb128> so that list has a few
[13:33] <seb128> the n-m ones are leftover of the SRU that regressed/got reverted, I'm going to assign to Till who is working on that
[13:34] <seb128> bug #1825940
[13:34] <ubot5> bug 1825940 in linux (Ubuntu) "[graphics] Enable ICL" [Undecided,Confirmed] https://launchpad.net/bugs/1825940
[13:35] <seb128> tjaalton, ^ should that be assigned to you?
[13:35] <seb128> assuming so, shout/ping me if that's wrong
[13:36] <seb128> bug #1830022
[13:36] <ubot5> bug 1830022 in cups (Ubuntu Disco) "DirtyCleanInterval should be 0 by default" [Undecided,Confirmed] https://launchpad.net/bugs/1830022
[13:36] <seb128> dgadomski, hey, should that be assigned to you?
[13:36] <dgadomski> seb128: hey, I'd appreciate tkamppeter's opinion on this one
[13:37] <seb128> dgadomski, also please respect the process, either tag as rls-nn-incoming for reviews if you work on a fix and decide to target then please assign to yourself directly
[13:37] <Laney> sounds like Incomplete
[13:37] <seb128> yeah
[13:37] <seb128> also the targetting sound wrong, I'm going to delete those lines
[13:37] <seb128> dgadomski, please tag rls-nn-incoming once it's understood if you feel like that needs proper serie tracking
[13:37] <seb128> next
[13:38] <seb128> japenese new era on some packages
[13:38] <seb128> it's probably something we should do so nominations sound right
[13:38] <tjaalton> seb128: done
[13:38] <seb128> does anyone fancy learning a bit about the topic and deal with those changes?
[13:39] <Laney> c_yphermox set all that up, have you checked it isn't being handled already?
[13:40] <seb128> no I didn't, I will after the meeting and find an assignee if needed
[13:40] <oSoMoN> I had a brief look at the bug and at least the poppler-data part needs some upstream work
[13:40] <seb128> thx for pointing that out!
[13:40] <seb128> ok, next cosmic
[13:40] <seb128> #topic rls-cc-bugs
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/uEut6bfN/ubuntu-desktop-1910-cycle | Desktop Team Meeting - 2019-05-28 | Current topic: rls-cc-bugs
[13:40] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html
[13:40] <seb128> no desktop
[13:41] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-tracking-bug-tasks.html
[13:41] <seb128> same japense era
[13:41] <seb128> that's it
[13:41] <seb128> #topic rls-dd-bugs
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/uEut6bfN/ubuntu-desktop-1910-cycle | Desktop Team Meeting - 2019-05-28 | Current topic: rls-dd-bugs
[13:41] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html
[13:41] <seb128> still no desktop!
[13:41] <kenvandine> :)
[13:41] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-tracking-bug-tasks.html
[13:42] <seb128> same japenese era
[13:42] <seb128> that's it
[13:42] <seb128> #topic rls-ee-bugs
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/uEut6bfN/ubuntu-desktop-1910-cycle | Desktop Team Meeting - 2019-05-28 | Current topic: rls-ee-bugs
[13:42] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-incoming-bug-tasks.html
[13:43] <seb128> there is one buggy g-c-c entry, marking that one invalid (I meant to do that from previous week, I had a look to the code and then forgot)
[13:43] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-tracking-bug-tasks.html
[13:43] <seb128> that's in shape
[13:43] <seb128> #topic update_excuses_by_team.html#desktop-packages
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/uEut6bfN/ubuntu-desktop-1910-cycle | Desktop Team Meeting - 2019-05-28 | Current topic: update_excuses_by_team.html#desktop-packages
[13:43] <seb128> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#desktop-packages
[13:44] <seb128> nothing there, the only entry seems an infra problem
[13:44] <tkamppeter> dgadomski, seb128, I have posted about bug 1830022 in the CUPS upstream mailing list now, let us see what Mike Sweet (CUPS upstream author) will say about this.
[13:44] <ubot5> bug 1830022 in cups (Ubuntu) "DirtyCleanInterval should be 0 by default" [Undecided,Confirmed] https://launchpad.net/bugs/1830022
[13:44] <seb128> #topic AOB
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/uEut6bfN/ubuntu-desktop-1910-cycle | Desktop Team Meeting - 2019-05-28 | Current topic: AOB
[13:44] <seb128> tkamppeter, thx
[13:44] <seb128> other topics?
[13:44] <didrocks> o/
[13:45] <didrocks> so, there are 3 MIRs which needs action/discussion
[13:45] <didrocks> https://bugs.launchpad.net/ubuntu/+source/xdg-dbus-proxy/+bug/1811824 -> got an ACK, just waiting on dep on it
[13:45] <ubot5> Launchpad bug 1811824 in xdg-dbus-proxy (Ubuntu) "[MIR] xdg-dbus-proxy" [Undecided,Incomplete]
[13:45] <didrocks> https://bugs.launchpad.net/ubuntu/+source/libbluray/+bug/1746629 -> was requested by jbicha, do we still want this?
[13:45] <ubot5> Launchpad bug 1746629 in libbluray (Ubuntu) "[MIR] libbluray" [Undecided,Incomplete]
[13:45] <didrocks> https://bugs.launchpad.net/ubuntu/+source/usbguard/+bug/1816548 -> it's a NACK for now AFAIK
[13:45] <ubot5> Launchpad bug 1816548 in usbguard (Ubuntu) "[MIR] usbguard" [Undecided,Incomplete]
[13:46] <kenvandine> didrocks: i'll look at xdg-dbus-proxy
[13:46] <kenvandine> i think we will need it soonish
[13:46] <didrocks> kenvandine: poke seb or myself once the dep is added so that we promote it
[13:46] <didrocks> (thx)
[13:47] <didrocks> I don't see strong reasons for libbluray, we don't have it for 8 years…
[13:47] <didrocks> (and it doesn't do decryption, unsure how uself this is)
[13:47] <didrocks> useful*
[13:47] <Laney> still a delta
[13:47] <didrocks> I guess seb is more aware of the topic for the last one
[13:47] <didrocks> true
[13:47] <seb128> didrocks, libblueray is not important but it's an easy one it would lower some Debian delta and enable a feature which exists upstream/in other distro
[13:47] <didrocks> Laney: wait to handle it so that we remove that delta? :)
[13:48] <seb128> but if it's*
[13:48] <didrocks> I guess it's just a confirmation that requests are fitted
[13:48] <seb128> it's a wishlist but still valid
[13:48] <seb128> yes they are
[13:48] <Laney> it's not actually a proper delta btw
[13:48] <seb128> usbguard is on review/discussion on the GNOME side
[13:48] <Laney> a conditional thing in the rules file
[13:48] <seb128> we have work to do from the security team review though
[13:48] <Laney> still it's a feature delta
[13:48] <didrocks> seb128: good, I'll answer that in our next week meeting
[13:49] <seb128> didrocks, thx!
[13:49] <didrocks> Laney: if you can just ack that all is good in the bug, I'm happy to port that in our next meeting
[13:49] <seb128> usbguard is probably to push forward this cycle if we want  it for the LTS
[13:49] <Laney> k
[13:49] <didrocks> agreed
[13:49] <didrocks> thanks Laney & seb128
[13:49] <didrocks> that was it for me
[13:50] <seb128> thx for the reminder didrocks, usbguards slipped a bit from my mind and I didn't include it in the planning, I should
[13:50] <seb128> other topics?
[13:50] <seb128> seems not
[13:50] <seb128> let's wrap then, thanks everyone!
[13:50] <seb128> #endmeeting
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/uEut6bfN/ubuntu-desktop-1910-cycle
[13:50] <meetingology> Meeting ended Tue May 28 13:50:49 2019 UTC.
[13:50] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2019/ubuntu-desktop.2019-05-28-13.30.moin.txt
[13:50] <didrocks> thx
[13:51] <oSoMoN> thx
=== pstolowski is now known as pstolowski|afk
=== jdstrand_ is now known as jdstrand
[20:24] <seb128> kenvandine, marcustomlinson, so what was the outcome of snaps needing gtk 3.24 / updating epiphany-browser? I did deal with updating the deb in bionic/cosmic/eoan now and I would like to go back to upstream being able to tell them we sorted out the issues raised, but we need to fix the snap as well for that
[20:25] <kenvandine> seb128: i haven't had a chance to look at it
[20:26] <kenvandine> marcustomlinson: can you have a look?  maybe tomorrow morning?
[20:26] <marcustomlinson> kenvandine: sure, can you point me to the repo
[20:26] <kenvandine> seb128: i suspect the answer will be building gtk as a part, but that is a can of worms :)
[20:26] <seb128> kenvandine, but you expect that to be easy? marcus was pointing out a snapcraft post earlier from feb that was stating that gtk 3.24 would come through the build snap
[20:26] <seb128> kenvandine, we don't have any snap using gtk 3.24 today?
[20:26] <kenvandine> but the build snap isn't ready yet
[20:27] <kenvandine> nope
[20:27] <kenvandine> but we need it
[20:27] <seb128> woh
[20:27] <marcustomlinson> seb128: so the build snap is WIP
[20:27] <seb128> I though most GNOME apps would have had that depends by now
[20:27] <marcustomlinson> my WIP. That said, I'm in a good position to look at this then
[20:27] <kenvandine> nope
[20:27] <seb128> k
[20:27] <seb128> well don't worry guys
[20:27] <seb128> I will go back to them telling that we sorted out the debs
[20:28] <marcustomlinson> seb128: no seriously I will do it tomorrow
[20:28] <seb128> I mentioned that the snap situation was probably more complex since our framework is based on bionic
[20:28] <seb128> they seemed really surprised by it
[20:28] <seb128> "so snap can't even get a recent gtk" :/
[20:28] <kenvandine> i think marcustomlinson is in a good position to sort that out now though
[20:28] <seb128> marcustomlinson, k, let me know how it goes, thx!
[20:28] <seb128> \o/
[20:28] <marcustomlinson> seb128: could you point me to the repo
[20:29] <marcustomlinson> with the snapcraft.yaml
[20:29] <kenvandine> https://git.launchpad.net/~ubuntu-desktop/epiphany/+git/snap/
[20:29] <kenvandine> i think
[20:29] <seb128> marcustomlinson, https://code.launchpad.net/~ubuntu-desktop/+snap/epiphany
[20:29] <seb128> ah, same thing
[20:29] <kenvandine> marcustomlinson: it's actually not a bad test case :)
[20:30] <marcustomlinson> k cool. My major fear is that it will not be compatible with the runtimes in the platform snap
[20:30] <kenvandine> maybe...
[20:30] <kenvandine> but, newer libgtk should be fine
[20:30] <marcustomlinson> yeah I'll give it a go
[20:31] <kenvandine> building it is more of the issue
[20:31] <kenvandine> bundling the newer libgtk is safer, as long as it's loaded first
[20:31] <kenvandine> which might be an issue :)
[20:31] <kenvandine> might need to flip the LD_LIBRARY_PATH order :)
[20:31] <seb128> kenvandine, marcustomlinson, thanks!
[20:32] <marcustomlinson> gonna call it a night now though. cheers!
[21:00] <seb128> same here, night!
=== JanC_ is now known as JanC