[01:50] <callmepk> good morning
[01:53] <duflu> Morning callmepk 
[02:04] <callmepk> morning duflu 
[06:48] <didrocks> good morning
[06:50] <duflu> Morning didrocks 
[06:50] <didrocks> hey duflu 
[07:10] <oSoMoN> good morning desktoppers
[07:11] <didrocks> salut oSoMoN 
[07:32] <oSoMoN> salut didrocks 
[07:42] <jibel> salut tout le monde
[08:24] <duflu> Salut oSoMoN et jibel 
[08:34] <Nafallo> morning! :-)
[08:38] <oSoMoN> salut jibel, hey duflu & Nafallo 
[08:55] <Wimpress> Bonjour!
[08:56] <Nafallo> morgon Wimpress :-)
[08:58] <oSoMoN> bonjour Wimpress !
[09:01] <duflu> Morning Nafallo and Wimpress 
[09:02] <Nafallo> I need more coffee... :-P
[09:03] <Laney> yoohoo
[09:04] <Nafallo> what language is that morning in? :-D
[09:04] <marcustomlinson> morning callmepk duflu didrocks oSoMoN jibel Nafallo Wimpress Laney
[09:04] <Nafallo> hey Laney, marcustomlinson :-)
[09:04] <seb128> hey oSoMoN didrocks jibel duflu Nafallo Wimpress Laney marcustomlinson 
[09:04] <Nafallo> salut seb128 da man! :-D
[09:04] <marcustomlinson> well timed seb128
[09:05] <callmepk> hi marcustomlinson , morning didrocks jibel Nafallo Wimpress Laney seb128 
[09:05] <seb128> hey callmepk 
[09:05] <seb128> how is everyone?
[09:05] <Nafallo> not at the correct coffee level... :-P
[09:05] <marcustomlinson> I’m good thanks, my son is back to nursery! how you seb128?
[09:05] <duflu> Hi marcustomlinson and seb128 
[09:06] <Laney> heh
[09:06] <duflu> and hi Laney
[09:06] <Laney> hey marcustomlinson Nafallo seb128 callmepk duflu 
[09:06] <oSoMoN> good morning Laney, marcustomlinson, seb128 
[09:06] <Laney> and oSoMoN!
[09:06] <Laney> active morning
[09:06] <oSoMoN> good afternoon/evening callmepk 
[09:06] <seb128> marcustomlinson, my stomach was a bit unhappy this night and I didn't sleep well so a bit extra tired :-(
[09:06] <duflu> It must be 9am in London-ish
[09:06] <marcustomlinson> always reminds me of the opening to Monty Python’s Meaning of Life
[09:06] <duflu> Yes
[09:06] <callmepk> oh morning oSoMoN 
[09:07] <marcustomlinson> seb128: take it from me, forcing yourself to sit at the computer and work just makes things worse! Go rest man
[09:08] <didrocks> hey marcustomlinson , seb128 , callmepk, Laney, Wimpress, Nafallo à the world and more and more and more :)
[09:09] <Nafallo> haha
[09:10] <Nafallo> basically hi .* :-D
[09:10] <seb128> marcustomlinson, right...
[09:10] <marcustomlinson> seb128: well you don’t need to take it from me, I’m sure you already know this
[09:10] <seb128> :-)
[09:10] <marcustomlinson> get better
[09:10] <seb128> thanks!
[09:11] <Laney> moin didrocks 
[09:12] <Laney> :( seb128 
[09:13] <seb128> on a positive notes, I landed another round of improvements for the snaps report
[09:13] <seb128> https://people.canonical.com/~platform/desktop/snaps.html
[09:13] <seb128> tweaked the colors a bit, also added the version of the gnome extension in use next to the version for candidate builds
[09:14] <Laney> nice
[09:15] <Laney> what is the top row for each entry, the one with the package name?
[09:27] <ricotz> good morning desktopers!
[09:27] <Nafallo> morning ricotz :-)
[09:28] <ricotz> something seems wrong with dnd/input-handling of windows in gnome-shell/mutter today
[09:28] <ricotz> Nafallo, hi
[09:32] <oSoMoN> good morning ricotz 
[09:33] <jamesh> marcustomlinson: I was having a look at your CLA check action, and noticed it doesn't seem to check the commit authors like the scripts in e.g. snapd do.  Was that intentional?
[09:34] <seb128> Laney, the main line is amd64, I could perhaps mention that next to the name?
[09:35] <seb128> hey jamesh, ricotz 
[09:35] <jamesh> hi seb128 
[09:35] <Laney> seb128: good idea, I thought it might be that those are all succeeding arches and the other lines are listed when there are failures or something
[09:36] <seb128> Laney, thx for the feedback!
[09:36] <Laney> I think it might be nicer if the FTBFS links were in the other cells too, like <version> (a newer version fails: <link>)
[09:36] <Laney> but maybe that's just me, a suggestion anyway
[09:36] <seb128> failing archs are the red items at the bottom
[09:36] <Laney> thanks for the work!
[09:37] <seb128> I guess it's a bit confusing
[09:37] <seb128> the version on the first line being a link points to the snap build launchpad page
[09:37] <seb128> the builds failured at the red arch mentions at the bottom
[09:38] <Laney> yeah, I'd prefer to read all of the status of the arch at once I guess, rather than find the build failure after reading a bit further down
[09:38] <Laney> maybe?
[09:38] <seb128> the snap page isn't arch specific, I put it on the first line because I was not sure how to represent it
[09:38] <Laney> ah
[09:38] <Laney> what if that was a link on the package name instead?
[09:39] <seb128> we have one page by build
[09:39] <Laney> IS ee
[09:39] <seb128> so several lines have one for candidate and one for edge
[09:39] <Laney> I'm confused because only 'some' of them are links
[09:39] <seb128> e.g evince and evince-mastrer
[09:39] <seb128> master
[09:39] <Laney> like for epiphany
[09:40] <seb128> right, epiphany doesn't have a -master build
[09:40] <seb128> I don't know how we ended up having a version in edge
[09:40] <seb128> https://code.launchpad.net/~desktop-snappers/+snap/epiphany uploads to candidate
[09:40] <Laney> other way to do it would be to have the top row be fore the source
[09:40] <Laney> and then have amd64 another row like the rest
[09:40] <seb128> right
[09:40] <seb128> I will try that
[09:41] <Laney> s/fore/for/
[09:41] <seb128> do some A / B /C layout and ask for feedback maybe
[09:41] <Laney> but yeah, FTBFSes inline is my main suggestion :>
[09:41] <seb128> good one, thanks :-)
[09:42] <Laney> I wonder how we can do a metric for this
[09:42] <Laney> like, when stable is out of date?
[10:00] <seb128> yes, number of yellow lines basically
[10:18] <marcustomlinson> jamesh: it’s not complete
[10:18] <marcustomlinson> I need to add the existing script logic still
[10:23] <jamesh> marcustomlinson: fair enough.  If all else fails, you could make it a Docker action and just call the existing script
[10:31] <marcustomlinson> I was thinking precisely this :)
[10:40] <seb128> Laney, https://people.canonical.com/~seb128/snaps.html wdyt, better? (it's generated from a smaller script is ignore the upstream versions being faked)
[10:46] <seb128> ricotz, what's up with vala versions, which series are considered stable and unstable?
[10:46] <seb128> ricotz, we are on 0.48 and upstream is at 0.51, I guess we are not updating on purpose? I want to set the correct series on our versions tracking
[10:47] <ricotz> see https://wiki.gnome.org/Projects/Vala
[10:47] <ricotz> I intended to stay on 0.48 on purpose
[10:48] <seb128> ricotz, and you prefer to stick the LTS serie?
[10:48] <seb128> k
[10:48] <seb128> thanks
[10:48] <ricotz> especially for a SRU to focal
[10:48] <seb128> right
[10:48] <ricotz> does this create issues with outdated glib bindings?
[10:49] <seb128> not that I know
[10:49] <ricotz> ok, please let me know if a project decides to require a newer valac
[10:49] <seb128> as said I was just asking because to update https://people.canonical.com/~platform/desktop/versions.html
[10:49] <seb128> ack
[10:50] <ricotz> or things happening like with seahorse
[10:56] <Laney> seb128: that's better! two things - "URL" could probably be something better, and in a few cases (epiphany/arm64, evince/armhf) the links are to the git branch and not a build log, that seems a bit odd
[11:15] <seb128> Laney, thx, the incorrect url was a bug in not handling Cancelled builds, it's fixed now, I replaced URL by Build but I'm not convinced, I need a designer ;-)
[11:17] <ricotz> seb128, oSoMoN, I am going to prepare a fixup for libreoffice 7.1.1~rc2 instead of waiting for 7.1.1 being declared final
[11:17] <seb128> ricotz, alright
[11:28] <ricotz> seb128, oSoMoN, https://people.ubuntu.com/~ricotz/libreoffice/
[11:29] <ricotz> I had this prepared on monday (labeled as final)
[12:17] <ricotz> oSoMoN, are you available to sponsor libreoffice 7.1.1~rc2-2ubuntu1? ^
[12:40] <oSoMoN> ricotz, yes
[12:40] <oSoMoN> let me take a look
[12:51] <oSoMoN> ricotz, it would have been better to use -v to include all the new changelog entries in the source.changes file
[12:54] <oSoMoN> uploaded anyway
[13:07] <ricotz> oSoMoN, appreciated, thank you
[15:28] <hellsworth> good morning desktopers
[15:29] <marcustomlinson> hi hellsworth
[15:29] <oSoMoN> good morning hellsworth 
[15:30] <hellsworth> hi guys!!
[15:32] <didrocks> hey hellsworth 
[15:34] <hellsworth> o/ didrocks :)
[16:29] <jibel> Good morning hellsworth 
[16:37] <hellsworth> bonjour jibel :)
[17:08] <oSoMoN> Trevinho, I intend to look at the gjs autopkgtest failures in the scope of my +1 maintenance shift, unless you are already handling it?
[17:09] <oSoMoN> Trevinho, I'm wondering where in salsa are the changes for 1.67.2-1 ?
[17:09] <oSoMoN> the master branch appears to have only up to 1.66.2-1 (the version in unstable)
[17:25] <oSoMoN> one of the test failures is caused by gjs-tests not installing /usr/libexec/installed-tests/gjs/js/modules
[17:37] <oSoMoN> gjs/testESModules.test is also trivial to fix
[17:37] <oSoMoN> gjs/testIntrospection.test segfaults, looking at that one now
[17:55] <Trevinho> oSoMoN: hey
[17:56] <Trevinho> oSoMoN: sooo... no I wasn't looking at it right now, so thatnks
[17:57] <Trevinho> oSoMoN: and... so it seems i forgot to push to salsa indeed, it's done now.
[17:58] <Trevinho> oh actually no, wait that I've to fix the gbp config
[18:11] <Trevinho> oSoMoN: ok should be good now
[18:20] <oSoMoN> Trevinho, thanks, once I have figured out the three failures I will push fixes and upstream accordingly
[19:28] <Trevinho> cool!
[21:26] <oSoMoN> Trevinho, I filed https://gitlab.gnome.org/GNOME/gjs/-/issues/383 and submitted https://gitlab.gnome.org/GNOME/gjs/-/merge_requests/580 to fix it