I understand your frustrations, but please calm down. Expletives don't help anyone. I am not a dev, I merely triage bugs. And only by chance did I revisit this ticket now.
I'll gladly explain how this works. This ticket is marked fix for the latest development release which by now is precise. Any release with 1.99~rc1-13ubuntu3 or later will not be affected. Unfortunately, that does not include Lucid. So, what will need to happen is an SRU (https://wiki.ubuntu.com/StableReleaseUpdates). In the most simple terms, someone needs to come up with a minimal patch to address this and only this problem. Any unrelated changes in code or updating the whole package would not be permissible. Thus, I labeled this ticket as "Affecting lucid" to request such a backport. Alas, I'm not sure this will happen in due time, but it's out of my control. I hope you will find this explanation of the process at least helpful. I agree the result is not always pretty, but it's the best the community can do. LTS should not be confused with bug-free or the focus of development. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/878070 Title: /usr/sbin/grub-probe: error: no mapping exists for `rootvol-boot'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/878070/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
