[12:55] <cpaelzer> ddstreet: didrocks: jamespage: doko: sarnold: joeubuntu: pre-MIR meeting ping for awareness
[12:55]  * cpaelzer lights the campfire
[12:55] <ddstreet> o/
[12:56] <joeubuntu> morning cpaelzer ddstreet
[12:56] <ddstreet> joeubuntu o/
[13:01] <cpaelzer> ok - one more ping for everyone and then lets kick this off
[13:01] <cpaelzer> ddstreet: didrocks: jamespage: doko: sarnold: joeubuntu:
[13:01] <cpaelzer> #startmeeting Weekly Main Inclusion Requests status
[13:01] <meetingology> Meeting started Tue Mar 31 13:01:15 2020 UTC.  The chair is cpaelzer. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:01] <meetingology> Available commands: action commands idea info link nick
[13:01] <cpaelzer> #topic Review of previous action items
[13:01] <cpaelzer> the one thing I remember being open was that doko wanted to review (or discuss with sil2100) about https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1867813
[13:01] <cpaelzer> I don't see an update on the bug
[13:02] <cpaelzer> doko: speak up if there are any update on this
[13:02] <cpaelzer> other than that we maybe should do the bug-assignment to you so that this is clear to everyone not reading the meeting logs
[13:02] <jamespage> o/
[13:02] <jamespage> sorry I'm a little late
[13:03] <cpaelzer> np
[13:03] <doko> cpaelzer: no, didn't touch yt
[13:03] <cpaelzer> ok, I updated the bug so it is clear
[13:03] <cpaelzer> you have another week for it (and another, ...) :-)
[13:04] <cpaelzer> Noth further open items I'd know of
[13:04] <cpaelzer> next topic would be the - today very interesting - component mismatches
[13:04] <cpaelzer> #topic current component mismatches
[13:04] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[13:04] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[13:05] <cpaelzer> This would be empty (what a nice picture this would be) if not for "Ubuntu.Focal supported-maas seed"
[13:05] <cpaelzer> this is due to https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/platform/commit/?id=eaef590aa2868e98d67c114bbc655be1964ddf6f
[13:05] <jamespage> apport depends on terminator?
[13:05] <cpaelzer> jamespage: that is a bad alternative listing
[13:05] <jamespage> I was aware of the mismatch for websockify -> python-jwcrypto
[13:05] <jamespage> https://bugs.launchpad.net/ubuntu/+source/python-jwcrypto/+bug/1869215
[13:06] <cpaelzer> yeah jamespage that one comes later in the "new" cases
[13:06] <jamespage> mainly as I did the update and raised the MIR (I know it late)
[13:06] <jamespage> ok
[13:06] <cpaelzer> and apport was discussed last week
[13:06] <cpaelzer> yet it isn't clear who is driving this to a conclusion (fixing d/control in apport)
[13:06] <jamespage> so what do we need to discuss now about mismatches?
[13:06] <cpaelzer> the maas seed change
[13:06] <doko> foundations needs to talk with the MAAS team who will maintain these in the archive
[13:07] <cpaelzer> ok is that ongoing doko?
[13:07] <cpaelzer> there are even denied packages in this list (like ipmitool)
[13:07] <doko> these are used to build the maas snap, however the team doesn't feel responsible to maintain those :-(
[13:07] <cpaelzer> no good sportsmanship that is young padawan
[13:07] <doko> just skip those for now.
[13:08] <cpaelzer> doko: can we keep it as is and you'll let us know how the discussion continues?
[13:08] <cpaelzer> ok
[13:08] <doko> yes
[13:08] <cpaelzer> #topic New MIRs
[13:08] <cpaelzer> #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir
[13:08] <cpaelzer> I'm volunteering to take u-boot-rpi
[13:09] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/python-jwcrypto/+bug/1869215 as mentioned by jamespage is up for grabs
[13:09] <cpaelzer> anyone?
[13:09] <cpaelzer> this should be a rather easy python package
[13:10] <ddstreet> i can take it, i suppose
[13:10] <cpaelzer> since doko and I are currently assigned and jamespage filed it I'm looking towards didrocks / ddstreet for this
[13:10] <cpaelzer> ah
[13:10] <cpaelzer> thanks ddstreet
[13:10] <cpaelzer> assigned
[13:10] <cpaelzer> jamespage: I have to admit - milestone 20.03 is a bit intense for this
[13:11] <cpaelzer> given that tomorrow is 20.04 :-)
[13:11] <cpaelzer> #topic Incomplete bugs / questions
[13:11] <cpaelzer> #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-mir
[13:11] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1864666 was punted to 20.10
[13:11] <cpaelzer> nothing newer than that to work on
[13:11] <cpaelzer> unless anyone of you disagrees
[13:12] <cpaelzer> ok, silence means you are ok I guess :-)
[13:12] <cpaelzer> #topic Any other business?
[13:12] <ddstreet> yes,
[13:12] <ddstreet> i'd like review of my reviews, if possible, either now or later
[13:12] <ddstreet> https://bugs.launchpad.net/ubuntu/+source/realmd/+bug/1868154
[13:12] <ddstreet> https://bugs.launchpad.net/ubuntu/+source/adcli/+bug/1868159
[13:13] <cpaelzer> I can do those tomorrow morning or late today
[13:13] <cpaelzer> along u-boot-rpi
[13:13] <ddstreet> cpaelzer one thing i may have missed (thinking about it now) is MIR requires a team to accept ownership of the pkgs, correct?  I think that should be added to the TODO checklist
[13:13] <cpaelzer> I think it is in it
[13:14] <cpaelzer> TODO: - The package has a team bug subscriber
[13:14] <ddstreet> ah, i misinterpreted that then
[13:14] <ddstreet> as *any* bug subscriber
[13:14] <ddstreet> my bad
[13:14] <ddstreet> perhaps that could be clarified, i assume only a limited set of lp teams are acceptible there, not just any team, right?
[13:15] <ddstreet> anyway, we can discuss after you have time for a more detailed review
[13:15] <ddstreet> thanks
[13:17] <cpaelzer> ok I can do that in a query with you
[13:17] <cpaelzer> nothing else I guess?
[13:17] <cpaelzer> 10
[13:17] <cpaelzer> 5
[13:17] <cpaelzer> 3
[13:17] <cpaelzer> 2
[13:17] <cpaelzer> 1
[13:17] <cpaelzer> #endmeeting
[13:17] <meetingology> Meeting ended Tue Mar 31 13:17:30 2020 UTC.
[13:17] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2020/ubuntu-meeting.2020-03-31-13.01.moin.txt
[13:17] <cpaelzer> thank you everyone
[13:17] <jamespage> thanks cpaelzer
[13:24] <jamespage> ddstreet, cpaelzer: soooo... websockify and spice-html5
[13:25] <jamespage> I completely foobar'ed spice-html5 - its still not been updated to the 0.2.x series, although we have tested OK with OpenStack
[13:25] <jamespage> https://bugs.launchpad.net/ubuntu/+source/python-jwcrypto/+bug/1869215 was a new depends of websockify which has been promoted to main
[13:26] <jamespage> but without the spice-html5 adapter we don't have a complete dependency chain under support
[13:27] <didrocks> sorry, was lost in grub git rebasing
[13:27] <didrocks> just backlog, sounds ok, ut do not hesitate to ping me if anything
[13:28] <ddstreet> jamespage seems like websockify in ubuntu is already newer than debian, are you saying we need to update spice-html5 to 0.2 series without debian also?
[13:28] <jamespage> ddstreet: welcome to openstack in ubuntu :)
[13:28] <ddstreet> lol
[13:28] <jamespage> kinda - I was raising that the three projects are all inter-linked
[13:29] <jamespage> i.e. unless I do the spice-html5 updates, the MIR can't complete
[13:29] <jamespage> but we're at beta freeze so I'll make myself somewhat unpopular
[13:29] <jamespage> so either I make myself (more) unpopular and we go for it for 20.04
[13:29] <jamespage> or we push websockify back to universe and push all three out to 20.10
[13:31] <ddstreet> i'll defer to cpaelzer and you as i'm new to MIR, though of course one of those options saves me MIR review work ;)
[13:32] <cpaelzer> jamespage: websockify again
[13:32] <cpaelzer> didn't we have that discussed in the past
[13:33] <cpaelzer> on https://bugs.launchpad.net/ubuntu/+source/websockify/+bug/1108935 ?
[13:39] <cpaelzer> jamespage: you are talking about the constraints I set in https://bugs.launchpad.net/ubuntu/+source/websockify/+bug/1108935 I guess
[13:40] <cpaelzer> there even is a 2.2
[13:40] <cpaelzer> and more fixes
[13:40] <cpaelzer> so yeah I'd still prefer an update beofre promoting that to main
[13:40] <cpaelzer> and while I understand tha no one wants to be (more) unpopular long term you'd be happy you have the newer version
[13:42] <cpaelzer> I agreee to "unpopular and we go for it for 20.04" or "push all three out to 20.10"
[13:42] <cpaelzer> but which of those you pick is your decision jamespage
[13:42] <cpaelzer> as it is your gain (cool features) and your pain (being unpopular)