[07:17] <didrocks> good morning
[07:25] <duflu> Hi didrocks
[07:28] <jibel> good morning
[07:30] <didrocks> hey duflu, jibel
[07:31] <duflu> Morning jibel
[07:46] <frechdachs69> Q: how do I install and use KDM on Xenial? apt-cache does not give me any useful results for kdm?
[07:56] <oSoMoN> good morning
[07:58] <didrocks> hey oSoMoN
[07:59] <oSoMoN> hey didrocks
[08:02] <duflu> o/ oSoMoN
[08:07] <oSoMoN> hey duflu
[08:33] <andyrock> morning!
[08:40] <didrocks> hey andyrock
[08:40] <duflu> Hello andyrock
[08:47] <oSoMoN> morning andyrock
[09:02] <Laney> boop
[09:02] <didrocks> buup Laney
[09:03] <Laney> ßöø?
[09:03] <willcooke> ahoy!
[09:03] <willcooke> jibel, seb128 - who did we say was going to run the meeting today?  Ken?
[09:03] <seb128> hey willcooke
[09:03] <seb128> willcooke, yes, Ken
[09:04] <willcooke> I'll send the reminder now then on his behalf
[09:04] <willcooke> and done
[09:05] <seb128> :)
[09:05] <willcooke> duflu, I love reading your updates.
[09:05] <duflu> willcooke, I can't tell if you're serious
[09:05] <willcooke> Just the right level of detail, and usually good news
[09:05] <willcooke> duflu, totally serious
[09:05] <duflu> Oh, good. Happy Tuesday
[09:06] <willcooke> \o/
[09:06] <seb128> hey duflu
[09:06] <duflu> Morning seb128
[09:06] <didrocks> morning willcooke & seb128
[09:07] <seb128> indeed, nice job on your updates duflu :)
[09:07] <seb128> lut didrocks
[09:16] <Laney> moin willcooke seb128 duflu didrocks
[09:17] <duflu> Hi Laney
[09:17] <andyrock> seb128: hey I found the problem with the udisk MP
[09:17] <andyrock> it was a deadlock not linked with my code
[09:19] <seb128> hey Laney andyrock
[09:19] <seb128> andyrock, oh, nice one!
[10:55] <willcooke> bah
[10:55] <willcooke> The electrician is here today. aka The Prince Of Darkness.  Back online again
[11:06] <ricotz> willcooke, haha, nice word play :)
[11:38] <jbicha> willcooke or seb128: can I drop http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/view/head:/supported-sysadmin-desktop see LP: #1738046
[11:38] <jbicha> good morning
[11:46] <didrocks> good morning jbicha
[12:40] <jbicha> heads up on LP: #1744619 maybe we want to discuss at today's meeting? We'll need to add a Community hub discussion to let Unity in particular know that this is coming
[12:47] <didrocks> good idea jbicha
[12:58] <seb128> hey jbicha
[12:59] <seb128> jbicha, no opinion from me on kickstart
[13:00] <seb128> jbicha, is the libnm-glib removal an upstream move? in which version?
[13:02] <jbicha> it's deprecated and being removed from Debian. The GNOME Shell part is probably landing in 3.28, see GNOME bug 789811
[13:03] <jbicha> gnome-control-center was ported away from libnm-glib sometime before 3.22 (according to the Debian changelog)
[13:22] <seb128> jbicha, that lib is a part of network-manager source no?
[13:22] <jbicha> yes
[13:22] <seb128> is upstream removing it?
[13:23] <jbicha> I don't know, maybe mbiebl knows
[13:23] <seb128> if upstream isn't removing it why do we need to?
[13:24] <jbicha> it's a pain to maintain diffs from Debian for all the NM plugins in Ubuntu
[13:25] <seb128> I don't understand why we need a diff? if they transition them to not use that lib it's fine
[13:25] <seb128> them making plugins not using the lib isn't a reason for having to remove the lib though, is it?
[13:26] <seb128> keeping the lib gives us more option, not less
[13:27] <jbicha> could you ask mbiebl your questions? :)
[13:28] <seb128> mbiebl isn't suggesting we do anything in bionic afaik
[13:28] <seb128> unsure why I would ask him questions
[13:28] <seb128> you are the one who said wanted to discuss the topic
[13:29] <jbicha> actually, he is because those VPN plugins would be autosynced to bionic now if I hadn't added a block-proposed bug
[13:29]  * didrocks understood from the description that the package would be removed from Debian (and so, not coming from upstream), but it seems it's not the case
[13:30] <seb128> jbicha, I don't see the issue of autosyncing the plugins?
[13:30] <jbicha> I know that he held off from pushing the VPN plugins without libnm-glib support until he patched gnome-shell this week
[13:30] <seb128> if they stop using a lib it's fine
[13:30] <seb128> why would that be an issue?
[13:30] <jbicha> my understanding is that gnome-shell's network menu won't display VPNs any more with the Debian VPN packages until we add the gnome-shell patches
[13:31] <jbicha> I don't use VPNs, so I'm kinda guessing here
[13:34] <seb128> https://bugzilla.gnome.org/show_bug.cgi?id=789811 has details
[13:35] <seb128> but basically the issue is that you can't load the gir bindings for the old and new lib
[13:35] <seb128> they symbol conflict or something
[13:35] <seb128> so the shell extensions and code needs to be in sync on which one they use
[13:35] <seb128> nothing requires us to drop libnm-glib though
[13:35] <seb128> that's just a lib, u-c-c can keep using it fine
[13:36] <seb128> the issue is when you mix both in the same process, e.g g-s and plugins
[13:36] <seb128> so to me it seems fine to sync the plugins and include the g-s patch
[13:36] <seb128> we don't need to remove the lib or port u-c-c if nobody has slots to work on that
[13:37] <jbicha> when I asked mbiebl yesterday, he though that u-c-c wouldn't show VPNs (because the Debian VPN packaging drops support for the old library and I think u-c-c never got support for the new library)
[13:40] <seb128> I don't understand that part
[13:43] <seb128> it's also not clear to me that we need to build without -glib support to be able to able to use the libnm code
[14:09] <alan_g> Hi, is there a way to prevent GTK apps drawing shadow decorations? (Preferably an env variable I can set when switching to Mir.)
[14:09] <alan_g> It seems to have been asked on the internet many times without a useful (to me) answer.
[14:21] <jibel> seb128, do we have to wait 7 days to publish update-notifier to the security pocket?
[14:31] <seb128> jibel, that's a question for the security team I guess
[14:31] <kenvandine> meeting time!
[14:31] <seb128> over 1 min!
[14:31] <kenvandine> :)
[14:31] <kenvandine> #startmeeting Desktop Team Weekly Meeting - 2018-01-23
[14:31] <meetingology> Meeting started Tue Jan 23 14:31:35 2018 UTC.  The chair is kenvandine. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[14:31] <meetingology> Available commands: action commands idea info link nick
[14:31] <oSoMoN> bad karma for you Ken
[14:31] <didrocks> hey hey
[14:31] <jbicha> o/
[14:31] <oSoMoN> o/
[14:31] <kenvandine> Roll call: andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel/heber, kenvandine, laney, oSoMoN, seb128, tkamppeter (out), trevinho, robert_ancell (out)
[14:31] <seb128> hey :)
[14:31] <andyrock> o/
[14:31] <Trevinho> o/
[14:32] <Trevinho>  /o/
[14:32] <jibel> o/
[14:32] <heber> o/
[14:32] <kenvandine> #topic andyrock
[14:33] <andyrock> 1. Fixed udisks patch to remove a deadlock that was causing failing tests (the problem was already there but never triggered)
[14:33] <andyrock> 2. Working on integrating canonical-livepatch in the installer
[14:33] <andyrock> 3. Investigating what needs to be done in order to provide a Ubuntu SSO experience with gnome-online-accounts
[14:33] <andyrock> eow
[14:33] <kenvandine> thanks
[14:34] <kenvandine> #topic dgadomski
[14:34] <dgadomski> hey
[14:34] <dgadomski> working on bug #1644662 and bug #1743422
[14:34] <dgadomski> eof
[14:34] <kenvandine> cool
[14:34] <kenvandine> #topic didrocks
[14:34] <didrocks> * Rebased ubuntu dock on latest master + some bug fixes. Uploaded to bionic.
[14:34] <didrocks> * Contributed to travis.debian.net to support ubuntu! Hook that up in the communitheme work (to ensure every PR can at least build the sass code): https://github.com/lamby/travis.debian.net/pull/56 and https://github.com/lamby/travis.debian.net/pull/55.
[14:34] <didrocks> * Pinged on the session discussion, didn't hear back yet. Meanwhile, implemented the "can disable session mode extension" instead of forcing them, and ensure -prefs reflect the correct status. This was the minimal agreement. Also, the widgets are disabled in -prefs if the gsettings keys aren't writable. Will need to update Tweaks and chrome extensions for this, but wait on upstream's feedback.
[14:34] <didrocks> * Was pinged by Google as our codelab markdown support (https://tutorials.ubuntu.com) is better than their. They want it for Google I/O. I didn't have time to write tests at the time that's why I didn't contribute it back (I have other contributions to upstream codelabs). They will write the tests, so rebased and opened https://github.com/googlecodelabs/tools/pull/33.
[14:34] <didrocks> * Got an icon and pinged again upstream for sound above 100%. Now, it's on the GNOME Shell review list!
[14:34] <didrocks> * Look and read various changes proposed at GNOME Shell design hackfest.
[14:34] <didrocks> * GCI finale reviews and help and cast my vote for winners.
[14:34] <didrocks> * GNOME Todos MIR.
[14:34] <didrocks> ?
[14:34] <didrocks> . ;)
[14:35] <kenvandine> thx didrocks
[14:35] <kenvandine> #topic duflu (out)
[14:35] <kenvandine> * PulseAudio update 1:11.1-1ubuntu4
[14:35] <kenvandine>   - Stuck in proposed due to never-ending testing? http://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#pulseaudio
[14:35] <kenvandine> * Bluetooth:
[14:35] <kenvandine>   - Not really bluez, but FYI a major fix for Bluetooth on artful with Intel 8260/8265 (ie. impacting many systems) was released this week: https://launchpad.net/bugs/1729389
[14:35] <kenvandine> * Unresponsive touchpads (https://launchpad.net/bugs/1696929)
[14:35] <kenvandine>   - Put together a new patch for bionic, and tested on some laptops.
[14:35] <kenvandine>   - Now in proposed!, again: https://launchpad.net/ubuntu/+source/libinput
[14:35] <kenvandine> * Gnome Shell performance work:
[14:35] <kenvandine>   - Great progress this week in reducing gnome-shell's CPU usage. Proposed two upstream fixes: https://launchpad.net/bugs/1743976
[14:35] <kenvandine>   - Stuttering: Annoyingly I've found app stuttering is completely consistent, but also machine-specific and app-specific. Each machine stutters reliably on its own period, different to other machines. So I'm still trying to narrow down all the variables. Also still considering the possibility that high CPU (or realtime blockage) is related.
[14:35] <kenvandine> * Gnome Shell minor visual fixes:
[14:35] <kenvandine>   - Upstream fix pending (also helps reduce CPU usage): https://bugs.launchpad.net/gnome-shell/+bug/1744001
[14:35] <kenvandine> * Daily bug management across gnome-shell, mutter, gdm3, ubuntu-themes, bluez, pulseaudio, dkms, mir, wayland, totem, mpv, libinput.
[14:35] <kenvandine> * HELP: Fixes still awaiting sponsorship:
[14:35] <kenvandine>   - https://code.launchpad.net/~vanvugt/gtk/fix-1698270/+merge/331846
[14:36] <kenvandine>   - https://code.launchpad.net/~vanvugt/totem/fix-1502476/+merge/333195
[14:36] <kenvandine> whoops... that was racy :)
[14:36] <kenvandine> #topic jbicha
[14:36] <jbicha> • Migrated Debian GNOME git repos from Alioth to https://salsa.debian.org/gnome-team/
[14:36] <jbicha> • Also helped Debian Fonts team with migration to Salsa
[14:36] <jbicha> • Renamed d-conf source package to dconf to match upstream name and hopefully eventually reduce confusion. Same for gnome-orca → orca (in bionic NEW)
[14:36] <jbicha> • Uploaded gnome-terminal 3.26 after Egmont Koblinger fixed our pcre2-revert patch for vte2.91 0.50.
[14:36] <jbicha> • Packaged woff2 and filed MIR LP: #1742743 (needed for webkit2gtk soon)
[14:36] <jbicha> • Debian GNOME team has adopted bijiben, geary, and gnote
[14:36] <jbicha> • Sponsored the ibus-libpinyin and friends packages that GunnarHj requested last week
[14:36] <jbicha> • Looking into libnm-glib issue with NetworkManager VPN plugins LP: #1744619
[14:36] <jbicha> eof
[14:36] <kenvandine> thx
[14:36] <kenvandine> #topic jamesh (out)
[14:36] <kenvandine> - At linux.conf.au this week, and snapcraft summit next week
[14:37] <kenvandine> #topic jibel/heber
[14:37] <jibel> -Investigated bug 1648534 and concluded that part of the problem is caused by out of date packages. The theory is that part of the problem is due to update notifications not triggered when there are updates availabled. Verified the fix proposed by seb128. Waiting for publication to the security pocket
[14:37] <jibel> - Bootspeed: Looking into gnome-shell startup time.
[14:37] <jibel> - Users of EOL releases with third party source configured cannot updated to a newer release. Triaged upgrade bug 1744722 and working on a fix. It’s preventing users of EOL release with third party sources configured to upgrade to a newer release.
[14:37] <jibel> - When ubiquity crashes during installation, the apport hook fails to attach syslog. Fixed it (bug 1582950)
[14:37] <jibel> Fixing/making more stable gnome-software tests submitted by GCI  (we have a total of 19 new tests from participants)
[14:37] <jibel> Test new version of bluez snap 5.48
[14:37] <jibel> - Daily bug triage
[14:37] <jibel> ..
[14:38] <seb128> jibel, did you write down your gnome-shell/startup finding somewhere?
[14:38] <seb128> is that g-s session or just the shell binary?
[14:38] <jibel> seb128, not yet, I just started last week
[14:38] <jibel> seb128, just the shell binary
[14:39] <jibel> it's the main consumer from boot charts
[14:39] <seb128> k
[14:39] <kenvandine> thx
[14:39] <kenvandine> #topic kenvandine
[14:39] <kenvandine> -  Updated the gnome-software SRU fixing bug 1690280
[14:39] <kenvandine> - Worked on getting builds of the reverse depends needed for a gnome-software classic snap
[14:39] <kenvandine> - Backported gtkmm and depends to the gnome-3-26 PPA to ease getting the new gtk3 inkscape snap built and in the store
[14:39] <kenvandine> #topic laney
[14:40] <Laney> o Finished build system / integration work for systemd user session stuff, pushed branches upstream, waiting for some (any!) comments
[14:40] <Laney> o Started investigating gnome clocks alarm systemd stuff which should work when the above is integrated, some outstanding questions around timezones but can get going on this
[14:40] <Laney> o Bit of autopkgtest maintenance, turned s390x back on, waiting for rest of the clouds to be fixed before we can turn the other arches on again. proposed is going to be a bit of a mess, should probably help cleaning that out
[14:40] <Laney> o Some random discussions on using git in the team
[14:40] <Laney> ?
[14:41] <kenvandine> thx
[14:41] <kenvandine> #topic oSoMoN
[14:41] <oSoMoN> hey
[14:41] <oSoMoN> • firefox
[14:41] <oSoMoN>   ∘ tested latest snap build, looks good except for localization (regression, already fixed in master)
[14:41] <oSoMoN> • chromium
[14:41] <oSoMoN>   ∘ updated stable to 63.0.3239.132 in bionic, still waiting on autopkgtests for arm* to run before it migrates from -proposed
[14:41] <oSoMoN>   ∘ updated snap in candidate channel and issued call for testing: https://forum.snapcraft.io/t/call-for-testing-chromium-63-0-3239-132/3627
[14:41] <oSoMoN>   ∘ updated beta to 64.0.3282.99 and snap in beta channel
[14:41] <oSoMoN>   ∘ updated dev to 65.0.3322.3 and snap in edge channel
[14:41] <oSoMoN>   ∘ finished patch to allow searching for the widevine CDM libs in $HOME/.local/lib, to make this mechanism snap-friendly (currently beta and dev branches)
[14:41] <oSoMoN>   ∘ fixed bug #1742653
[14:41] <oSoMoN>   ∘ tested again accessibility with local build of 65.0.3315.3, still not working (no ATK events at all seen on chromium application), reported to upstream
[14:41] <oSoMoN> • libreoffice
[14:41] <oSoMoN>   ∘ tested snap build of 6.0.0, need to investigate further some unit test failures
[14:41] <oSoMoN>   ∘ looking into 5.4.4 bionic autopkgtest failures, it appears my apparmor profile fixes are to blame
[14:41] <oSoMoN> That's all folks 🐰
[14:41] <kenvandine> :)
[14:42] <kenvandine> #topic seb128
[14:42] <seb128> • travelled to CapeTown with the flu, that was no fun
[14:42] <seb128> • mid-cycle sprint/review of the plans, no surprises but some new work added to our list (mostly reasonable installer changes, see trello)
[14:42] <seb128> • looked at why we are still getting report from an old gnome-software/xenial version, SRUed a potential update-notifier fix that should resolves cases where users don't get update-manager auto-opened
[14:42] <seb128> • travelled back without the flu this time, that was better ;)
[14:42] <seb128> • reported some of the .config dir permissions issues upstream, they are not convinced it makes a difference if .config is readable or not if other user dirs are
[14:42] <seb128> • post-travelling emails/catchup
[14:42] <seb128> • irc discussions (git workflow,
[14:42] <seb128> nmglib, etc)

[14:42] <kenvandine> the flu... yuck!  glad you're feeling better now!
[14:42] <seb128> thx!
[14:42] <kenvandine> #topic tkamppeter (out)
[14:42] <kenvandine> - systemd: Tests for finding out why auto setup of USB printers stopped working in Artful. Problem was that device does not get unregistered from systemd when unplugging. Updated to Bionic and problem went away.
[14:42] <kenvandine> - system-config-printer: Updated UDEV rules and systemd unit file to upstream-supplied ones as these work around the quoting/unquoting problem of systemd (bug 1721839).
[14:42] <kenvandine> - system-config-printer: Updated ippusbxd support patch to only start ippusbxd when printer is not HP (HPs get set up with HPLIP to make scanning work) and to not create a queue when ippusbxd is used as cups-browsed or CUPS creates a queue then.
[14:42] <kenvandine> - ippusbxd: Released upstream version 1.32: Minor changes, mostly bug fixes and documentation.
[14:42] <kenvandine> - CUPS/cups-filters: Tests and fixes on color space and color depth support in auto-generated PPD files for driverless printers. Reported bugs to CUPS upstream, they are fixed now.
[14:43] <kenvandine> - Bugs.
[14:43] <kenvandine> #topic trevinho
[14:43] <Trevinho> · Fixed a glib-appstream crash:
[14:43] <Trevinho>   https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1744941
[14:43] <Trevinho> · Rework for various JS fixes patch:
[14:43] <Trevinho>   https://bugzilla.gnome.org/show_bug.cgi?id=791233
[14:43] <Trevinho> · Fixed various workspace and and thumbnails positioning issues:
[14:43] <Trevinho>   https://bugzilla.gnome.org/show_bug.cgi?id=792687
[14:43] <Trevinho> · Fixed bug causing a window to be wrongly positioned in activities
[14:43] <Trevinho>   https://bugzilla.gnome.org/show_bug.cgi?id=792681
[14:43] <Trevinho> · Fingerprint: prepared some pam settings, doing some testing
[14:43] <Trevinho> · Fixed a GtkCssProvider issue ignoring theme changes when using named
[14:43] <Trevinho>   themes (for mutter frame theming)
[14:43] <Trevinho> · Reload mutter frames on theme changes
[14:43] <Trevinho> 🏓
[14:43] <kenvandine> thx
[14:44] <kenvandine> #topic robert_ancell (out)
[14:44] <kenvandine> - Guest session work
[14:44] <kenvandine> - GNOME Software work
[14:44] <kenvandine> - LightDM 1.18.4, 1.24.1, 1.25.1 releases
[14:44] <kenvandine> - Simple Scan 3.26.3 release
[14:44] <kenvandine> #topic aob
[14:44] <jbicha> seb128: do you plan to enable bionic langpacks soon?
[14:45] <seb128> jibel, I was waiting on the launchpad team to do an export, I emailed them a few weeks ago
[14:45] <seb128> seems like they didn't reply to my email but did an export on thursday now
[14:46] <seb128> so I'm add that to my list for this week
[14:46] <jbicha> thanks
[14:46] <seb128> yw, thanks for pointing that out
[14:46] <kenvandine> anything else?
[14:46] <sil2100> Sorry to interrupt
[14:46] <kenvandine> hey sil2100!
[14:47] <kenvandine> #endmeeting
[14:47] <meetingology> Meeting ended Tue Jan 23 14:47:06 2018 UTC.
[14:47] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2018/ubuntu-desktop.2018-01-23-14.31.moin.txt
[14:47] <willcooke> thanks everyone
[14:47] <seb128> urg
[14:47] <sil2100> seb128: the bionic langpack exports are now weekly + I set up l-o-m to do a langpack run on the next day, we're using the schedule of yakkety now
[14:47] <kenvandine> sil2100, not interrupting at all :)
[14:47] <seb128> I though jbicha wanted to discuss nm-glib?
[14:47] <kenvandine> oh...
[14:47] <kenvandine> sorry
[14:47] <kenvandine> i thought i waited long enough :)
[14:48] <didrocks> I don't know if the previous discussion was already enough and derailed the aob ;)
[14:48] <seb128> sil2100, k, it's annoying how guys are doing those changes and keep us out of the loop, I had emailed wgrant mid decembre about that and never got a reply
[14:49] <seb128> sil2100, anyway, I consider then that you handle langpacks/translations and I stop carring then, one less thing to do :)
[14:50] <didrocks> (that should have been a \o/)
[14:50] <seb128> lol
[14:51] <seb128> jbicha, didrocks, bottom line on that nm-glib issue from what I understood is that g-s/plugins need to use the same code, we don't need to drop nm-glib since it doesn't hurt having it around, but somebody needs to investigate the impact on unity and if people have time to fix u-c-c/how much of an issue that is for their team
[14:52] <seb128> solutions probably include re-enable the nm-glib code in the plugins (if that doesn't lead to issues with g-s)
[14:53] <sil2100> seb128: sorry about that! I just didn't know who's responsible for those actually, making sure the langpacks are up and running was in the release checklist so I 'followed' :(
[14:53] <seb128> GunnarHj, jbicha, seems like sil2100 took over langpacks so if you have questions/issues with those in the futur he's the one to redirect complains to
[14:53] <seb128> sil2100, pitti handed that over to me when he left so I've been looking after it, but you taking over is fine
[14:53] <sil2100> seb128: the LP team already prepped everything beforehand, then they seemed to be waiting for someone to give them green light
[14:53] <seb128> pitti, sorry for the ping :)
[14:53] <pitti> seb128: don't be; nice to see that they stay in good hands :)
[14:54] <seb128> sil2100, as said, I email them and they never bothered replying
[14:54]  * pitti hugs sil2100 and se128
[14:54] <seb128> pitti, :)
[14:54] <pitti> and seb128 too
[14:54]  * seb128 hugs pitti
[14:54]  * sil2100 hugs pitti and seb128 
[14:54] <sil2100> Hug party!
[14:54] <pitti> seb128: in fact, I got a few "udisks" pings from the meeting and was secretly reading along
[14:54] <seb128> haha
[14:54] <kenvandine> :)
[14:54] <seb128> andyrock has been doing good work :)
[14:54] <sil2100> seb128: anyway, I can surely help with langpacks as I have some bare knowledge, but didn't mean to snatch that from you if you're the driver
[14:55]  * pitti hugs andyrock too then :)
[14:55] <andyrock> :D
[14:55] <seb128> sil2100, well you just did so congrats on the new reponsability :)
[14:55] <pitti> sil2100: I figure it's much more of a hot potato than a trophy :)
[14:55] <sil2100> seb128: I... I don't think I actually want that ;p
[14:55] <jbicha> pitti: don't tell him! ;)
[14:55] <seb128> sil2100, too late :p
[14:56] <sil2100> seb128: but seriously speaking, if you want I can indeed pick this up, but I hope you won't mind me poking with questions?
[14:57] <seb128> sil2100, well, I don't care either way, I just want those "doing conflicting working without talking to each others" to stop, that already happened previous cycle
[14:57] <seb128> sil2100, so I let you drive
[14:57] <seb128> sil2100, feel free to ask if you have questions
[14:57] <seb128> working->work
[14:58]  * pitti reads https://usn.ubuntu.com/usn/usn-3531-2/ , what a mess..
[14:58] <sil2100> seb128: thanks and again, sorry about that
[14:58] <seb128> no worry
[14:58] <sil2100> Seems like I sometimes suck in checking if work is not duplicated, eh
[14:58] <seb128> sil2100, so when do you plan to do a base upload to bionic?
[14:59] <pitti> mdeslaur: ... so away with microcode, and retpoline it is? :/
[14:59] <seb128> sil2100, also https://dev.launchpad.net/Translations/LanguagePackSchedule still has RTM slots, shouldn't we stop those?
[14:59] <tkamppeter> kenvandine, can you have a look at my packages in NEW: cpdb-libs, cpdb-backend-cups, cpdb-backend-gcp?
[14:59] <seb128> pitti, I though retpoline was more complex and less safe and such not plan A, did that change?
[14:59] <kenvandine> tkamppeter, i'm not an archive admin
[15:00] <kenvandine> tkamppeter, maybe seb128?  please? :)
[15:00] <pitti> seb128: right, and AFAIUI it actually requires rebuilding everything
[15:00] <sil2100> seb128: I think they're not actually used on the crontab, just the document needs refreshing - as for the base packs, I guess since I just got a new thing on my plate, I'll try running the base packs this week
[15:00] <pitti> seb128: but I thought plan A (microcode) just got pulled
[15:00] <tkamppeter> seb128, can you have a look at my packages in NEW: cpdb-libs, cpdb-backend-cups, cpdb-backend-gcp?
[15:00] <pitti> not that I would know plan B or C, I'm just curious
[15:00] <sil2100> seb128: I'll keep you in the loop
[15:00] <seb128> kenvandine, tkamppeter, I can add to my list but unsure when I will get to it
[15:01] <seb128> sil2100, thanks
[15:01] <tkamppeter> seb128, will it be possible to get it into 18.04, including the MIR afterwards?
[15:01] <seb128> pitti, I'm curious as well, I've no idea if plan A got pulled or just needs another better iteration
[15:02] <pitti> seb128: yeah, let's hope for a fixed µcode..
[15:02] <seb128> pitti, my understanding was that retpoline was also tricky to get right because any third party module not rebuilt with it could screw your security
[15:02] <pitti> rebuilding the entire release would be a helluva security update..
[15:03] <pitti> although it probably doesn't matter for 95% of teh archive, but identifying the 5% that do seems awfully tricky too
[15:03] <seb128> tkamppeter, that I don't know, depends of how busy the MIR team is and what the review outcome is, also it's new code so unsure it has been tested enough to be included in a LTS during the same cycle
[15:03] <seb128> pitti, right :/
[15:03] <pitti> time to dust off my old Pentium 60?
[15:03] <mdeslaur> pitti: updated microcode will come back, as it's useful for userspace and for hypervisors
[15:04] <mdeslaur> pitti: retpoline doesn't cover all use cases
[15:04] <pitti> mdeslaur: ah good, so still plan A v2.0
[15:04]  * pitti hugs mdeslaur too, "good" times to be in security teams
[15:04]  * mdeslaur hugs pitti 
[15:04] <mdeslaur> :)
[15:06] <pitti> mdeslaur: but still, my impression is that by far the biggest real-life door for this are (1) JS code and (2) untrusted VMs, right? and (1) has been thwarted by browsers by reducing the timer precision
[15:06] <pitti> so I guess for pretty much all client computers there's no reason to panic
[15:06] <pitti> (servers running cloud stuff are a different issue, of course)
[15:07] <pitti> (one of my favourite fixes recently - make computers compute less correctly to *improve* things)
[15:11] <tkamppeter> seb128, if it does not work, then we make it a central project of 18.10 and schedule the needed steps in Budapest, especially to get time slots at the NEW and at the MIR team.
[15:11] <seb128> tkamppeter, NEW and MIR are not the issue there, it's going to get done
[15:12] <seb128> tkamppeter, but it seems risky to want to make new/untested code be added and used by default during the LTS cycle
[15:12] <tkamppeter> seb128, OK, this I understand.
[15:16] <kenvandine> seb128, can you please reject my packagekit upload to xenial
[15:16] <kenvandine> seb128, i put the ppa arg after the changes file in my dput :)
[15:16]  * kenvandine grumbles
[15:17] <seb128> kenvandine, done
[15:17] <kenvandine> seb128, thx!
[15:17] <seb128> yw!
[15:19] <kenvandine> i haven't made that mistake in years...
[15:20] <Laney> at least it was a frozen suite :P
[15:20] <kenvandine> Laney, indeed
[15:21] <Laney> if you use ~ppa versions and dput-ng then you get an error when doing that
[15:21] <kenvandine> oSoMoN, the chromium snap must have updated. it's been a while since the icon has lost it's mind :)
[15:21] <kenvandine> Laney, oh... dput-ng?
[15:21] <kenvandine> never heard of that
[15:22] <oSoMoN> kenvandine, yes I published a few updates yesterday and today, which channel?
[15:22] <kenvandine> edge
[15:22] <Laney> kenvandine: yah, dput with safety checks
[15:22] <oSoMoN> right, I updated it a couple of hours ago
[15:22] <Laney> don't think it would have saved you in this case tho
[15:22] <kenvandine> Laney, excellent, i'll have to switch :)
[15:22] <kenvandine> yeah, i had xenial in the version :)
[15:22] <kenvandine> not ~ppa
[15:23] <kenvandine> i haven't made this goof up since the precise cycle, so i don't do it often :)
[15:23] <Laney> there's this thing that can happen in Debian
[15:24] <kenvandine> and it was an upload that i was confident was going to go to precise, just wanted to test in a ppa first :)
[15:24] <Laney> if you use sbuild to build your changes file (e.g. sbuild -d unstable) then this is the target your upload gets, regardless of what the changelog says
[15:24] <Laney> lots of uploads end up accidentally going to sid instead of experimental because of this
[15:24] <kenvandine> ugh
[15:24] <Laney> but dput-ng catches that one :-)
[15:25] <Laney> I did that with glib2.0 a few years ago
[15:25] <Laney> epic fail
[15:25] <Laney> was during the freeze too
[15:25] <kenvandine> excellent
[16:12] <GunnarHj> jbicha: Problems. qtwebengine-opensource-src has not been built in ppc64el and s390x. Not sure what the proper resolution is. One way might be to not build fcitx-libpinyin in those architectures.
[16:12] <GunnarHj> https://launchpad.net/ubuntu/+source/fcitx-libpinyin/0.5.2-1~exp1/+build/14263698
[16:12] <GunnarHj> https://launchpad.net/ubuntu/+source/qtwebengine-opensource-src/5.9.3+dfsg-0ubuntu1
[16:14] <jbicha> GunnarHj: you'll just need to ask a member of ~ubuntu-archive to remove the ppc64el/s390x binaries for those arches
[16:15] <jbicha> qtwebengine-opensource-src has a lot of rdeps so we've had to do that often already
[16:15] <GunnarHj> jbicha: Without modifying debian/control?
[16:17] <jbicha> yes, if qtwebengine ever supports additional arches, we'll get those binaries built almost automatically then :)
[16:17] <GunnarHj> jbicha: Ok, I'll ping someone.
[16:27] <GunnarHj> Hi seb128: Can you please remove the ppc64el/s390x binaries for fcitx-libpinyin from the archive, so the other architectures make it to -release. (fcitx-libpinyin depends on binaries from qtwebengine-opensource-src.)
[16:27] <GunnarHj> https://launchpad.net/ubuntu/+source/fcitx-libpinyin/0.5.2-1~exp1
[19:33] <willcooke> Night all.  Wont be around tomorrow morning on IRC but will be on Telegram.