Hi Antoine, I hit this in NEW queue review and there is nothing that needs to hard block this, but one detail I wondered - the --no-start has gladly been discussed here but I think this aspect has been lost.
I see Chris already raised my point in comment #8 """ This is strange — this will automatically start the nvidia-mig-manager service next boot, but not immediately on install. This is not what policy would usually suggest (either immediately start or not start until explicitly enabled). """ You went on (good) explaining why --no-start is used. But I lack to find/understand why --no-enable is not used. Just like Chris I'd usually expect "either immediately start" (default) "or not start until explicitly enabled" (--no-start + --no-enable). The reasoning in the comment explains why --no-start but it leaves open and questionable why --no-enable was not used. I read most of the bug here but could not find it either. Do you want to explain or change this detail before it is accepted? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2139070 Title: [needs-packaging] mig-parted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2139070/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
