Simon, while I appreciate the amount of work you put into this, please
respect the work of others. We were dealing with this, and you just
unilaterally closing the bug like this is not OK.
It would have been problematic on any given bug, but here it's
compounded by the fact that it's literally not
Hmm, I seem to have lost a couple sentence there. Re "not your
business": MIRs are the process by which Canonical teams decide what
they'll take responsibility for. It is OK for a community member to
start that process and lobby teams for support, but here you're
interfering with an ongoing process
Superseded by LP: #2098797
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098769
Title:
[MIR] nghttp3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nghttp3
I'm actually writing out the MIR bug now, separately.
** Changed in: nghttp3 (Ubuntu)
Status: Incomplete => Invalid
** Tags removed: rls-pp-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
A revert of that dependency is in progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098769
Title:
[MIR] nghttp3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
