https://bugzilla.novell.com/show_bug.cgi?id=784980 https://bugzilla.novell.com/show_bug.cgi?id=784980#c0 Summary: Error "source_dir does not exist. Please specify --target or --directory" when updating GRUB2 on UEFI platform Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain@suse.com ReportedBy: arvidjaar@gmail.com QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.8) Gecko/20100101 Firefox/10.0.8 When updating grub2 package it tries to update core.img in postinstall script. grub2-install auto-detects current architecture, which in case of UEFI system is always {i386,x86_64}-efi. Because it runs /usr/sbin/grub2-install which was compiled with "grub2" transform, it looks for architecture specific modules under /usr/lib/grub2/{i386,x86_64}-efi. This directory does not exist because it is unstalled under different prefix - /usr/lib/grub2-efi. Even if it existed, grub2-efi is not yet updated when grub2 post runs; it has to be done in grub2-efi post. I set it to MAJOR because effectively it means core.img (or grub{32,64}.efi) is NOT updated on update on UEFI systems. Leading to any hard to debug errors (when it tries to access modules from different version). This is related to https://bugzilla.novell.com/show_bug.cgi?id=782891. Unifying grub2 and grub2-efi would eliminate this issue entirely. Alternative clean fix would be to split each /usr/lib/grub2/${target} in separate subpackage and run grub2-install with explicit --target=${target} in each subpackage. Is there any mailing list where this can be discussed (it is probably not for Bugzilla)? I think that for 12.2 the minimal fix is to add grub2-efi-mkconfig to grub2-efi post and explicitly specify --target in post for grub2 package. WDYT? Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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.