[02:25] <robert_ancell> kenvandine, snapd-glib 1.56 has a fix for a memory leak. I guess that snap-store will just pick that up on next build?
[06:40] <jibel> Morning everyone
[07:11] <didrocks> good morning
[08:40] <seb128> goood morning desktopers
[08:41] <didrocks> salut seb128
[08:41] <seb128> didrocks, salut, comment ça va ?
[08:42] <didrocks> ça va, et toi ?
[08:43] <Wimpress> Bonjour o/
[08:44] <didrocks> bonjour Wimpress
[08:46] <seb128> ça va ici
[08:46] <seb128> :)
[08:47] <seb128> salut Wimpress
[08:49] <Wimpress> seb128 I filed the bug for nv-codec-headers last night.
[08:49] <Wimpress> https://bugs.launchpad.net/ubuntu/+bug/1866709
[08:49] <seb128> Wimpress, great :)
[08:49] <Wimpress> Does that look correct? Should I also subscribe ubuntu-sponsors?
[08:51] <seb128> Wimpress, not needed, I just commented to say that from a sponsor/archive admin view it's fine, now we need the release team to ack/nack the request
[08:51] <Wimpress> Thanks!
[08:53] <Wimpress> Currently progressing this for Debian too.
[09:04] <Laney> moin
[09:05] <didrocks> hey Laney
[09:12] <seb128> k, back! good morning u.k :)
[09:12] <seb128> hey Laney, how are you today?
[09:14] <Laney> hey didrocks seb128
[09:14] <Laney> yeah doing alright
[09:17] <Laney> seems like there was some kind of incident with some crypt thing
[09:17] <Laney> how are you?
[09:26] <ricotz> good morning desktopers!
[09:26] <ricotz> please sync gnome-builder 3.36.0-2
[09:40] <seb128> hey ricotz, how are you?
[09:40] <ricotz> seb128, hey, I am find, corona didn't get me yet ;)
[09:40] <ricotz> *fine
[09:40] <seb128> :-)
[09:41] <seb128> Laney,  yeah, glibc/libcrypt knocked out the autopkgtest infra, Julian had to rebuild image from eoan apparently, sounds like they had fun fixing it
[09:42] <seb128> LANEYKGB, also your russion spy version is making tab completion on your name annoying :p
[09:42] <Laney> muhahah
[09:43] <seb128> Laney, oh and 3.36 tarballs week, I've updated the trello board, enough cards to have fun :-)
[09:44] <Laney> yeah, I made one of those for gnome-session
[09:45]  * Laney is waiting for some updates to the default extensions ...............
[10:17] <Wimpress> ricotz: o/
[10:20] <ricotz> Wimpress, hi
[10:35] <amurray> Laney: do you know if the glib2.0 parts of LP #1844853 are likely to migrate soon? I noticed your comment#29 said all but eoan can be released... (also do you know the likely timing for eoan)
[10:36] <Laney> hi amurray
[10:37] <amurray> hey Laney :) - there is an open CVE against glib2.0 for eoan/focal so I am thinking if the eoan SRU is not likely to land soon then we will do the GDBusServer fix bit as part of that security fix so we can unblock the ibus update
[10:37] <Laney> I don't know, perhaps we need to ping the SRU team if you need those older series released faster
[10:37] <amurray> but if bionic and xenial are close then we wouldn't bother doing the dbus bits there via -security
[10:38] <amurray> that sounds like it could be worthwhile - would that just be a ping to various individuals in #ubuntu-release or via the launchpad bug?
[10:39] <amurray> Laney: if you could try and prod it along that would be grand
[10:39] <Laney> :(
[10:40] <Laney> RAOF: if you're around, it's your vanguard day apparently - could you check out glib2.0 < eoan pls?
[10:40] <Laney> as you can see I'm being kindly hassled about it
[10:41] <amurray> Laney: thanks! :)
[10:41] <Laney> I was supposed to just be the sponsor for this SRU but I feel like I got left carrying the can on it
[10:41]  * Laney has learned a lesson
[10:41] <amurray> Laney: apologies - if it continues to languish I'll poke GunnarHj in the future
[10:43] <Laney> that's OK, it is our package to own at the end of the day
[10:47] <RAOF> Laney I'm off this week, so I probably won't get to glib, sorry.
[10:48] <Laney> np
[10:48] <RAOF> At least until next week.
[11:53] <KGBaney> glib ubuntu/test b853d2b Iain Lane . * branch deleted
[11:53] <KGBaney> glib ubuntu/test b853d2b Iain Lane . * branch deleted
[11:54] <Laney> wee
[12:49] <tjaalton> if someone has ubiquity git cloned, please drop xkb-data-i18n from the build-deps as it's gone
[12:54] <seb128> tjaalton, the build-depends was no needed? or does it need to be replaced by something else now?
[12:55] <tjaalton> seb128: everything is in xkb-data now, which it already build-depends on
[12:55] <seb128> tjaalton, k, good, I can do that change :)
[12:55] <tjaalton> great, thanks
[12:55] <seb128> np:!
[13:55] <Saviq> didrocks: is there a way to manually prune the zsys snapshots?
[14:00] <didrocks> Saviq: yes! However this is extremely experimental :p
[14:00] <didrocks> Saviq: zsysctl service gc
[14:00] <Saviq> what can go wrong, eh?
[14:00] <didrocks> righttttttt
[14:00] <didrocks> at least, it’s protected against destroying your current mounted dataset :p
[14:01] <Saviq> didrocks: and what does it consider "garbage"?
[14:01] <didrocks> automated snapshots (not taken by you manually) or manual clones, with a decay garbage rules
[14:02] <didrocks> Saviq: the default strategy is available at https://github.com/ubuntu/zsys/blob/master/internal/config/zsys.conf
[14:02] <didrocks> (embeeded in the binary)
[14:02] <didrocks> the spacing strategy for each bucket will be changed in next release
[14:03] <didrocks> to keep a more "balanced" number
[14:03] <didrocks> basically the config is:
[14:03] <didrocks> - keep all snapshots from the last 24h
[14:03] <didrocks> - then keep 3 a day between the 2-7 days
[14:03] <didrocks> - then keep one a day for the previous week
[14:04] <didrocks> (from the previous week to the month before)
[14:05] <didrocks> - then keep one per week for the previous month
[14:05] <didrocks> - then keep one per month for the previous year to -2 years
[14:05] <didrocks> and finally, twice a year for the year before
[14:05] <didrocks> (yes, this was a lot of fun to implement :p)
[14:05] <didrocks> those are targets, meaning, you can have more or less than that
[14:06] <didrocks> (like if you don’t boot your computer for a given period)
[14:06] <didrocks> and some locks can happen if you manually cloned and so on
[14:06] <didrocks> I guess you start to underestand why we didn’t enable it by default yet (but we will for 20.04)
[14:12] <didrocks> no new from Saviq, so either gc worked and he was DDOSed by this explanation or that gc was worse than expected :p
[14:12] <Saviq> still here ;)
[14:12] <didrocks> phew
[14:12] <Saviq> but don't see that gc actually did anything…
[14:12] <didrocks> hum, weird
[14:13] <Saviq> last snap from 29.02
[14:13] <didrocks> you still have that many autozsys_ ?
[14:13] <Saviq> didrocks: https://paste.ubuntu.com/p/GJ94t9C7Rp/
[14:13]  * didrocks looks
[14:14] <Saviq> I suppose that's less than 20
[14:14] <Saviq> so it wouldn't prune
[14:14] <didrocks> right, there is that and it follows the previous rules
[14:14] <didrocks> yeah, when you have more than 20, the duplicated on 03-03 should be pruned
[14:14] <didrocks> but that would be the only ones
[14:15] <Saviq> ack
[14:15] <didrocks> I forget to mention the rules of "keep at least"… :)
[14:15] <didrocks> forgot*
[14:20] <Mirv> wow, I just noticed for the first time you've included the "Ubuntu tone" from Ubuntu Phone in the desktop/installer bootup, and I thought my phone is ringing when starting VM since I've carried over the Ubuntu.ogg from my Meizu Pro 5 Ubuntu Edition to my Android phones :D
[14:24] <hellsworth> good morning desktopers!
[14:30] <seb128> hey Heather, how are you? how is the jet lag?
[14:30] <seb128> oh, meeting time!
[14:30] <hellsworth> oh the jet lag is all gone :)
[14:31] <hellsworth> yes it's nice to have the meeting at this time too (at least for a couple of weeks :) )
[14:31] <seb128> great :-)
[14:31] <seb128> #startmeeting Desktop Team Weekly Meeting - 2020-03-10
[14:31] <meetingology> Meeting started Tue Mar 10 14:31:15 2020 UTC.  The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[14:31] <meetingology> Available commands: action commands idea info link nick
[14:31] <didrocks> Hey hellsworth
[14:31] <hellsworth> hi there didrocks !
[14:32] <seb128> Roll call:  didrocks, duflu (out), heather, jamesh (out), jibel, kenvandine, Laney, marcustomlinson (out), oSoMoN (out), tkamppeter, trevinho, robert_ancell (out)
[14:32] <Trevinho> o/
[14:32] <hellsworth> o/
[14:32] <seb128> I hope everyone travelled back without issue and is feeling good
[14:32] <seb128> hey Trevinho :)
[14:32] <kenvandine> o/
[14:33] <jibel> hi
[14:33] <seb128> k, let's get started
[14:33] <seb128> #topic rls-bb-bugs
[14:33] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[14:33] <seb128> no desktop item
[14:34] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[14:34] <seb128> bug #1866574
[14:34] <seb128> kenvandine, I think Robert intend to do those updates, can you remind him to assign himself when he targets a serie?
[14:35] <kenvandine> i will
[14:35] <seb128> thanks
[14:35] <seb128> bug #1855893 the oem guy who was assigned removed the assignment
[14:36] <seb128> I ping on the bug asking why
[14:36] <seb128> other ones are nm that I sitll need to clear and incomplete ones
[14:36] <seb128> #topic rls-ee-bugs
[14:37] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-incoming-bug-tasks.html
[14:37] <seb128> no desktop item
[14:37] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-tracking-bug-tasks.html
[14:37] <seb128> snapd-glib also there
[14:37] <seb128> & nm
[14:37] <seb128> but otherwise nothing interesting
[14:37] <seb128> #topic rls-ff-bugs
[14:37]  * Trevinho just lost connection, let me know if I lost pings
[14:38] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html
[14:38] <seb128> Trevinho, you didn't
[14:38] <hellsworth> lol
[14:38] <Trevinho> ta
[14:38] <seb128> 23 items, shrug
[14:38] <seb128> k, Daniel nominated half his bugs
[14:39] <seb128> I will skip the gnome-shell stack ones for today and ask Daniel to review/sort those out with Marco for next week
[14:39] <Trevinho> k
[14:39] <Laney> at least https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725180 happened on 2020-02-07 so why are we still looking at it now?
[14:40] <seb128> let's review that one
[14:40] <Trevinho> Laney: I think it depends on latest gjs
[14:40] <Trevinho> but will be addressed anywyas
[14:40] <seb128> I don't think it needs rls tracking, Daniel is obviously on it and gjs will be updated
[14:40] <seb128> I +1 rls-ff-notfixing
[14:40] <Trevinho> yeah, we can
[14:40] <Laney> indeed
[14:41] <seb128> k, done
[14:42] <seb128> bug #1865838
[14:42] <Trevinho> fine with that
[14:43] <seb128> I don't think it's frequent/important enough to be rls targetted
[14:43] <Trevinho> not sure is gdm3 though
[14:43] <seb128> unless oem believe it's important
[14:43] <Trevinho> seb128: ah ok... I assumed that was the case
[14:43] <seb128> Trevinho, that's the one Benjamin gave details about on the upstream report
[14:43] <seb128> I will follow up with oem
[14:43] <seb128> if they want it I said we rls target
[14:43] <Trevinho> well those fprint issues are all per OEM decisions
[14:43] <seb128> otherwise if it's medium important we rls-ff-notfix
[14:44] <Laney> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864052 this one should be assessed
[14:44] <seb128> are we done with the fingerprint one?
[14:45] <seb128> let's stick to what I said for it if no-one disagree
[14:45] <seb128> Trevinho, ^ any input on that gnome-shell?
[14:45] <Laney> umm ok sorry for interrupting, that sounded to me like a decision
[14:45] <seb128> Laney, another reason I wanted to skip the shell ones is that I would guess a part of the issue are fixed in 3.36
[14:45] <seb128> I don't want to 'waste' energy on reviewing things that are already fixed
[14:46] <seb128> we should get those updates out, then we can properly look at remaining issues
[14:46] <Laney> don't agree, but fine
[14:46] <seb128> but if you think we should review that one now it's fine
[14:46] <Trevinho> seb128: I think I did the previous fix for that, should be probably be addresse
[14:46] <seb128> Trevinho, ^ does that ring a bell/any opinion?
[14:46] <Laney> I think there are clearly ones to review in the list
[14:46] <seb128> Trevinho, k, can you assign to yourself and put on your backlog?
[14:46] <Laney> like this one https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825710
[14:46] <Trevinho> k
[14:46] <Laney> obviously gonig to be a notfixing and there's no point skipping it
[14:47] <seb128> k
[14:47] <seb128> let's do this one
[14:47] <seb128> +1 for not-fixing
[14:47] <seb128> others?
[14:47] <seb128> I mean what do others think, I guess it's a no discussion/agreement?
[14:47] <Trevinho> it may be related to the other issue we've in rls tracking that was causing crashes on java apps though
[14:48] <Laney> agreed
[14:49] <Laney> suspicious tag addition imho
[14:49] <Laney> ;-)
[14:49] <hellsworth> from the user perspective, it is an annoying bug/feature
[14:49] <seb128> bug #1859782
[14:49] <seb128> xwayland and need Daniel's eyes to see the issue
[14:49] <seb128> I vote notfixing
[14:50] <Laney> yup
[14:50] <hellsworth> seems pretty minor so i vote notfixing too
[14:51] <seb128> bug #1862308
[14:51] <seb128> notfixing imho, unsure anyone else than Daniel would notice
[14:51] <seb128> and he's assigned/can work on it if he wants anyway
[14:52] <hellsworth> since the wallpaper is the first thing someone sees when they login, i would vote for fixing but it looks like upstream is working on it
[14:52] <hellsworth> so is there anything for us to do anyways?
[14:52] <Laney> he's got a patch that he is arguing to be taken before upstream merges it
[14:52] <Laney> so not sure what the rls angle is there
[14:52] <hellsworth> oh i see
[14:52] <seb128> can you notice it being blurry?
[14:52] <Laney> no
[14:53] <seb128> so I vote notfixing
[14:53] <hellsworth> ok fair enough. looks fine to me :)
[14:53] <kenvandine> me either
[14:53] <seb128> Heather vote fixing
[14:53] <seb128> others?
[14:53] <hellsworth> notfix
[14:53] <hellsworth> i changed my mind
[14:53] <didrocks> agreed on notfix
[14:53] <seb128> k, done
[14:53] <kenvandine> notfix
[14:53] <seb128> bug #1865865
[14:53] <Laney> +1
[14:53] <Laney> also known, also Trevinho is already working on it I think
[14:53] <Trevinho> yeah
[14:53] <seb128> k, wfm
[14:53] <Trevinho> part of the dock fixes
[14:54] <seb128> bug #1866275
[14:54] <Laney> this is one to wait and see if you want
[14:54] <Laney> but if not fixed it should probably be taken
[14:54] <Laney> I'd say
[14:54] <seb128> it seems annoying indeed
[14:54] <seb128> let's target
[14:55] <seb128> I will assign to Daniel since he's less busy than Trevinho
[14:55] <Laney> the upstream bug is still open so seems less likely to be fixed but maybe nobody noticed the issue on gitlab
[14:55] <Laney> thx
[14:55] <seb128> bug #1864127
[14:55] <seb128> osomon said he would look at that but he's out today
[14:55] <Laney> sounds like the same auto refresh thing anyway
[14:56] <Laney> to me
[14:56] <seb128> I will check with him and get it out of the list if that's what he recommends
[14:56] <seb128> yes, same
[14:56] <seb128> bug #1864644	
[14:57] <seb128> I'm not familar enough about what video drivers are 'standard' in vms
[14:57] <seb128> what do other think?
[14:57] <seb128> 1 affected user, no duplicate
[14:58] <seb128> I would vote notfixing on the assuption it's not impacting a lot of users but I'm unsure if that assumption is true
[14:58] <Laney> hmm interesting
[14:59] <seb128> (sorry I'm a virtualbox user :p)
[14:59] <hellsworth> maybe notfix unless others report the issue?
[14:59] <Laney> that sounds like a systemd bug that I fixed in like January, I thought we had it in Ubuntu already
[14:59] <Laney> but it looks like not
[14:59] <Laney> laney@disco (master|…)> git tag --contains 625077264ba01a108386eeea733ee244e6b7ff14                                                                                                                            ~/dev/random/systemd
[14:59] <Laney> v245
[14:59] <Laney> I would say reassign to systemd, and let me comment with the commits they need
[14:59] <seb128> Laney, thanks
[14:59] <Laney> hopefully foundations will pick it up from there
[15:00] <seb128> reassigned
[15:00] <Laney> thx
[15:00] <seb128> I keep the tag so they can review it :)
[15:00] <seb128> bug #1865222
[15:01] <seb128> it seems an annoying issue but I didn't hit it and didn't see other mention
[15:01] <seb128> I would notfix unless/until we get more reports
[15:01] <seb128> wdyt?
[15:01] <hellsworth> agreed
[15:02] <seb128> k, let's do that
[15:02] <seb128> bug #1866194
[15:02] <Beret> uh
[15:02] <Beret> we can't fix https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825710 ?
[15:04] <Eickmeyer[m]> Not sure if I'm barking up the right tree here, but can I get a merge on some changes to the Ubiquity Slideshow for Ubuntu Studio? https://code.launchpad.net/~eeickmeyer/ubiquity-slideshow-ubuntu/ubuntustudio/+merge/380461
[15:04] <seb128> Eickmeyer[m], hey, we are in the middle of a team meeting, and try #ubuntu-devel maybe?
[15:04] <Eickmeyer[m]> seb128: My bad. Thanks!
[15:04] <seb128> Beret, we can but it's too low priority to get the required ressources allocated this cycle, feel free to discuss priorities with Wimpress and get that changed if you wish though :)
[15:05] <Laney> It's really tied up with doing some work on focus stealing prevention imo
[15:05] <seb128> so, that pulseaudio bug
[15:06] <Beret> yeah I guess it would be good to know what it's competing with
[15:06] <Beret> it is annoying
[15:06] <seb128> I will ask questions, I don't have an opinion with the info the bug has
[15:06] <Beret> some apps are worse than others
[15:06] <seb128> Beret, yeah, well the notification is useful, it shouldn't just be displayed as often it is/we have buggy cases
[15:07] <seb128> Beret, so it's not as simple as removing it
[15:07] <Beret> so I don't even know what it means
[15:07] <seb128> if you click on something slooow to start
[15:07] <seb128> let's say eclipse
[15:07] <seb128> and go write an email
[15:07] <seb128> you dont want what you type stop going to the email 30s later
[15:07] <seb128> eclipse should open in the background
[15:07] <seb128> and tell you it is loaded
[15:08] <seb128> now if you click on nautilus and the dialog is displayed the next second it should be in front and not show a notification
[15:08] <Beret> I disagree with that
[15:08] <Beret> if I start an application, I expect it to steal the focus, that's the whole point
[15:08] <Laney> what if it's a telegram snap and it steals your password from the terminal?
[15:09] <Beret> context matters - I *launched the application*
[15:09] <Beret> it's not like it decided to open itself
[15:09] <seb128> well, you do, but then it's so slow to open that you go something else
[15:09] <seb128> like use your command line
[15:09] <Beret> that's fine
[15:09] <seb128> or type a private reply on IRC
[15:09] <seb128> anyway
[15:09] <hellsworth> but the snap might take 15s to start. in that time you go start typing your password in the terminal but partway through the snap does launch, steals the focus, and your pw is printed there
[15:10] <Beret> this is a case in which you're technically correct and practically completely wrong
[15:10] <seb128> did you ever have issue with the focus stealing prevention under unity7?
[15:10] <Beret> no
[15:10] <seb128> had
[15:10] <seb128> see
[15:10] <seb128> and it was present there
[15:10] <hellsworth> perhaps the bug is the best place for the back and forth on what the behavior should be
[15:10] <Beret> so this is broken, we're agreed :)
[15:10] <seb128> just not buggy
[15:10] <seb128> yes
[15:10] <seb128> anyway, it's buggy and we know it
[15:11] <seb128> just dealing with focus is non trivial code and it needs work to be resolved
[15:11] <seb128> so we need resources allocated
[15:11] <seb128> we are not going to resolve that now, but let's discuss with Wimpress later if you want
[15:11] <Beret> ok
[15:11] <seb128> thanks
[15:11] <Beret> yeah, I'd like to know what its competing against
[15:11] <seb128> (also we are in the middle of reviewing champagne bugs as part of our team meeting)
[15:11] <seb128> so let's go back to that :)
[15:12] <seb128> bug #1866194
[15:12] <Beret> even while having this conversation I've had people privately pinging me with "Yes, that's been annoyihng me forever"
[15:12] <Beret> sorry, didn't realize you were in a meeting
[15:12] <Beret> I'll shut up :)
[15:12] <kenvandine> :)
[15:12]  * Beret goes back to his hole
[15:12] <seb128> sooo
[15:13] <seb128> does anyone know if that pulseaudio issue is new/a regression
[15:13] <seb128> or specific to some hardware?
[15:14] <Laney> don't know
[15:14] <kenvandine> actually, this might not even be bluetooth specific
[15:14] <kenvandine> last week i had this issue when plugging in my usb headphones
[15:14] <seb128> sorry it's taking a while today, let's try to finish the rls list
[15:15] <kenvandine> but after unplugging and plugging in again it worked
[15:15] <seb128> I will ask questions/test and let's revisit this one with more data next week
[15:15] <kenvandine> so maybe it's just sound devices add/remove
[15:15] <seb128> right
[15:15] <seb128> if others want to play with that please do
[15:15] <kenvandine> which i think is a regression
[15:15] <seb128> and we discuss it again next week
[15:15] <kenvandine> i'll comment
[15:15] <seb128> thanks
[15:15] <seb128> bug #1866616	
[15:16] <seb128> that one rather looks like a kernel bug to me
[15:16] <seb128> and no proof it's impacting enough users to be rls at this point
[15:18] <seb128> I'm just going to go through the remaining bugs, stop me if you disagree
[15:18] <seb128> (the meeting is getting looong)
[15:18] <seb128> bug #1864274
[15:18] <seb128> it's an understood upstream issue, I will assign to tjaalton
[15:18] <seb128> bug #1865221
[15:19] <seb128> upstream can't reproduce, let's see if 3.36 still has it, doesn't seem import enough to be rls bug anyway
[15:19] <seb128> bug #1847712
[15:19] <seb128> Daniel has a fix proposed, so I'm just going to let it to him
[15:19] <seb128> and target
[15:20] <seb128> and the last 2 are fix commited
[15:20] <seb128> thanks everyone, long review list today
[15:20] <seb128> #topic update_excuses_by_team.html#desktop-packages
[15:20] <didrocks> thanks seb128 for keeping up with it :)
[15:20] <seb128> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#desktop-packages
[15:20] <seb128> Laney, want to do it or should I?
[15:21] <seb128> k, I'm going to assume it's fine if I handle it
[15:21] <hellsworth> libreoffice says it requires icu to migrate but icu isn't in proposed. any advice on how to move forward getting 6.4.1 past this?
[15:22] <seb128> https://launchpad.net/distros/ubuntu/+source/icu
[15:22] <seb128> it's in proposed
[15:22] <Laney> you can
[15:22] <hellsworth> well i take that back. it is in proposed but doesn't seem stuck
[15:22] <Laney> it's reasonably self explanatory anyway this week
[15:22] <hellsworth> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#icu
[15:22] <seb128> it's a candidate
[15:22] <seb128> but it's a transition, all rdepends need to be rebuilt
[15:23] <seb128> see https://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt (but it's difficult to parse/understand)
[15:23] <hellsworth> ok so candidate means it's waiting for depends to be rebuilt
[15:23] <seb128> yes, which the report has a stack, but https://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt basically tell you what is missing
[15:24] <hellsworth> ok thanks for the link
[15:24] <seb128> np
[15:24] <seb128> ideally it would show up on https://people.canonical.com/~ubuntu-archive/transitions/
[15:24] <seb128> otherwise gcr/libsecret build failures are on my plate
[15:24] <Laney> it does
[15:24] <hellsworth> Laney: what might be self explanitory to you might not me to others :)
[15:25] <Laney> hm?
[15:25] <Laney> I was replying to seb128
[15:25] <seb128> Laney, ah, I though it was the previous one since it states 100%
[15:25] <seb128> thanks for pointing that out :p
[15:25] <Laney> np
[15:26] <Laney> that probably means it waiting for some test failures to be resolved
[15:26] <seb128> we need someone to look at ruby-gnome & sphinx on ppc to unblock webkit
[15:26] <seb128> I will add a trello card
[15:26] <seb128> if anyone volunteer feel free to add yourself
[15:26] <seb128> otherwise we will end up volunteering someone :)
[15:26] <seb128> and I think that's it
[15:27] <seb128> #topic AOB
[15:27] <seb128> I will remind the team about GNOME 3.36 & https://trello.com/b/z29JJK3q/gnome-336
[15:27] <seb128> if you want to help that would be welcome
[15:27] <seb128> Trevinho, please get those extension ported sooner than later if you can to unblock shell and co
[15:28] <seb128> also UIF is next week if you have UI changes you still want to do
[15:28] <seb128> and that's it for me
[15:28] <seb128> anyone else with a topic?
[15:29] <seb128> seems not, that's a wrap then
[15:29] <seb128> sorry for the long meeting!
[15:29] <seb128> #endmeeting
[15:29] <meetingology> Meeting ended Tue Mar 10 15:29:14 2020 UTC.
[15:29] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2020/ubuntu-desktop.2020-03-10-14.31.moin.txt
[15:29] <Eickmeyer[m]> Annnd sorry for the interjection. :)
[15:30] <seb128> Eickmeyer[m], no worry, I would say to subscribe ubuntu-sponsors to your mp
[15:30] <seb128> (if that's not done yet)
[15:31] <Eickmeyer[m]> seb128: Yeah, good idea.
[15:31] <seb128> Eickmeyer[m], I will try to take a look maybe later but I'm busy with GNOME updates / meetings and I've unity components on my sponsoring list that came first
[15:31] <didrocks> thx!
[15:32] <Eickmeyer[m]> seb128: No worries. I'm sure somebody could do it.
[15:34] <xclaesse> is it known that devhelp crash when opening any page?
[15:34] <xclaesse> I think it's related to wayland
[15:35] <hellsworth> seb128: so when all of the ongoing transitions are at 100% in https://people.canonical.com/~ubuntu-archive/transitions/, then icu will be migrated and libreoffice should make it past proposed. is that right?
[15:35] <xclaesse> (devhelp:2696801): Gdk-DEBUG: 11:34:31.040: wl_drm@39: error 2: invalid name
[15:35] <xclaesse> Gdk-Message: 11:34:31.040: Error flushing display: Protocol error
[15:35] <xclaesse> On 20.04
[15:36] <seb128> xclaesse,  no known by me but I don't use wayland, I can try later
[15:36] <seb128> hellsworth, it doesn't need all transition, just icu to migrate, but it can be tricky to figure out what is blocked a transition like that one
[15:37] <seb128> hellsworth, #ubuntu-release is working on it, so if you wait a bit it should get sorted out without you having to worry too much about it
[15:37] <hellsworth> sure thing. just wanted to make sure that i wasn't letting it stagnate :)
[15:38] <seb128> it's not
[15:38] <seb128> if you are curious you can look at https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[15:38] <seb128> items like
[15:38] <seb128> ruby-charlock-holmes (0.7.6-1build1 to 0.7.6-1build3)
[15:39] <seb128> Depends: ruby-charlock-holmes icu
[15:39] <seb128> Depends: ruby-charlock-holmes ruby-defaults (not considered)
[15:39] <seb128> Not considered
[15:39] <seb128> are probably things that need resolved
[15:39] <seb128> it's needed for icu
[15:39] <seb128> but also depends on ruby-defaults
[15:39] <seb128> which isn't ready
[15:39] <seb128> which probably means ruby-defaults need to be done as well for icu to migrate
[15:40] <hellsworth> i see
[15:40] <seb128> also boost1.71 it looks like
[15:42] <hellsworth> yeah ok. quite a rabbit hole..
[15:42] <hellsworth> i have really been using update_excuses to look for red items.. but seems there's more introspection to do with it sometimes :)
[15:44] <seb128> right, those transitions can be tricky to sort out, I'm able to poke around and help but I often don't manage to have a clear view of remaining blockers when it's mostly done, it's wizard magic ability to me still :-p
[15:45] <seb128> #ubuntu-release has some people skilled to that who usually get us through the finish line for those things though
[15:45] <hellsworth> ok still, thank you so much for your explanation seb128  :)
[15:48] <seb128> yw!
[16:05] <seb128> bah, I forgot I don't have commit access to ubiquity
[16:05] <seb128> could someone with commit access git am https://people.canonical.com/~seb128/0001-debian-control.patch ?
[16:12] <seb128> xnox, ^
[16:13] <xnox> seb128:  like Laney? =)
[16:14] <xnox> seb128:  i'm not sure if i hate git format-patch more or less than launchpad merge proposal UI!
[16:18] <Laney> GET <url> | git am
[16:18] <Laney> seems easy to me :-)
[16:18] <Laney> done
[16:23] <xnox> Laney:  the ultimate cowboy => piping patches to git am in production
[16:23] <xnox> from curl
[16:24] <Laney> yeah ACTUALLY I just rsynced directly to the Launchpad storage unit
[16:35] <seb128> Laney, thanks :)
[18:15] <GunnarHj> seb128: As regards xkb-data{,-i18n}, the translations are stripped. Is there a reason now to not strip them, as we do with language-selector?
[19:24] <seb128> GunnarHj, dunno, why did we strip them to start with? does it break anything to have them in langpack?
[19:29] <GunnarHj> seb128: My thought was that only a few languages will be available in the installer. (Once installed I see no problem with having them in language packs.)