[15:30] here in a minute [15:30] o/ [15:31] hi [15:31] #startmeeting Weekly Main Inclusion Requests status [15:31] Meeting started Tue Dec 1 15:31:40 2020 UTC. The chair is cpaelzer. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [15:31] 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 Main Inclusion Requests status Meeting | Current topic: [15:31] ddstreet: doko: sarnold: jamespage: didrocks999 - hi [15:32] o/ [15:32] we had no past weeks action items, so let us skip that [15:32] good morning [15:32] also no new MIRs in our inbox [15:32] hey [15:32] nor are there recent updates to incomplete MIRs [15:32] what has some content thou is component mismatches [15:33] #topic current component mismatches === 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 Main Inclusion Requests status Meeting | Current topic: current component mismatches [15:33] #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg [15:33] #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg [15:33] doko: postgresql-13 is ready to migrate except for perl - I think this could be promoted now in hirsute [15:34] doko: what do you think and coudl you do that? [15:34] related bug (to post updates) is https://bugs.launchpad.net/ubuntu/+source/postgresql-13/+bug/1902059 [15:34] Launchpad bug 1902059 in postgresql-13 (Ubuntu) "[MIR] postgresql-13" [Undecided,Incomplete] [15:35] * cpaelzer is waiting a bit to let this topic conclude before starting the next one we see in mismatches [15:35] sure. will do. please note that we also need postgresql-12 for the perl transition, afaics [15:35] doko: PG-12 is intended to be removed [15:35] doko: hence we didn't care for it [15:35] doko: it is already out of Debian testing [15:35] but I didn't track how many reverse dept we'd have left [15:36] yes, we can remove it after perl mirates ... [15:36] doko: should I analyze and file a removal for hirsute ? [15:36] oh ok, so perl can migrate without postgresql-12 being either removed or fixed then? [15:36] let's discuss this later, not MIR stuff [15:36] ok WFM [15:37] next MIR topic node-jquery->sizzle [15:37] how did node-jquery get into main? [15:37] exactly [15:37] it is unsubscribed http://reqorts.qa.ubuntu.com/reports/m-r-package-team-mapping.html [15:37] and if I read https://launchpad.net/ubuntu/+source/node-jquery/+publishinghistory correctly we'd have to ask vorlon [15:37] I can't spot a bug [15:37] https://bugs.launchpad.net/ubuntu/+source/node-jquery/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=OPINION&field.status%3Alist=INVALID&field.status%3Alist=WONTFIX&field.status%3Alist=EXPIRED&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED [15:37] &field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.tag=&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field [15:37] .has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on [15:37] wow [15:38] in groovy [15:39] it was promoted in groovy, but why is the question I guess (and once solved fixing up subscriptions to the pkg) [15:39] having no bugs in a package thats been around for [15:39] ~10 releases is kinda sus ngl [15:39] anyway, I'll demote and see what breaks ... [15:39] that is an option as well [15:40] wfm :) [15:40] if anything breaks you might ask vorlon in whatever the next foundation meeting is [15:40] as he seems to have promoted it he might have extar context [15:40] next mismatches are u-boot-menu and opensbi [15:40] raspi related ? [15:40] ItzSwirlz: especially since bugreporters surprisingly often just pick packages at random.. [15:41] or risc [15:41] opensbi rings a risc bell to me [15:43] commit 6e2571375f95c01bc26f912b1de20909b8f2e547 [15:43] Author: Dimitri John Ledkov [15:43] Date: Wed Nov 25 13:37:08 2020 +0000 [15:43] supported-cloud: add RISC-V packages [15:43] given how new the riscv platform is it feels very early to me to be bringing in a 'supervisory binary interface' [15:43] xnox: will there be MIRs filed for these since you added them to the seeds? [15:44] next is ruby-defaults -> rubygems [15:44] sarnold: do we have a chance to go without it? [15:44] rubygems was in precise in main ... [15:45] isn't this some split-out? [15:45] yeah and mostly removed rom everything else [15:45] it was onyl coming back to hirsute - and in Debian also is only in unstable [15:46] my ping to solve this would go to kanashiro but he's not aroudn this week [15:46] however rubygems-integration was in main [15:46] the question is "re-promote on the base of the old MIR" https://bugs.launchpad.net/ubuntu/+source/gem2deb/+bug/894827 or do we need something else? [15:46] Launchpad bug 894827 in rubygems (Ubuntu) "[MIR] gem2deb" [Undecided,Fix released] [15:47] It also has ~25 test issues in excuses [15:47] so it won't move to -release even if promoted [15:47] ouch [15:47] well, lets wait [15:47] agreed [15:48] xnox: you can answer later about opensbi and u-boot-menu when you see the ping [15:48] that concludes todays component mismatch oddities [15:48] #topic Any other business? === 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 Main Inclusion Requests status Meeting | Current topic: Any other business? [15:49] nothing for me [15:49] sarnold: discount status? [15:49] doko: no movement, sorry [15:49] sarnold: if the security-team would join +1 maitenance, you would see the pain and extra work that this causes :-( [15:51] in general security reviews seem rather stuck recently, I gues overload is happening [15:51] or reviews just happen on a lot of things not related to ine ... [15:51] mine [15:51] sarnold: can you carry the pain-FYI to the Team so everone is aware? [15:52] not, you're very right; due to losing several staff members we're heavily oversubscribed, 'tis the season to use unused PTO, and of course there's been glorious training modules to complete [15:52] cpaelzer: yes [15:53] thanks [15:53] let us clsoe the meeting for today then [15:53] #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 [15:53] Meeting ended Tue Dec 1 15:53:39 2020 UTC. [15:53] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2020/ubuntu-meeting.2020-12-01-15.31.moin.txt [15:53] doko: where do you want to continue the discussion on postgresql-12 next steps? [15:53] thanks cpaelzer, all [15:53] thanks! [15:53] can do here [15:53] ok [15:54] so PG-12 is in excuses with a bunch of tests failing, we didn#t care for it as it is intended to be removed [15:54] but I wanted to remove PG-12 when PG-13 moved into hirsute and is promoted [15:54] that depends on perl atm [15:54] what is the order of promotion/removal/other that you'd recommend [15:54] -13 is not yet migrated [15:55] yeah PG-13 depends on perl [15:55] IÄve ensured it is otherwise ready [15:55] so is the related postgresql-common v223 [15:55] omnidb ftbfs [15:56] hmm, I can look for that [15:56] pgpointcloud/armhf ftbfs [15:56] should not be related [15:56] does that need to be resolved for PG-13 [15:57] anyway I can take a look as well- b'cause why not [15:57] and: Implicit dependency: perl postgresql-12 (not considered) [15:57] for perl. [15:57] hrm [15:57] so perl won't migrate without -12 [15:57] so you are saying I need to get PG-12 working for PG-13 to migrate because perl links the two [15:57] arrr [15:58] yes [15:58] sorry [15:58] I love fixing proposed if I'm not doing it 24/7 - so yeah I'll look into all of those [15:58] but maybe (only maybe) re'll remove PG-12 instead even before 13 migrates [15:58] depends how easy/hard those fails are PG-12 has [15:59] but then you need -13 in the release pocket ... [15:59] * cpaelzer sigh [15:59] ok on it [15:59] Then let me replace that with ... maybe test hints [16:00] just so I have the feeling of a chance to get it resolved :-) [16:00] Notes on PG related tasks taken and will look into them ... [16:01] thanks doko for sorting out next steps for these! [16:01] cpaelzer: yes, proposed a hint with the note that it will be removed anyway [16:41] Any kernel meeting today or still not? [16:42] also are you rebuilding the 5.9.11 kernels ? === cpaelzer__ is now known as cpaelzer