Hello Christian and thank you for the review, In my humble opinion, it all makes sense. Since launching the program will trigger a reboot if done right after installation
1. We use --no-start to prevent that 2. We trigger the "reboot required" notification from the maintainer scripts, so that the user reboots 3. The user reboots, the service starts (since it's enabled), everything is fine. The --no-start is only here because of this reboot requirement, we do want the service to be enabled by default. Do you want me to clarify the explanation within the rules file? -- 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
