Comment # 12 on bug 897847 from
(after updating the above a bit, at least I see it attempt the rebranding now)

This also can't really work it sees

      # FIXME workaround grub2 need manual rerun of branding due to overwrite
by
      # pbl. see bnc#879686 and bnc#901003
      Builtins.y2milestone(Bootloader.getLoaderType)
      if Bootloader.getLoaderType =~ /grub2/
        prefix = Installation.destdir
        branding_activator =
Dir["#{prefix}/usr/share/grub2/themes/*/activate-theme"].first
        if branding_activator
          branding_activator = branding_activator[prefix.size..-1]
          res = SCR.Execute(path(".target.bash_output"), branding_activator)
        end
      end

Correspndidng extract from y2log-1 (some added debug statements)

2014-10-24 20:26:24 <1> linux.site(2944) [Ruby]
clients/bootloader_finish.rb:183 Installation started with kexec_reboot set 0

2014-10-24 20:26:24 <1> linux.site(2944) [Ruby]
clients/bootloader_finish.rb:209 Rebraning activator is
/mnt/usr/share/grub2/themes/openSUSE/activate-theme
=> expected, after al we're in stage one, after applying the image on the disk.
The NEW setup is inside /mnt

2014-10-24 20:26:25 <1> linux.site(2944) [Ruby]
clients/bootloader_finish.rb:214 Reactivate branding with
/usr/share/grub2/themes/openSUSE/activate-theme and result {"exit"=>0,
"stderr"=>"", "stdout"=>""}
=> that might work, after all it's pretty much a copy. But not very obviousy.
Most of all: it does not write the configuration to /mnt => hence, still no
luck

The script /usr/share/grub2/themes/openSUSE/activate-theme has absolutely no
idea how to handle a different prefix; so whatever the idea is here: it can't
work as-is


You are receiving this mail because: