== Meeting information == * #ubuntu-meeting: Weekly Ubuntu Foundations team, 24 Jan at 16:03 — 17:20 UTC * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-meeting/2019/ubuntu-meeting.2019-01-24-16.03.log.html]] == Meeting summary == === Lightning rounds === The discussion about "Lightning rounds" started at 16:04. === Release incoming bugs === The discussion about "Release incoming bugs" started at 16:13. * ''LINK:'' http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html#foundations-bugs * ''LINK:'' https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767918 * ''LINK:'' https://gitlab.gnome.org/GNOME/gdm/issues/408#note_360857 === Team proposed-migration report === The discussion about "Team proposed-migration report" started at 16:33. * ''LINK:'' http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#foundations-bugs === AOB === The discussion about "AOB" started at 16:56. == Vote results == == Done items == * (none) == People present (lines said) == * cyphermox (91) * doko (74) * sil2100 (39) * xnox (36) * bdmurray (35) * rbalint (18) * waveform (14) * tdaitx (14) * gaughen (13) * ubottu (12) * juliank (7) * meetingology (3) * cpaelzer (1) == Full Log == 16:03 #startmeeting Weekly Ubuntu Foundations team 16:03 Meeting started Thu Jan 24 16:03:45 2019 UTC. The chair is cyphermox. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 16:03 16:03 Available commands: action commands idea info link nick 16:04 #topic Lightning rounds 16:04 echo $(shuf -e vorlon bdmurray xnox tdaitx doko sil2100 rbalint infinity cyphermox mwhudson juliank waveform) 16:04 xnox infinity waveform sil2100 vorlon cyphermox tdaitx rbalint doko bdmurray mwhudson juliank 16:04 winner is xnox this week. 16:04 oh really 16:04 not fair =) 16:05 not rigged =) 16:05 he is setting up his new router 16:05 * systemd fun -> untangled migrations of related things, now down to just systemd/ppc64el 16:05 xnox: need more time then? 16:05 o/ 16:05 * s390-tools srus 16:05 * upstream upgrades of mdadm/systemd-upstreaming. 16:05 * router hunter 16:05 (done) 16:05 xnox: really? still seeing arm64 16:06 I suspect infinity isn't around? 16:06 okay, I'll go next then 16:06 * RPi.GPIO updated to work on aarch64 but may need SRU? 16:06 yup 16:06 doko, i'm looking to get systemd migrate.... i need it to migrate such that triggered by things get better.... http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#systemd 16:06 * gpiozero updated to work on aarch64. Will either need SRU or backport 16:06 * wiringpi packaging (source v1!) needs updating 16:06 * testing pigpio under aarch64; not working yet 16:06 * tested current released on CM3; works but needs missing device-tree 16:06 * tested current release on 3B, 3B+, 3A+ - working fine 16:06 * still looking at kernel compression 16:07 (done) 16:07 nice 16:07 o/ 16:07 waveform: you missed the archive training ;p 16:07 xnox: Have you seen bug 1811071? also valgrind 16:07 bug 1811071 in The Ubuntu-power-systems project "Ubuntu19.04: valgrind does not properly handle the addex instruction (power9)" [Medium,New] https://launchpad.net/bugs/1811071 16:07 - Many kernel SRU reviews (new cycle) 16:07 - SRU reviews and releases 16:07 - DMB meeting 16:07 - Fixing core18 snap builds caused by a locale-dependent test failing on builders 16:07 - raspi3 'upstreaming': 16:07 * Pushing flash-kernel, raspi3-firmware and Dave's u-boot + irqbalancer to bionic 16:07 * Finished work-around hack for enabling multiverse in gadget tree builds on builders 16:07 * Got working cdimage raspi3 builds for disco 16:07 * Did a manual cpc livefs -proposed enabled raspi3 build - success! 16:07 * Confirmed reported possible issues with using raspi3-firmware on pi3 16:07 bdmurray, yes, valgrind with s390x fixes migrated. should upload that bit too. 16:07 * Prepared an updated linux-firmware-raspi2 + livecd-rootfs in PPA for testing 16:07 * Changed classic pi3-gadget to use different config.txt for armhf and arm64 16:07 - Sent credentials for core-snap rebuilds to CPC 16:07 - Fixed a typo in core-snap rebuilder jenkins script 16:07 - Started looking into trello API and the available Python bindings 16:07 - Sponsored irqbalancer and json-schema-validator for Dave 16:07 - Performed NEW reviews of ec2-hibinit-agent and zhmcclient 16:07 - Performed a few package removals 16:08 (done) 16:08 no vorlon today 16:08 cyphermox: 16:08 - so. much. snow. shoveling. 16:08 - MIR reviews: libimagequant, gnome-remote-desktop, pipewire 16:08 - grub2: SRUs for signature checking, update-grub breadcumbs, LVM menu 16:08 - dkms/shim-signed: preparing SRUs for self-signing process 16:08 - update packagesets for DMB 16:08 ooh ooh, had an awesome meeting with IBM presenting z14 mainframe storage groups, over webex.... because they can't give us access. 16:08 - discussion with Microsoft on processes for shim reviews 16:08 - helping slashd with a new package (sosreport cleaner) 16:08 - reviewing http module to enable for grub EFI images 16:08 (done) 16:09 tdaitx: 16:09 * openjdk-7 security update is on hold 16:09 - hotspot patch backport is kind of a beast 16:09 - upstream should be releasing the security updates soon anyway 16:09 * reviewing failed packages in the bionic rebuild 16:09 - focusing on packages in main or packages that are (b-)deps of other main packages 16:09 Other: 16:09 - travelling Saturday to Europe 16:09 - working half-days next week in UTC+1 timezone, will try to match work time to join the squad/team meetings 16:09 - at FOSDEM in Brussels next weekend and the openjdk unconference on Monday (that translates to 3-5 February) 16:09 (done) 16:09 * partner work 16:09 rbalint: go! 16:09 * fixed meld's dependencies 16:09 * backported wireshark 2.6.6 for *-security 16:09 * fixed a bunch of unattended-upgrades regressions affecting Disco in git 16:09 https://github.com/mvo5/unattended-upgrades/pull/166 16:09 * triaging the kubernetes vs. systemd-resolved issue 16:09 (done) 16:10 - GCC 9 packages are getting ready for upload to disco 16:10 - GCC 8 updates, pending upload 16:10 - openjdk-11 and openjdk-12 updates 16:10 - finally started bionic test rebuilds (archive & planned OpenSSL/OpenJDK/Python/GCC updates) 16:10 - MIR writing / reviews 16:10 - transition fun the whole week ... 16:10 - pestering people about addressing ftbfs and autopkg test failures, within the team and cross team. Not much success for both 16:10 - getting mobbed by desktop team members about my automake workaround 16:10 and how long does http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html take to display for you? 16:10 (done) 16:11 ooh, its me 16:11 fixed Error Tracker mojo specification so it passes CI 16:11 submitted RT re live-ues-foundations Jenkins jobs 16:11 tested multiple systemd-resolved potential fixes for comcast mail servers 16:11 SRU verification of debootstrap for T, X, released B 16:11 rebuilt oops-repository so the Depends on python-cassandra takes 16:11 tested livepatch not available notification for release upgrades 16:11 merged livepatch not available notification to Disco, uploaded SRU for C 16:11 verified livepatch notification bug LP: #1799310 for Cosmic 16:11 Launchpad bug 1799310 in ubuntu-release-upgrader (Ubuntu Cosmic) "No warning when upgrading OS will turn off Livepatch" [Medium,Fix committed] https://launchpad.net/bugs/1799310 16:11 uploaded ubuntu-release-upgrader, update-manager SRUs for 18.04, 18.10 16:11 verified all (so many!) their bugs too 16:11 uploaded intitramfs-tools SRU for 18.04 (LP: #1768230, #1561643) 16:11 Launchpad bug 1561643 in initramfs-tools (Ubuntu Bionic) "initramfs-tools ignores the FRAMEBUFFER option" [High,In progress] https://launchpad.net/bugs/1561643 16:11 Launchpad bug 1768230 in initramfs-tools (Ubuntu Bionic) "Long time booting : Failed to connect to lvmetad. Falling back to device scanning." [Undecided,In progress] https://launchpad.net/bugs/1768230 16:11 ✔ done 16:11 juliank: 16:11 * gnutls28 SRU ploaded 16:11 * apt CVE fix 16:11 * apt 1.8.0~beta1 releasing (lots of small branches merged!) 16:11 * apt hardening work (getting a bit stuck) 16:12 done 16:12 doko: update_excuses takes about 7~10 seconds 16:12 I need a new laptop 16:13 bdmurray, the framebuffer option stuff looks interesting. 16:13 bdmurray, it's "fixed" in disco too? 16:13 doko: why? 16:13 #topic Release incoming bugs 16:13 doko: it is displayed as soon as it starts loading and I can scroll down, still 7~10 seconds to load everything 16:13 doko: 7.67seconds I measured on my t480s 16:13 oh, time to load excuses, ok 16:13 took not long at all here. 16:14 so; let's talk about the 18.04.2 bugs? 16:14 * juliank measured using "Page load time" chrome extension 16:14 bug 1812258 16:14 bug 1812258 in debian-installer (Ubuntu) "Bionic amd64 netboot image has incorrect permissions on kernel" [Undecided,New] https://launchpad.net/bugs/1812258 16:14 I forget where those go again. 16:15 Oh, maybe I should have reloaded. 16:16 cyphermox: What about bug 1772374 for the point release? 16:16 bug 1772374 in OEM Priority Project "ubiquity need mount point /sys/firmware/efi/efivars" [High,Triaged] https://launchpad.net/bugs/1772374 16:16 bdmurray: yes 16:17 thanks for reminding me, I'll get on it right after the meeting 16:17 cyphermox: So no card needed? 16:17 no 16:17 cyphermox: I think xnox merged a ubiquity fix for bionic from slangasek too 16:17 yeah, I'll go have a look at ubiquity in general 16:19 bdmurray, i have merged an duploaded again 16:19 fwiw it's as simple as merging https://code.launchpad.net/~swem/ubiquity/+git/ubiquity/+merge/346666 16:19 it should be in unapproved. 16:19 there is more? 16:19 looking 16:19 xnox: oh, I can do it, no biggie 16:19 seems legit. 16:19 xnox: there is no ubiquity in the bionic queue 16:19 hmmmm 16:20 xnox: What about bug 1776626? 16:20 bug 1776626 in Ubuntu on IBM z Systems "[18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part" [High,In progress] https://launchpad.net/bugs/1776626 16:20 bdmurray, do not care. 16:20 bdmurray, we never actually committed to backport all of that into bionic. 16:22 xnox: What about bug 1760106? 16:22 bug 1760106 in klibc (Ubuntu Cosmic) "FFe: Enable configuring resume offset via sysfs" [Undecided,New] https://launchpad.net/bugs/1760106 16:23 bdmurray, it's in disco, remaining tasks are unimportant. 16:23 bdmurray, i kind of want to drop them to be fair. 16:24 Okay, that was it for me. 16:25 ok 16:25 moving on to DD bugs? 16:25 #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html#foundations-bugs 16:25 i think we could have LP: #1803993 on the radar for bionic, too 16:25 Launchpad bug 1803993 in plymouth (Ubuntu) "Password appears on the VT1 screen" [Undecided,Confirmed] https://launchpad.net/bugs/1803993 16:26 rbalint: AFAIK that was fixed already 16:26 https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767918 16:26 Launchpad bug 1767918 in plymouth (Ubuntu Bionic) "Login password from GDM is shown in plain text on the VT1 console" [High,Fix released] 16:26 *sigh* 16:27 but but plymouth is supposed to be on vt1 16:27 cyphermox, seems like the fix ws not complete 16:27 so should gdm 16:27 why is there like handoff.vt=7 stuck somewhere? 16:27 why, is there like handoff.vt=7 stuck somewhere? 16:27 rbalint: doesn't tell much actually 16:27 https://gitlab.gnome.org/GNOME/gdm/issues/408#note_360857 16:29 cyphermox, it may turn out that the fix was complete, but the newer report seems to be valid 16:29 rbalint: wanna look into it then? 16:30 cyphermox, yes, it sounds important if it is not fixed yet 16:30 xnox agreed to test it 16:31 rbalint: I think what we were trying to say is that it likely is already fixed, and this could be caused by some extra bit laying around 16:31 config and stuff 16:31 like vt.handoff not doing what it should. 16:31 there isn't much new in the dd list 16:31 although bug 1812688 is new 16:31 bug 1812688 in automake-1.16 (Ubuntu) "self-check-report.sh fails on armhf/disco since new year" [Undecided,New] https://launchpad.net/bugs/1812688 16:31 so sounds like xnox will test, and then we can look again 16:32 ok, misunderstanding 16:32 bdmurray: I XFAIL'd it 16:32 rbalint: you want to have a look at plymouth, see if our patch is solid, get more info from the reporter? 16:33 doko: thanks 16:33 ok next topic 16:33 #topic Team proposed-migration report 16:33 cyphermox, i'd try to reproduce then see if the suggestion on gnome's tracker fixes it 16:33 ok 16:34 #link http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#foundations-bugs 16:34 to shorten that ... 16:34 we need systemd migrating, and hints updating 16:34 sil2100: ^^^ 16:35 and blocking issues are: gsequencer coyote idlastro mothur ngraph-gtk redmine gap-io mir 16:35 besides to the latter everything else is unowned 16:35 maybe server cares about redmine 16:35 so https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1812258 commented and marked incompleted 16:35 Launchpad bug 1812258 in debian-installer (Ubuntu) "Bionic amd64 netboot image has incorrect permissions on kernel" [Undecided,Incomplete] 16:36 escalated the kernel not migrating to gaughen and the kernel team 16:37 cyphermox: do you have gaughen powers for this meeting? then please assign people to one of those issues above ;-P 16:38 I don't have super powers, no 16:39 I'm just throwing people under the buses 16:39 systemd sounds like xnox work, and he probably already is on top of it? 16:39 i have local two patches to hopefully unfuck ppc64el 16:41 So who will test e2fsprogs for Bionic? 16:41 so who volunteers for looking at gsequencer coyote idlastro mothur ngraph-gtk redmine gap-io mir 16:41 ? 16:42 I said I'd try to do the patch, I can try to test e2fsprogs on bionic 16:42 I haven't yet blown away my MAAS setup 16:42 cyphermox: okay, great 16:43 I can look at mir 16:44 sil2100: ta, that is entangled with capnproto 16:44 pygments will migrate after new python 16:45 doko: coyote, mothur; maybe 16:46 ok, that leaves gsequencer idlastro ngraph-gtk redmine gap-io 16:46 in Rome they close doors until things are done ... 16:46 idlastro looks to go with coyote for gnudatalanguage tbh 16:47 doko, i take redmine blindly 16:47 rbalint: ta, please coordinate with server (ahasenack, cpaelzer) 16:48 doko, ok 16:48 that leaves gsequencer idlastro ngraph-gtk gap-io 16:48 sil2100, waveform, bdmurray: ^^^ 16:49 doko, I don't see gsequencer on the update-excuses list 16:49 gaughen: you see it on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output_notest.txt 16:50 aaah, I was looking at http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html 16:50 gaughen: and it's on excuses as well, triggered by jack-audio-connection-kit 16:50 I really don't see it on the link I pasted 16:51 gaughen: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html 16:51 ok; we done with proposed-migration? 16:51 we still have gsequencer idlastro ngraph-gtk gap-io unaddressed 16:52 I said I'm taking idlastro too 16:52 sorry, but this sucks. the last two meetings we adjourned this discussion 16:52 and I have one more topic 16:52 ta 16:52 I understand 16:52 fwiw it smells like a gnudatalanguage real regression 16:52 gsequencer ngraph-gtk gap-io 16:53 yep, I already pinged ginggs 16:53 anybody not yet core-dev wants to play? 16:53 waveform: ^^^your turn ;p 16:53 I got the hint ;) Just looking at gap-io to see if I have the slightest clue what's up! 16:54 I'll give that ngraph-gtk a look 16:54 waveform: ta. tbh, no clue what gap-io is at all ;P 16:54 ok, then I take gsequencer 16:55 please note, you can come up with a fix or a work around 16:55 cyphermox: next to AOB? 16:55 waveform: once I untangle mir+capnproto, I can help you out since you're probably new to all this ;) 16:55 yes. 16:55 sil2100, ta :) 16:56 doko, so are they all taken now? 16:56 #topic AOB 16:56 rbalint: we have not investigated redmine yet, just skimmed it and thought it depends on ruby things which are in flight - if you take it (blindly or not) we'd appreciate 16:56 sil2100, did mir get the MIR that they wanted for whatever new mir1.0 release? 16:56 xnox: no clue, I don't follow mir development, I'll just have to look into that 16:56 xnox, sil2100: no, I asked security to priotize today. but it's a ftbfs now as well 16:57 ok, now there is a bionic test rebuild ... http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181220-disco.html 16:57 a lot of regressions ... 16:58 xnox: anyway, I'll be looking at that tomorrow 16:58 doko: bionic or disco test rebuild? 16:58 bdmurray: should I file tagged bug reports so that these get attention within the different teams? 16:58 aohh, wrong URL: http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html 16:59 /usr/lib/bin/capnp: not found 16:59 sounds not fun 16:59 xnox: you want to take mir? 16:59 sil2100, i think so. 16:59 Since you started investigating it now 16:59 cpaelzer, i take a look, maybe some in-flight packages are stuck 16:59 sil2100, i have history 16:59 doko: ^ 17:00 waveform: so maybe I'll pick up gap-io then o/ 17:00 yup, I'll take it 17:00 sorry, meant - no I can take a look 17:01 (til I get horribly stuck and come begging for help :) 17:01 doko, security team has put yaml-cpp on top of the security review queue 17:01 ta 17:02 and we're over time 17:02 anything else to discuss? 17:02 doko, did you get your other topic discussed? 17:02 so what about the bionic ftbfs? 17:02 gaughen: no, not the last one 17:02 they need to be fixed... 17:02 bdmurray, sil2100: so filing tagged reports? 17:03 doko: about the ones in main? 17:03 yes, at least those. 26 ... 17:03 doko: I'll look at libdbusmenu for sure, can look at a few others by the way 17:03 that seems reasonable to me 17:03 we don't have to assign them right now in this meeting 17:03 but yes, they should be fixed 17:04 sil2100: it's not about a single one, but how to proceed 17:04 so how should I tag them? 17:05 I guess bdmurray might have better ideas, but I'd say a 'ftbfs' tag and affecting bionic should be enough? 17:06 bdmurray: ^ what do you think? 17:06 they should show up on the 18.04 LTS report 17:07 sil2100: +1 17:07 doko, are these regressions? 17:08 okay, xnox says yes these are regressions 17:09 doko, do you want to join the voice call? =) 17:09 doko, was bionic ftbfs your last topic? 17:09 doko: we could put them on the .2 milestone as well, but I'd like Adam as the driver to decide if that's the way to go 17:09 So for now I'd say just the tags and nominations 17:09 gaughen: they built before, so yes 17:10 sil2100: can you make show up adam in a meeting? 17:11 gaughen: yes, but I didn't get a reply yet 17:11 doko, hehe 17:11 gaughen: maybe I just tag those as rls-cc-incoming 17:11 cc? 17:11 or whatover this tag is named 17:11 doko: "they need to get done, they will be done on an opportunity basis" is your reply I guess right now 17:12 and tag was rls-bb-incoming / ftbfs / bionic or did I get that wrong? 17:12 I wonder if we use the rls-**-incoming tasks for point releases 17:12 Maybe we should 17:12 IIRC we did 17:12 so how to flag them? 17:12 to some degre anyway 17:12 doko: ok, so fair point, add the rls-bb-incoming tag to it 17:13 worst case is it won't be useful, but at least they will show up on the report 17:13 So ftbfs rls-bb-incoming and a nomination to bionic, for now 17:13 ta. will file these 17:13 ok 17:13 cyphermox: true, I hope Adam looks at that one! 17:14 well; it's useful for anyone who wants to make the release , and later the point release, shinier. 17:14 Anyway, I will from now on for sure 17:14 what I never understand is if I should close the bug task for the development series ... 17:14 doko: if it builds for the dev release, yeah, no? 17:14 well yes, I can check that too 17:14 since fix does not apply to dev release 17:14 anyway, just a guess 17:16 ok; closing meeting then? 17:17 gaughen, cyphermox: we should have a format where things don't fall off 17:17 like rotating the different topics 17:17 doko: sorry, what? 17:17 the format to not drop bugs is the incoming/tracking reports, no? 17:17 doko, you mean topics in our irc mtg here? 17:17 for meetings I use http://people.ubuntu.com/~cyphermox/meetings/foundations.html ; open to additions / changes 17:17 the ftbfs issues were delayed and adjourned for hte last two meetings. that should not happen 17:18 just rotate these topics except for the status reports and aob 17:18 doko: last meeting was special, no managers around. I'm not making decisions for the team without talking to our leaders. 17:18 before last, I don't recall 17:19 * doko ducks. which manager was present this meeting? 17:19 gaughen was. 17:19 I was here this week! 17:19 and I still am 17:19 doko: or is that why you ducked ;D 17:20 anyway, I'd like to stay in the time limits, and address issues not for one area 17:20 anyway, this sounds very #endmeeting 17:20 for just one area 17:20 so if lts issues fall out, that's ok as well 17:20 doko: if you think we should rotate every week so the meeting doesn't take 2 hours, I'm all for it. Let's check with vorlon who usually drives the meeting. 17:20 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)