FS#54600 - [linux-hardened] When updating from linux-grsec, no grub-mkconfig is made

Attached to Project: Community Packages
Opened by Chris (h8h) - Monday, 26 June 2017, 17:32 GMT
Last edited by Daniel Micay (thestinger) - Monday, 26 June 2017, 19:56 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Daniel Micay (thestinger)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


If people use linux-grsec and linux-hardend replaces linux-grsec no grub-mkconfig is made. On reboot, fresh system boot, grub searchs for the grsec kernel and doesn't find it.

I think a posthook is missing, triggering grub-mkconfig or simlar command.

Steps to reproduce:
1. pacman -S linux-grsec
2. pacman -Syu
3. pacman replaces linux-grsec with linux-hardend
4. reboot
5. Grub has troubles

This task depends upon

Closed by  Daniel Micay (thestinger)
Monday, 26 June 2017, 19:56 GMT
Reason for closing:  Not a bug
Additional comments about closing:  This is how it was intended to happen. It would have been nice to write a post-install message and/or a news item but there's limited time and no one has had interest in helping. A patch adding a post-install message for the linux-grsec upgrade case would still be accepted but it's a bit late.
Comment by Doug Newgard (Scimmia) - Monday, 26 June 2017, 17:41 GMT
Yeah, it probably shouldn't have "replaces" in the PKGBUILD.
Comment by Daniel Micay (thestinger) - Monday, 26 June 2017, 19:53 GMT
It wasn't intended to be an intervention-free automatic migration, only a way to providing notification that Arch's linux-grsec package is dead and gone with linux-hardened as the only replacement. I didn't write a guide for the post-install message because I thought what was going on was straightforward. I don't want grub configuration integration.