=== cpaelzer__ is now known as cpaelzer [15:01] * vorlon waves [15:01] o/ [15:01] o/ [15:02] #startmeeting Weekly Ubuntu Foundations team [15:02] Meeting started Thu Jul 11 15:02:05 2019 UTC. The chair is vorlon. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [15:02] Available commands: action commands idea info link nick === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | be nice | Weekly Ubuntu Foundations team Meeting | Current topic: [15:02] #topic Lightning rounds === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | be nice | Weekly Ubuntu Foundations team Meeting | Current topic: Lightning rounds [15:02] echo $(shuf -e vorlon bdmurray xnox tdaitx doko sil2100 rbalint infinity cyphermox mwhudson juliank waveform) [15:02] bdmurray juliank xnox rbalint tdaitx infinity doko sil2100 waveform cyphermox vorlon mwhudson [15:02] fixed a Traceback in retracing retry code, submitted RT re production update of daisy [15:02] investigated amd64 queue growth, updated daisy to save core files in another case [15:02] submitted RT regarding cassandra write timeouts [15:02] converted more of oops-repository from using pycassa to python-cassandra [15:02] sponsored gdb 18.04 SRU for manoj [15:02] uploaded better fix for motd-news.timer, wrote test case too (LP: #1829968) [15:02] Launchpad bug 1829968 in base-files (Ubuntu Bionic) "motd [on at least some instances] does not auto-update daily" [High,Fix committed] https://launchpad.net/bugs/1829968 [15:02] uploaded findutils with a change so that command-not-found will not suggest locate (package) [15:03] documented / carded additional mlocate work [15:03] tested and worked with Laney on his changes to whoopsie [15:03] created a different PPA with Error Tracker packages for staging [15:03] done [15:03] Not really here, see https://wiki.ubuntu.com/JulianAndresKlode/Status/1907 [15:04] * juliank is running around finding groceries for dinner :( [15:04] xnox is out [15:04] rbalint: [15:05] * released unattended-upgrades 1.13 via Debian with a few more fixes [15:05] * released shadow 1:4.7-1 via to Debian [15:05] * sponsored & SRU-d LP: #1835809 [15:05] Launchpad bug 1835809 in systemd (Ubuntu) "AMD Ryzen 3000 series fails to boot" [High,In progress] https://launchpad.net/bugs/1835809 [15:05] * setting up https://wiki.ubuntu.com/WSL and other WSL related tasks [15:05] (done) [15:05] * jck 11 [15:05] - testing different jti templates (ie. jck settings) [15:05] - setting up for manual tests [15:05] (done) [15:05] Guess no doko and no infinity [15:05] So it's me [15:05] - Some stomach problems this week [15:06] - SRU reviews and releases [15:06] - New core18 release phasing [15:06] - Kernel SRUs [15:06] - Rust 1.35.0 update: [15:06] * Wasting some time working on an out-of-date version [15:06] * Pulling new upstream, refreshing patches, building tarballs [15:06] * Preparing new cargo, updating the patches, lots of hacking of orig-vendor [15:06] * Asked Olivier for help testing - firefox successfully built and ADT tests passing [15:06] * Uploaded to eoan [15:06] * Prepared backports, sent to a Bileto PPA, ready for copy to archive and/or rust PPA [15:06] - ubuntu-core gadget updates: [15:06] * A few PRs, working through snap build failures [15:06] * Promoting snaps to beta [15:06] - Final tweaks to the new automated infra for core18 snap promotion - all working now [15:06] - Investigating issues with SRU ADT failure comments sent when there are no failures [15:06] - Friday: working half-day only [15:06] (done) [15:06] waveform: [15:06] * Chased licensing on libraspberrypi0 for Pi spec (related to bug #1819444); seems to be some confusion upstream as to where the source for the package is [15:06] * Responded to review on ubuntu-image instructions for rpi [15:06] * Figured out A/B booting mechanism on core, related to combining the core & classic bootscripts. Unfortunately, it's going to require changes (snapd?) due to the way it's currently operating [15:06] * Figured out steps for switching bluetooth and serial console on the pi without locking the VPU's clock (which we currently do; however, fix requires up to date u-boot, currently eoan only) [15:06] * Working my way down into the depths of u-boot for pi4 support; nothing working yet but identified several changes required (bus to phys address mapping, serial console changes (?), the list goes on) [15:06] bug 1819444 in libcec (Debian) "libcec: Please stop linking to GPL-incompatible libraries" [Unknown,Confirmed] https://launchpad.net/bugs/1819444 [15:06] (done) [15:06] cyphermox: [15:08] evidently out [15:08] * a few weeks since my last report [15:08] * travelled to and from the UC20 sprint in London [15:08] * last Thursday was a holiday here [15:08] * was off Tuesday; will be off tomorrow and also next Wednesday [15:08] * reviewing the (touchy) ubuntu-advantage-tools SRU to trusty [15:08] * currently just working on verifying the authenticity of the GPG keys it's set up to import into apt's keyring [15:08] * discussions around the toolchain-triggered regressions in kernel module buildability that made it into the release pocket [15:08] * various follow-ups around full-disk encryption in UC20 [15:08] (done) [15:08] any questions over status? [15:09] I have no questions about status [15:09] not a single one either [15:11] #topic Release incoming bugs (eoan) === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | be nice | Weekly Ubuntu Foundations team Meeting | Current topic: Release incoming bugs (eoan) [15:11] #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-incoming-bug-tasks.html#foundations-bugs [15:12] I forget did we talk about bug 1834226 before? [15:12] bug 1834226 in software-properties (Ubuntu) "update-notifier doesn't respect "automatically check for updates: Never"" [High,New] https://launchpad.net/bugs/1834226 [15:12] not that I know [15:12] I don't think we did [15:12] But we should definitely investigate this [15:13] agreed [15:14] if there is disagreement about what the UX here should be, we will probably want to involve the design team [15:14] but based on the bug history it looks like the current behavior in 19.04 is not what's expected [15:15] targeting, carding [15:15] moving on then [15:16] the initramfs-tools one is still incomplete [15:16] ok, skip then? [15:16] yeah, bug 1396379 [15:16] bug 1396379 in ubiquity (Ubuntu) "installer uses first EFI system partition found even when directed otherwise" [High,Confirmed] https://launchpad.net/bugs/1396379 [15:17] fwiw I think there had been some discussion of that bug on #ubuntu-release at the time w/ infinity, xnox, and tsimonq2; but it's not documented in the bug, so [15:17] at what time? [15:17] when the bug was filed and xnox added his comment marking it incomplete [15:18] that was re: the initramfs-tools bug, not the ubiquity bug [15:18] why has this 5yo bug been escalated now? [15:18] comment #29 I believe [15:18] I don't know who Tom Reynolds is [15:19] I think we should decline this one [15:20] +1 - since sure, it's a bug, but it doesn't seem like a high-impact one [15:20] comment #24 somebody says they bricked their laptop? [15:21] I think this is largely user error, and perhaps things could be made clearer but I don't think ubiquity is fundamentally broken here when multiple ESPs are present [15:21] bdmurray: with no other context we don't know what "bricked" actually means or why the user thinks this bug is their bug [15:22] ack [15:23] Do you want to comment on the bug / tag it rls-ee-notfixing? [15:24] I've tagged it [15:24] apt-xapian-index is in universe for most releases... [15:24] bug 1612948 [15:24] bug 1612948 in apt-xapian-index (Ubuntu) "axi-cache conversion to python3 broke the script" [High,Confirmed] https://launchpad.net/bugs/1612948 [15:24] seb128 tagged the bug though [15:25] doesn't mean it's Foundations' responsibility to work it [15:25] because universe [15:25] skip? [15:25] skip not decline? [15:25] (and I'll let seb128 know it's not Foundations) [15:25] well someone else could commit to doing the work [15:26] actually, good point, since -incoming is only for Canonical teams [15:26] yeah, decline then [15:26] Is desktop subscribed to the package too? [15:26] Nope, okay I will decline it [15:26] the next is a ftbfs so card it [15:27] I will [15:28] actually it sounds like the ftbfs is fixed so I'll follow up on the bug state [15:29] bug 1835809 is assigned to rbalint already, should it have a card? [15:29] bug 1835809 in systemd (Ubuntu) "AMD Ryzen 3000 series fails to boot" [High,In progress] https://launchpad.net/bugs/1835809 [15:30] he mentioned that one in his status, I guess it's already uploaded and in -proposed [15:30] sil2100: you were going to look at bug 1833758 iirc [15:30] bug 1833758 in lvm2 (Ubuntu) "lvm2: vgcfgbackup in postinst takes several minutes" [Undecided,New] https://launchpad.net/bugs/1833758 [15:30] did we skip LP: #1836064? [15:30] Launchpad bug 1836064 in glibc (Ubuntu) "glibc needs an update for linux-5.2 kernel headers (alpha)" [High,Triaged] https://launchpad.net/bugs/1836064 [15:30] ah that might be the other end of the previous cross-build bug? [15:30] vorlon: Oh, I think I did skip it. [15:31] oh, this is for alpha not powerpc, so a different bug [15:31] and evidently not fixed [15:31] so yes, that's another ftbfs, let's card it [15:31] (I will) [15:32] bdmurray: yes, but then I noticed you already checked what needed checking, right? [15:33] sil2100: my vague note says "will see if image building is affected" [15:33] bdmurray: ok, so I can still check that, guess I missed that one [15:33] Will do that this week [15:34] sil2100: okay, thanks [15:34] So now we are in undecided territory [15:34] bug 1830044 [15:34] bug 1830044 in glibc (Ubuntu) "glibc 2.29-0ubuntu2 ADT test failure with linux 5.2.0-0.1" [Undecided,New] https://launchpad.net/bugs/1830044 [15:35] That seems High correct? [15:35] Is that the kernel bug affecting glibc that we were talking about 2 weeks ago? [15:35] I mean, I remember some kernel bug affecting glibc thingy being discussed recently [15:35] It was reported on 5/22 so maybe [15:36] may or may not be the same one, but it's surely resolved, the glibc in -proposed has passing autopkgtests [15:37] So High and card it? [15:37] I don't think it should be carded [15:37] it's fixed in proposed [15:37] I guess it's just a matter of getting glibc released [15:37] Since it's the previous one that's failing [15:38] Ah, got it. [15:38] Guess Adam's working on getting it migrating? [15:38] don't know if he is, but I have been [15:38] Moving on to bug 1835660. Its super vague but seemed important so I tagged it. [15:38] bug 1835660 in initramfs-tools (Ubuntu) "initramfs unpacking failed" [Undecided,Confirmed] https://launchpad.net/bugs/1835660 [15:39] doko: why did you mark LP: #1830044 rls-ee-incoming, given that the fixed glibc was already in -proposed? [15:39] Launchpad bug 1830044 in glibc (Ubuntu) "glibc 2.29-0ubuntu2 ADT test failure with linux 5.2.0-0.1" [Undecided,New] https://launchpad.net/bugs/1830044 [15:40] not much detail in that bug [15:40] Is there any follow up that should be done on the unpacking failed bug? [15:40] anyone have a booted eoan that they can check to see if this message shows on boot for them? [15:41] I guess it doesn't cause boot to fail, right? [15:41] right, but we don't want junk messages showing on the console at boot [15:43] reassigning to linux [15:43] Okay. Then seb128 reminded me of a patch in bug 1551623 [15:43] bug 1551623 in gconf (Ubuntu) "[SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed" [Critical,Triaged] https://launchpad.net/bugs/1551623 [15:44] is gconf a foundations package? [15:45] vorlon, see the last comment [15:45] seb128: which is an observation about why the patch might be unnecessary when using newer dpkg [15:46] vorlon, I asked bdmurray about whether we should/could consider SRUing that dpkg patch instead [15:46] does that imply desktop team is declining to apply the patch in this bug to gconf and wants Foundations to SRU dpkg instead? [15:46] we would like the dpkg patch to be applied [15:46] I don't see a dpkg patch that's been isolated in that log [15:46] it doesn't imply we nacl the gconf fix [15:46] but bdmurray nacked the sponsoring request because the patch isn't in debian [15:47] and it's not in debian because they EDONTCARE because they fixed dpkg [15:47] I didn't nack it, I asked a question about it. [15:47] https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=b5c50b3c6 [15:47] I guess? [15:48] and https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=7f43bf5 [15:49] ok, so someone should file a bug against dpkg with this context [15:49] k [15:49] thx [15:49] will do that for next week :) [15:49] seb128: thanks - probably target the bug directly to xenial/bionic and flag us the bug # so we get it on our trello [15:50] #topic Release incoming bugs (bionic) === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | be nice | Weekly Ubuntu Foundations team Meeting | Current topic: Release incoming bugs (bionic) [15:50] disco? [15:50] #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html#foundations-bugs [15:50] yeah, disco too [15:51] and the bug here is the one we just declined [15:51] * vorlon nods [15:51] because its in universe [15:51] Should we unsubscribe from the package now? [15:51] what did we decide wrt packages that are in main only in releases that are in ESM now? [15:52] I think Foundations is no longer responsible for those; Security Team is responsible for ESM [15:52] I don't think we did decide about ESM [15:52] I propose that we should unsubscribe if they're only in main for <= trusty [15:53] bdmurray: do you want an action for this? :) [15:53] (or a card?) [15:53] vorlon: for unsubscribing from the package or something more? [15:53] for unsubscribing from all packages that are only in main for <= trusty [15:54] vorlon, bdmurray, bug filed https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1836225 [15:54] Launchpad bug 1836225 in dpkg (Ubuntu) "SRUing the dpkg trigger improvements to bionic" [Undecided,New] [15:54] a card as I'm taking off this afternoon and tomorow and might forget stuff [15:54] ok [15:54] I filed a bug for thatearlier [15:54] juliank: for dpkg? [15:54] Or reused bdmurray's bug [15:54] yes, for dpkg [15:54] It already has a card [15:55] juliank, ah, sorry, I didn't see it in the recent dpkg ones, feel free to mark it as dup then [15:55] I also have the list of commits from guillem I have to cherry-pick :) [15:55] bug 1828639 has dpkg tasks [15:55] bug 1828639 in dpkg (Ubuntu Eoan) "package libvlc-bin 3.0.6-1 failed to install/upgrade: 90.8592:triggers looping, abandoned" [High,Triaged] https://launchpad.net/bugs/1828639 [15:55] yeah, that's it [15:55] isn't it fixed for Eoan now though? [15:56] It's certainly in proposed [15:56] FWIW, this is the card: https://trello.com/c/nECzoqs2/2039-package-menu-2147ubuntu3-failed-to-install-upgrade-triggers-looping-abandoned [15:56] We'd found that already [15:57] Planned uploading that soon, was waiting for infinity to do eoan, which has been done now [15:57] juliank: so you are SRUing that? [15:57] I planned on doing that, yes [15:57] ok [15:57] juliank: that should fix many? all? trigger looping issues [15:57] bdmurray: all AFAIUI [15:58] so a bug scrub may be in order [15:58] #topic Team proposed-migration report === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | be nice | Weekly Ubuntu Foundations team Meeting | Current topic: Team proposed-migration report [15:58] #link http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#foundations-bugs [15:59] I guess we have to go quick, 1 minute left :P [15:59] a lot of ppc64el backlog there [15:59] which explains most of glibc [16:00] sphinx was a non-Foundations upload, but it's not clear if oSoMoN is following up [16:00] I'll ping him [16:00] vorlon, I was handling the sphinx one [16:00] waveform: oh ok [16:00] sorry - slipped under the radar this week with pi4 and u-boot filling my head! [16:00] python-service-identity [16:01] was anyone working on this? it was an autosync [16:02] who wants to volunteer to take python-service-identity? [16:02] vorlon, waveform, sphinx was https://bugs.launchpad.net/ubuntu/+source/python3.7/+bug/1834236 afaik [16:02] Launchpad bug 1834236 in python3.7 (Ubuntu) "codecs.open(errors='strict') doesn't fail on invalid encoding with python3.7.4 RC1" [High,Fix released] [16:02] (unless we have a new one) [16:03] let's see, i retried the build [16:03] python-reportlab: the autopkgtests don't fail in Debian, I've retried them now and will follow through [16:04] python-setuptools: reprotest/i386 is a progression (or flaky test) rather than a regression, we can sort that out [16:04] but libcloud/armhf looks like a real regression [16:05] anyone want to dig into that? [16:05] * vorlon tries a --no-proposed autopkgtest retry [16:06] put your hand up if you want to claim it; meanwhile, moving on [16:06] debian-installer needs an update for linux 5.2 [16:06] I'll check w/ infinity on that [16:06] glib2.0, I think the Desktop Team is managing that one [16:06] and then we're done [16:07] #topic Chair selection for next meeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | be nice | Weekly Ubuntu Foundations team Meeting | Current topic: Chair selection for next meeting [16:07] who should we nominate that isn't here to object? [16:07] doko! [16:07] He'll be at DebCamp [16:07] I'm off next Thu, Fri [16:08] anyone else who hasn't had a turn lately? [16:09] Should we keep a list of this [16:09] * vorlon shrugs :) [16:09] I'm not keeping the list :) [16:09] We could grep the backlog [16:09] tdaitx: you want to chair next? [16:09] vorlon: yeah [16:09] Sounds sensible [16:09] #agreed tdaitx to chair next [16:10] #topic AOB === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | be nice | Weekly Ubuntu Foundations team Meeting | Current topic: AOB [16:10] anything else? [16:10] Again, to make sure it sticks: I'm off next Thu, Fri [16:10] * vorlon nods [16:10] Also DebConf after that [16:10] I'm out this afternoon and tomorrow [16:11] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | be nice [16:11] Meeting ended Thu Jul 11 16:11:58 2019 UTC. [16:11] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2019/ubuntu-meeting.2019-07-11-15.02.moin.txt [16:12] thanks, all! [16:30] vorlon: there's no hint about that in the report [16:42] doko: sure; the bug report was untriaged, but a check of the current status of the autopkgtests would've shown that there's a newer passing version, so I don't understand why you were a) looking at this bug and b) nominating it