MIR stands for *Main* Inclusion Request. It's different from processing
a NEW package. Or else we would only accept NEW packages in Ubuntu if
they went into main.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.l
Just a note that Jeff wasn't asking for an MIR, but an SRU.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1868882
Title:
[SRU] Put ipmctl into Bionic (and update necessary deps)
To manage
Hello Jeff,
I have opened a card to keep track of this work in 20.10. I'm not sure
that a MIR will be possible (for ndctl/ipmctl) based on previous denial
but we can take a look later after we MERGE latest upstream release
(02.00.00.3759) to 20.10.
For now I'm closing this bug as there is nothing
Hello Jeff,
I just synced with other engineers about this particular bug and it was
brought to my attention that a MIR was attempted before and didn't pass
(LP: #1854181). Unfortunately, for this case, a MIR is needed because
the package is in [universe].
There is something else:
$ rmadison ipmc
So what we need here is:
# Eoan
- Backport of Focal ipmctl package to Eoan
- includes ipmctl
- includes libipmctl4
- Upload of this "new" package into Eoan Universe
# Bionic
- Backport of Focal ipmctl package to Bionic
- includes ipmctl
- includes libipmctl4
- Upload of this "new" pac
** Changed in: ipmctl (Ubuntu)
Status: New => Triaged
** Changed in: ipmctl (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1868882
Title:
