[10:12] * xnox is not it =) === dbungert1 is now known as dbungert [14:56] o/ [14:57] \o [15:00] mapreri teward around for mtg? [15:00] I'm around, though I'm not really ready for anything. tbh with vacation and everything else I haven't done 1 single bpo thing this month. [15:01] alive but operating at 20% - on the line with a vendor for FT job [15:01] all i did was approve a couple backports last week [15:01] ok let's start, probably most items will carry over [15:01] yeah [15:01] nothing else much to mention [15:01] #startmeeting Ubuntu Backporters [15:01] Meeting started at 15:01:26 UTC. The chair is ddstreet. Information about MeetBot at https://wiki.ubuntu.com/meetingology [15:01] Available commands: action, commands, idea, info, link, nick [15:01] #topic previous action items [15:01] #subtopic ddstreet update tooling, requestbackport, backportpackage (carried over) [15:01] Hey backporters [15:01] #action ddstreet update tooling, requestbackport, backportpackage (carried over) [15:01] ACTION: ddstreet update tooling, requestbackport, backportpackage (carried over) [15:01] hi luna__ [15:02] #subtopic ddstreet get DEB_VENDOR=ubuntu dch --bpo to DTRT pls (carried over) [15:02] #action ddstreet get DEB_VENDOR=ubuntu dch --bpo to DTRT pls (carried over) [15:02] ACTION: ddstreet get DEB_VENDOR=ubuntu dch --bpo to DTRT pls (carried over) [15:02] #subtopic ddstreet look at reviewer tooling such as 'queue' or other tools for reviewing/accepting/rejecting uploads, and closing the corresponding bugs (carried over) [15:02] #action ddstreet look at reviewer tooling such as 'queue' or other tools for reviewing/accepting/rejecting uploads, and closing the corresponding bugs (carried over) [15:02] ACTION: ddstreet look at reviewer tooling such as 'queue' or other tools for reviewing/accepting/rejecting uploads, and closing the corresponding bugs (carried over) [15:02] #subtopic ddstreet send ML reply to continue thread re: clarification on specific wording for no-bug-required backport exceptions [15:02] this one, i actually did [15:02] saw the mail, ty [15:03] #subtopic ddstreet finish updating charter/policies, send email to ML to request team review [15:03] and i did this one as well, and sent an email [15:03] those both probably should get discussed on the ML, unless either of you want to discuss them now [15:03] #subtopic ddstreet sched next meeting for aug 31 15:00 UTC [15:03] i did this one, of course :) [15:04] done [15:04] #subtopic mapreri upload (more of) all the tools (carried over, in progress) [15:04] cheer for ddstreet actually doing his tasks! [15:04] i assume carry all yours mapreri? [15:04] boos for mapreri not doing :( [15:04] lol, i only did the 2 easiest tasks :) [15:04] pls yap [15:04] #action mapreri upload (more of) all the tools (carried over, in progress) [15:04] ACTION: mapreri upload (more of) all the tools (carried over, in progress) [15:04] #subtopic mapreri fix lintian to not complain about ~bpo suffix (https://bugs.debian.org/1001399) (carried over) [15:04] Debian bug 1001399 in lintian "lintian: adjust backports-upload-has-incorrect-version-number for ubuntu" [Normal, Open] [15:05] #action mapreri fix lintian to not complain about ~bpo suffix (https://bugs.debian.org/1001399) (carried over) [15:05] ACTION: mapreri fix lintian to not complain about ~bpo suffix (https://bugs.debian.org/1001399) (carried over) [15:05] #subtopic mapreri review wiki page to see how we can highlight that backport requestors need to do the backport work and find a sponsor [15:05] #action mapreri review wiki page to see how we can highlight that backport requestors need to do the backport work and find a sponsor (carried over) [15:05] ACTION: mapreri review wiki page to see how we can highlight that backport requestors need to do the backport work and find a sponsor (carried over) [15:05] #subtopic mapreri start thread on ML about how to use bug status to define meaing in process [15:05] #action mapreri start thread on ML about how to use bug status to define meaing in process (carried over) [15:05] ACTION: mapreri start thread on ML about how to use bug status to define meaing in process (carried over) [15:05] ok that's all previous items [15:06] moving on :) [15:06] #topic open mailing list items [15:06] #subtopic clarification on specific wording for no-bug-required backport exceptions [15:06] as mentioned before, we should probably keep this on the ML [15:06] still in inbox, yes. [15:06] but please let's all remember to reply before next mtg :) [15:06] #action clarification on specific wording for no-bug-required backport exceptions [15:06] ACTION: clarification on specific wording for no-bug-required backport exceptions [15:07] #subtopic charter/policies [15:07] #link https://lists.ubuntu.com/archives/ubuntu-backports/2022-February/022680.html [15:07] thanks luna__! [15:07] a bit to slow with the copy and paste tough [15:07] this will need review from you both, so no need to discuss now, but hopefull we can finalize it on the ML and/or by next mtg [15:08] ok that's all the ml threads, unless i'm missing something [15:08] #link https://lists.ubuntu.com/archives/ubuntu-backports/2022-August/022925.html [15:08] ah thanks again :) [15:09] #topic open bugs needing discussion [15:09] haven't even looked at what's open now :( [15:09] i reviewed the dh-python bug, and there were some issues there [15:09] unit193 said it should just be dropped, so i believe teward[m] marked it wontfix [15:10] i can't see it as open [15:10] i dont know of anyone here thinks it might be worth looking into backporting it [15:10] #link https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1983414 [15:10] Launchpad bug 1983414 in dh-python (Ubuntu) "[BPO] dh-python 5.20220403 to focal" [Undecided, Fix Released] [15:11] yep teward teward[m] has indeed closed it as not fixing [15:11] ddstreet: correct i did a won'tfix on one of the bugs because Unit mentioned in the message it should be dropped given $REASONS [15:11] the main issue, at least from my relatively quick review, was the py2 dh_python2 script, which did a pkg move, so that would need to be properly handled in the backport [15:11] holed on [15:11] the main reason behind that bpo was to have the pyproject support, right? [15:11] IIRC [15:11] yep that's my understanding [15:12] and that would require a few other backports for deps [15:12] "This is needed to refresh the yt-dlp package as it has support for 'environment markers'" [15:12] I understand that such reason still stands, so I think I'd want to look at it as imho it makes sense to have [15:12] pybuild-plugin-pyproject <-- not tested [15:12] ddstreet: what's "a few"? [15:12] #link https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1983414/comments/1 [15:12] Launchpad bug 1983414 in dh-python (Ubuntu) "[BPO] dh-python 5.20220403 to focal" [Undecided, Fix Released] [15:12] i listed the deps in my comment [15:13] specifically, python3-{build,installer,tomli} packages [15:13] which aren't available in focal. [15:13] doesn't sound like a goal-blocker to me, just bpo those all? [15:13] yeah i think it's quite doable [15:13] also I'm not sure there is a problem with the python2 thing? [15:14] but just would need someone to do the dep backports, and properly adjust the backported dh-python package [15:14] I don't see having the bpo package be uninstallable with something in the main suite as a problem? [15:14] you mean the conflicts with python2? [15:14] yep [15:14] i mean i'd certainly prefer to address that, no? [15:15] or, indeed, if that's only for dh_python2 is trivially solvable sure, but anyway, even if unsolved I don't think it's a blocker to me? [15:15] but then users of the backported dh-python would not be able to run any py2 script [15:15] it's certainly preferable yes [15:15] I'm mostly trying to understand how you feel about that particular point [15:16] personally, i think it should be fixed [15:16] i mean, if dh-python was actually *providing* python2, then that might be ok, but it's conflicting (which will force removal) of python2 only due to a single dh_python2 script [15:17] i think the right approach is to remove the dh_python2 from the backport, and remove the Conflicts: python2 [15:17] if it's only for that single script, it's probably best to drop it from dh-python yes [15:17] it's B+R, not conflicting iiuc [15:17] anyway, I got your point [15:17] that's certainly my preference, but it will depend on the details once someone gets into doing it [15:17] right B+R sorry [15:18] I doubt I'd be able to pick up, but since it's something that might make sense to have, if unit193 wants to pick it up again at least I know your position :) [15:18] (as I will tell him that I'm all for it and not give up just after one review!) [15:18] so should we reopen the bug, and/or add an action item for us to look at it? [15:19] yeah my review didn't mean to shut his work down [15:19] I think it's fine as it is, I'll more informally poke him [15:19] ok hopefully we won't forget about it :) [15:20] i guess if he wants to backport yt-dlp anymore, he'll need to either fix that backport, or work on dh-python backport :) [15:20] * mapreri just did [15:20] IRC++ [15:20] also fyi, i did approve one of his yt-dlp backports, which failed due to dh-python dep missing [15:20] so it's bd-uninst atm? [15:21] #link https://launchpad.net/ubuntu/+source/yt-dlp/2022.08.19-1~bpo20.04.1 [15:21] doesn't look failed to me? [15:21] sorry, wrong page [15:21] meh [15:22] feel free to action me to poke him some more on this [15:22] I think this is the first time. how harsh should we be about unbuilt packages? [15:22] #action mapreri poke unit193 about yt-dlp dep on dh-python [15:22] ACTION: mapreri poke unit193 about yt-dlp dep on dh-python [15:23] well, he did upload both yt-dlp *and* dh-python, so if i'd accepted dh-python, then the yt-dlp upload would have built [15:23] so it's partially my fault for not realizing that before i accepted the yt-dlp upload [15:23] accept and rebuild? [15:23] buuuuut it certainly would have been better for him to not upload yt-dlp until dh-python was accepted [15:23] I kind of believe this should go in that page describing when an upload is acceptable without a tracking bug report [15:24] luna__ yeah, if we do finally accept the dh-python backport, we can just do a rebuild of the yt-dlp [15:24] if it requires special attention and the uploader knows of it, I reckon a bug is warrented. [15:24] ddstreet: sounds good [15:24] (in fact, no rebuild is needed, lp would pick it up by itself since it's in bd-uninst) [15:24] mapreri yep i agree, the previous yt-dlp uploads have been bugless which i think was fine, but yeah once there's any complexity like this, we do need a bug [15:24] (i think at least) [15:24] ah [15:25] ah didn't know it would automatically rebuild [15:25] it's not a *re*build after all [15:25] right :) [15:25] didn't build at all yet :) [15:25] true [15:25] ok, anything else for that bug? [15:26] none from me [15:26] not from me [15:26] #link https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1987356 [15:26] Launchpad bug 1987356 in elfutils (Ubuntu) "[BPO] elfutils/0.187-1 from Kinetic" [Undecided, Fix Committed] [15:26] i think this one is done and published, does it just need to move to fix-released? [15:27] i'll go ahead and mark it as such, since it does seem released [15:27] https://packages.ubuntu.com/jammy-backports/elfutils ? [15:27] seems like you just did lol [15:28] seems to be in the repos [15:28] and there are 2 more bugs, but both appear to need a sponsor [15:28] #link https://bugs.launchpad.net/ubuntu/focal/+source/ipmctl/+bug/1968076 [15:28] Launchpad bug 1968076 in ipmctl (Ubuntu Focal) "[BPO] ipmctl with support for CPS hardware" [Undecided, New] [15:28] #link https://bugs.launchpad.net/ubuntu/jammy/+source/limnoria/+bug/1983415 [15:28] Launchpad bug 1983415 in limnoria (Ubuntu Jammy) "[BPO] limnoria 2022.6.23-1 to jammy" [Undecided, New] [15:29] tbh, I would rather not look at anything more right now, as I have another meeting coming up on the hour and I'd like to prepare for it :3 [15:29] ack, i think we can leave the unsponsored ones alone [15:29] ok that's all open bugs [15:30] #topic AOB [15:30] anything else from anyone? [15:30] luna__ you have any topics? [15:30] nope [15:30] ok final subtopic then, next meeting [15:30] #subtopic next mtg date [15:30] 1 month from now? [15:31] mh [15:31] sep 28? [15:31] works for me [15:31] 28 is looking crowded for me, what about oct 5 instead? [15:31] oct 5 works for me [15:31] have another meeting 5th Oct, but i don't do much backports work just curious so its okay to go without me [15:31] (I also have a bit of travel the week before, that's why I'm not suggesting sep 21) [15:32] mind you, I *can* do sep 28th, it's just that my agenda will look messy :3 [15:32] teward[m]: ? [15:32] no issue of oct 5, sept. 28 is a no go [15:33] let's do oct 5 then [15:33] same time, 15:00 UTC [15:33] that makes it easy i guess [15:33] sure [15:33] luna__ if you have interest in joining backporters team, feel free to let us know in a mtg or ML :-) [15:34] #action ddstreet schedule next mtg Oct 5 15:00 UTC [15:34] ACTION: ddstreet schedule next mtg Oct 5 15:00 UTC [15:34] will think about it and do if so [15:34] ok i think that's all the topics, last chance for anything else? [15:34] #endmeeting [15:34] Meeting ended at 15:34:44 UTC. Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-08-31-15.01.moin.txt [15:34] thanks all! o/ [15:34] \\o [15:35] thanks