Comment # 19 on bug 1179981 from Marco M.

(In reply to Michael Chang from comment #18)
> Hi Marco,
> 
> I have updated the package to address the metadata 1.0 problem we just
> discussed. Would you please verify if that can work for you ?
> 
> Thanks in advanced.

Hi,
I've just installed your updated packages and this time results looks good!
At first i installed the patch and the posttrans scripts did not report any
error. 
But my efivars were still pointing to shim because the last time I left the
test machine with secureboot enabled in yast. So I launched yast, removed
secureboot settings and saved. I did not receive any erros and evivars are now
correctly set as shown below:

**************
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0002,0001,0003,000B,0000,000A
Boot0000* UiApp
FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)
Boot0001* opensuse (vda1)
       
HD(1,GPT,d12112d2-e2a6-49bd-9f4c-9e22b9504f84,0x800,0xfa000)/File(\EFI\opensuse\grubx64.efi)
Boot0002* opensuse (vdb1)
       
HD(1,GPT,481918fa-c9a3-4f74-a05f-96237355c4c8,0x800,0xfa000)/File(\EFI\opensuse\grubx64.efi)
Boot0003* UEFI QEMU DVD-ROM QM00005    
PciRoot(0x0)/Pci(0x6,0x0)/Sata(0,65535,0)N.....YM....R,Y.
Boot000A* EFI Internal Shell   
FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
**************

Reboot was fine. 
I also manually launched update-bootloader and grub2-install, in both cases
results looks good (no error and efivars correctly set).

I'm planning to do a more complete test reinstalling from scratch, avoiding
shim since the beginning (grub only) and I'll let you know, but I'm confident
the it will work.

Thank you very much