[01:34] <callmepk> good morning
[01:49] <duflu> Morning callmepk 
[01:51] <callmepk> hi duflu 
[06:16] <jibel> Good morning everyone
[06:31] <duflu> Morning jibel 
[06:34] <jibel> Hi duflu 
[06:40] <callmepk> hi jibel 
[06:47] <jibel> Hi callmepk 
[07:12] <seb128> goood morning desktopers
[07:18] <duflu> Morning seb128 
[07:18] <seb128> hey duflu, how are you?
[07:18] <duflu> seb128, going... better. You?
[07:20] <seb128> I'm alright thanks! summer finally arrived which feels weird since we didn't really have spring weather, from cold to warm without adaptation
[07:21] <duflu> Sounds like you might get some variation before it sticls
[07:21] <duflu> sticks
[07:30] <jibel> Good morning se
[07:30] <jibel> seb128, ^ 
[07:31] <jibel> tab completion failed :)
[07:31] <seb128> hey jibel!
[07:32] <seb128> ok, things should work now
[08:03] <awayney> so this is where the action is?
[08:06] <seb128> hey laney, wb! Did you had a nice week off?
[08:07] <laney> yeah I lost my capital 'L' at some point during it! /me is a cool kid now
[08:08] <laney> was nice, swimming in the sea and relaxing mainly - and now summer is here :-)
[08:08] <laney> how's it going there seb128?
[08:08] <seb128> nice timing!
[08:08] <seb128> going alright, summer arrived for us as well which is a nice change :-)
[08:09] <seb128> oh, I'm registered to get my covid vaccin round1 on next monday now
[08:10] <laney> \o/
[08:11] <laney> exciting times
[08:11] <laney> I had mine on Friday, no big problems except my arm was like it got punched for 3 days
[08:11] <seb128> seems quite common from the news title I saw
[08:14] <laney> yeah that's an ok price to pay I think :p
[08:14] <seb128> indeed!
[08:14] <seb128> otherwise on work news Trevinho is rocking the GNOME updates, cleaning technical debt by removing old patches on the way
[08:15] <laney> nice
[08:15] <seb128> his discourse weekly summary is a nice read, I recommend it ;-)
[08:15] <seb128> speaking of, my scripts tells me
[08:16] <seb128> jamesh, marcustomlinson, tillkamppeter, weekly summary reminder
[08:17] <laney> I did, I just 'liked' it! /me pats Marco
[08:17] <laney> also had a few telegram chats about debian packaging from the beach ;-)
[08:17] <seb128> haha
[08:19] <laney> guess I should fiddle with IRC config to drop freenode eh
[08:19] <laney> also looks like gnome members can #voteken
[08:24] <seb128> :-)
[08:34] <laney> let's see if that worked
[08:35] <laney> no :(
[08:37] <jibel> Good morning laney 
[08:37] <duflu> Morning laney
[08:47] <laney> hey jibel duflu, how are you?
[08:47] <laney> think I'm done fiddling with IRC config for now
[08:47] <duflu> laney, alright thanks. Not as excited as you
[08:47] <laney> that's a high bar
[08:48] <laney> so, no shame
[08:52] <jibel> laney, going well, thanks. 
[09:01] <Trevinho> laney: hey back Laney 
[09:02] <Trevinho> also... KGB seems to be still on freenode 
[09:04] <laney> yeah will fix it
[09:44] <laney> Trevinho: did you use the gitlab api before?
[09:45] <laney> if possible we should use it to set up / fix the webhooks for libera
[09:47] <seb128> who is maintaining and hosting that bot btw?
[09:48] <seb128> laney, is that you?
[09:48] <laney> nope, some debian guys
[09:48] <seb128> I wanted to add a bot to the channel maybe to do some status daily reports, like last ISO build result, etc
[09:48] <laney> great idea
[09:49] <laney> but it would need to be something else not that KGB thing
[09:49] <seb128> right, that's what I was wondering
[09:49] <seb128> I'm probably going to do something simple like queuebot
[09:49] <laney> nod
[09:49] <laney> would be good if it could be part of the metrics project, like getting data from there
[09:49] <laney> (if possible)
[09:53] <seb128> what would be the right way to query data from the metrics?
[09:54] <seb128> I know that grafana has access to the records but I don't know how
[09:56] <laney> there's a python API, you can use sql-ish queries to get data from them
[10:03] <laney> or interesting, looks like there's something like https://github.com/influxdata/kapacitor which could maybe be used
[10:13] <seb128> laney, I meant the db, can we public access it? where is it hosted? 
[10:17] <laney> seb128: it's in prodstack. If you go with this idea you could deploy it in the same environment as the metrics collector itself
[10:17] <laney> not the same machine, but the same env, then it will be able to connect to it
[10:17] <seb128> ack
[10:20] <seb128> ok, on that note it's modern age but we are still on IRC and I still don't have a proxy so I'm going to drop of the channel for a bit
[11:25] <GunnarHj> Hi oSoMoN, Your help would be appreciated to point me to the right person. The thing is that apparmor fixes are needed to made fcitx5 (bug #1928360) and to some extent ibus (bug #1890905) work as expected in the snaps. I had a conversation with Seth A. the other day, and he claims that the snap team needs to be involved.
[11:25] <GunnarHj> https://irclogs.ubuntu.com/2021/05/27/%23ubuntu-devel.html#t18:57
[11:25] <GunnarHj> Who would be the right person to talk with?
[11:25] <ubot3> Bug 1928360 in ubuntukylin "Switch to Fcitx 5 for Chinese" [Undecided, In Progress] https://launchpad.net/bugs/1928360
[11:25] <ubot3> Bug 1890905 in snapd (Ubuntu) "Snaps cannot access IBus when $XDG_CACHE_HOME is set" [Medium, Confirmed] https://launchpad.net/bugs/1890905
[12:55] <oSoMoN> GunnarHj, you could try pedronis or ijohnson (both are on #snappy)
[13:34] <GunnarHj> oSoMoN: Will do, thanks!
[14:23] <oSoMoN> ricotz, re bug #1930315, we should probably change the build dependencies of the firefox-next PPA to security only, to replicate how firefox updates are built for the archive, and catch these issues earlier, what do you think?
[14:23] <ubot3> Bug 1930315 in firefox (Ubuntu) "firefox 89.0 FTBFS on ppc64el with clang 10" [High, Fix Committed] https://launchpad.net/bugs/1930315
[14:29] <ricotz> oSoMoN, hi, I understand, I was hoping the llvm 11 backport would be a viable solution
[14:30] <ricotz> e.g. focal got llvm 12 in -proposed now
[14:30] <oSoMoN> ricotz, that will be viable as soon as it hits -security
[14:30] <ricotz> I would expect such build failures with older llvm will occur in the future more often
[14:31] <oSoMoN> hopefully not too often :/
[14:31] <ricotz> oSoMoN, llvm 11 is there forso 2 months
[14:31] <ricotz> oops
[14:31] <ricotz> oSoMoN, llvm 11 is there for 2 months
[14:32] <ricotz> in build-support ppa that is
[14:32] <oSoMoN> and it is in focal-updates, but we don't use -updates to build firefox/thunderbird updates
[14:33] <ricotz> I thought we are talking about bionic
[14:33] <oSoMoN> so until there is a CVE in llvm-toolchain-11 and an update hits focal-security, we can't rely on it
[14:33]  * ricotz just mentioned focal as example
[14:33] <oSoMoN> that build failure affected both bionic and focal
[14:34] <ricotz> ah I see
[14:34] <oSoMoN> for bionic we're stuck with clang 10 for the foreseeable future
[14:34] <ricotz> ok, and this might get painful
[14:35] <ricotz> alright
[14:36] <oSoMoN> only two years of bionic support to go ;)
[14:37] <oSoMoN> ricotz, shall I change the build deps of firefox-next?
[14:37] <ricotz> done, will fiddle with the build-support ppa later
[14:38] <ricotz> oSoMoN, please push these build fixes to the best branches :)
[14:39] <oSoMoN> thanks, I think I did push them to firefox.bionic and firefox.focal
[14:39] <ricotz> oSoMoN, ff90 failures of ppc64/s390x are fixed in nss upstream which hopefully gets merged into beta soon
[14:39] <ricotz> I meant beta branches
[14:40] <oSoMoN> I wanted to come up with a smarter patch that detected the clang version and didn't skip these flags if it is > 10, but couldn't figure out an obvious way to access the clang version
[14:40] <oSoMoN> I sure can merge the release branches into the beta branches
[14:41] <ricotz> thanks
[14:47] <oSoMoN> ricotz, done
[14:48] <ricotz> great
[15:51] <laney> Trevinho: I asked the kgb folks and they said it is configured for libera already, we need to update the webhooks to have &network=libera instead of =freenode
[15:52] <Trevinho>   laney nice, will test soon
[15:52] <Trevinho> laney: though... I think I can't edit them (most of them at least)
[15:52] <Trevinho> so you've to go with manual labooor :)
[15:53] <laney> should use the API I think
[15:53] <laney> will look into it later
[15:54] <laney> (not today probably)