https://bugzilla.novell.com/show_bug.cgi?id=782891 https://bugzilla.novell.com/show_bug.cgi?id=782891#c9 --- Comment #9 from Andrey Borzenkov <arvidjaar@gmail.com> 2012-10-24 15:56:53 UTC --- (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 :) )
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. -- 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.