[08:20] <luis220413> What does it take for a team to own a package in the context of a main inclusion report (MIR)?
[08:22] <tumbleweed> that the team is maintaining it. They're subscribed to the bugs, dealing with the critical ones.
[08:22] <tumbleweed> everything that goes with being a maintainer
[08:23] <luis220413> I am asking this question for my 6 MIRs: the top 6 in https://bugs.launchpad.net/~ubuntu-mir/+bugs?orderby=-id&start=0
[08:23] <luis220413> See this comment: https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1986592/comments/8
[08:23] <ubottu> Launchpad bug 1986592 in network-manager-openconnect (Ubuntu) "[MIR] network-manager-openconnect" [Low, Incomplete]
[08:26] <tumbleweed> so, you need the desktop team to agree to own them
[10:12] <luis220413> What are the security implications of a binary in /sbin, in the context of a main inclusion report (MIR)?
[10:12] <luis220413> I mean: Why are binaries in /sbin and /usr/sbin security relevant, in the context of a main inclusion report (MIR)?
[10:13] <luis220413> Specifically bug 1987446
[10:13] <ubottu> Bug 1987446 in openconnect (Ubuntu) "[MIR] openconnect" [Undecided, Incomplete] https://launchpad.net/bugs/1987446
=== sem2peie- is now known as sem2peie
[11:18] <luis220413> I returned. Can anyone answer my question about the security relevance of /sbin I made earlier today?
=== luis220413_ is now known as luis220413