Hello community,

here is the log from the commit of package shim for openSUSE:Factory checked in 
at 2016-09-09 10:15:19
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/shim (Old)
 and      /work/SRC/openSUSE:Factory/.shim.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "shim"

Changes:
--------
--- /work/SRC/openSUSE:Factory/shim/shim.changes        2016-08-17 
11:59:48.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.shim.new/shim.changes   2016-09-09 
10:15:23.000000000 +0200
@@ -1,0 +2,5 @@
+Fri Aug 19 06:46:59 UTC 2016 - [email protected]
+
+- shim-install : fix regression of password prompt (bsc#993764) 
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ shim.spec ++++++
--- /var/tmp/diff_new_pack.shvCLl/_old  2016-09-09 10:15:24.000000000 +0200
+++ /var/tmp/diff_new_pack.shvCLl/_new  2016-09-09 10:15:24.000000000 +0200
@@ -1,7 +1,7 @@
 #
 # spec file for package shim
 #
-# Copyright (c) 2016 SUSE LINUX GmbH, Nuernberg, Germany.
+# Copyright (c) 2016 SUSE LINUX Products GmbH, Nuernberg, Germany.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed

++++++ shim-install ++++++
--- /var/tmp/diff_new_pack.shvCLl/_old  2016-09-09 10:15:24.000000000 +0200
+++ /var/tmp/diff_new_pack.shvCLl/_new  2016-09-09 10:15:24.000000000 +0200
@@ -237,6 +237,7 @@
 make_grubcfg () {
 
 grub_cfg_dirname=`dirname $grub_cfg`
+grub_cfg_basename=`basename $grub_cfg`
 cfg_fs_uuid=`"$grub_probe" --target=fs_uuid "$grub_cfg_dirname"`
 
 if test "x$SUSE_BTRFS_SNAPSHOT_BOOTING" = "xtrue"; then
@@ -257,8 +258,7 @@
 cat <<EOF
 search --fs-uuid --set=root ${cfg_fs_uuid}
 set prefix=(\${root})`${grub_mkrelpath} ${grub_cfg_dirname}`
-normal_exit
-normal
+source "\${prefix}/${grub_cfg_basename}"
 EOF
 
 }


Reply via email to