https://bugzilla.novell.com/show_bug.cgi?id=782891 https://bugzilla.novell.com/show_bug.cgi?id=782891#c10 --- Comment #10 from Michael Chang <mchang@suse.com> 2012-10-25 07:16:44 UTC --- (In reply to comment #9)
(In reply to comment #7)
A quick question, why you choose to use %triggerpostun but not %postun?
because %postun of *old* package does not know anything about it and we obviously cannot change it. And %postun of *new* package does not run when removing *old* package.
(In reply to comment #8)
More specifically .. the question is
%triggerpostun -- %{name}-efi vs %postun efi
What happens on update is
1. new version of grub2-efi is installed 2. %post of *new* version runs and creates /boot/grub2-efi -> grub2 3. *old* version of grun2-efi is uninstalled. It removes /boot/grub2-efi/grub.cfg
I could not add /boot/grub2-efi/grub.cfg to new version as ghost, it conflicts with /boot/grub2-efi being symlink. And the only way to add code that runs after removal of *old* package was trigger (and trigger on different package too, trigger on grub2-efi would not work :) )
Thanks for explanation, now I understand.
Please submit
It needed some work, in particular, link was not created on new install or when bootloader was not grub2-efi (could happen e.g. for elilo). I updated it and appreciate if you could verify it once more. Thank you.
I've tested your new package, still no problem found. This time is a new installation as you requested. My procedure. 1. New installation using elilo 2. When system boots, remove grub2 grub2-efi package 3. rm -rf /boot/grub2 and /boot/grub2-efi, make sure no left in the system 4. Install new grub2 grub2-efi downloaded from your repo 5. Run yast2 bootloader, select grub2-efi and install 6. Reboot, grub2-efi was used and booted with any problem Great, and really appreciate your hard work on this. :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.