Commenting since the report still exists in the bug DB... I've found `os-prober` often produces many false positive OS installation detections. As such I really find recommends too strong, simply including during installation and then merely suggests would be better.
If someone removes it, likely that is due to not needing it and the choice should be honored. Worse, on VM systems searching for additional OS installations is a major security risk due to potential for finding VMs instead of host. If one of those manages to boot on bare hardware, everything is compromised. Producing messages during updates though is reasonable. Just don't be too pushy, even keeping recommends packages from being reinstalled requires a careful eye. Mostly documenting some people *really* don't want os-prober, even though we are likely the minority. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sig...@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445