/sbin/update-grub complains about being run instead of /usr/sbin/update-grub
Bug #78552 reported by
Bogdan Butnaru
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub (Ubuntu) |
Invalid
|
Undecided
|
Steve Langasek | ||
linux-meta (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
ubiquity (Baltix) |
Invalid
|
Undecided
|
Unassigned | ||
update-manager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: linux-image-2.6-386
Each time one of the linux-image-2.6.* packages is added or removed, I get the warning:
"You shouldn't call /sbin/update-grub. Please call /usr/sbin/
-- although the call isn't made by me, but by the package manager. From what I can tell from the /sbin/update-grub script, this is a mis-configuration of the package.
I don't remember seeing this in Edgy. I'm running Feisty, and I get this message for every linux-image-* package I've tried. For instance, I got it for "sudo aptitude remove linux-image-
Changed in update-manager: | |
status: | Unconfirmed → Rejected |
Changed in grub: | |
status: | Unconfirmed → Confirmed |
Changed in grub: | |
assignee: | nobody → vorlon |
milestone: | ubuntu-7.04 → none |
To post a comment you must log in.
More exactly, the message is as follow:
Running postrm hook script /sbin/update-grub. img.conf needs to be updated. Read grub's NEWS.Debian[1]
Your /etc/kernel-
file and follow its instructions.
1. /usr/share/ doc/grub/ NEWS.Debian. gz
You shouldn't call /sbin/update-grub. Please call /usr/sbin/ update- grub instead!
Searching for GRUB installation directory ... found: /boot/grub
Looking at /usr/share/ doc/grub/ NEWS.Debian. gz, /sbin/update-grub has been moved to /usr/sbin/ update- grub
NEWS.Debian.gz says that you _must_ edit /etc/kernel- img.conf and change:
postinst_hook = /sbin/update-grub
postrm_hook = /sbin/update-grub
to update- grub update- grub
postinst_hook = /usr/sbin/
postrm_hook = /usr/sbin/
In the meanwhile, a wrapper is provided to keep backward compatibility.
I don't know yet if kernel-img.conf will be automatically updated in a close future so I change this bug status to confirmed.
I believe people installing brand new feisty will get their kernel-img.conf properly configured.