Hi Samuel, I agree that the severity should not be release-critical since it is not a regression.
When I introduced this package, I could only test it on the Amazon cloud, where it did not make sense to have a separate /boot partition. In addition, the MBR of the instances can not be modified, so the regular grub-legacy package could not be installed, which was one the justification for creating this package (the other being to clean the cloud-init package when importing initially from Ubuntu, which contained the ancestor of pv-grub-menu as part of the package diff). In your system, can't pv-grub-menu be replaced by grub-legacy ? In any case, you are very welcome to enhance pv-grub-menu to support your use case. The source package is in collab-maint. The original work for pv-grub-menu, Ubuntu's grub-legacy-ec2, seemed to be a partial fork of Ubuntu's grub-legacy, that itself had accumulated a large quantity of difference from Debian's grub-legacy, which is in maintainance mode. This was way too hard to maintain for me and I trimmed the main script (http://anonscm.debian.org/cgit/collab-maint/pv-grub-menu.git/log/update-menu-lst), in order to obtain something that I could understand. But please feel free to add some complexity back. Or if you prefer, you can also rewrite it altogether. What we need is a generator for menu.lst, and it does not necessary need to be a fork of grub-legacy. Have a nice day, Charles -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
