Hello community,

here is the log from the commit of package yast2-bootloader for 
openSUSE:Factory checked in at 2017-06-24 08:33:28
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/yast2-bootloader (Old)
 and      /work/SRC/openSUSE:Factory/.yast2-bootloader.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "yast2-bootloader"

Sat Jun 24 08:33:28 2017 rev:248 rq:505833 version:3.3.0

Changes:
--------
--- /work/SRC/openSUSE:Factory/yast2-bootloader/yast2-bootloader.changes        
2017-06-17 10:18:18.399384381 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-bootloader.new/yast2-bootloader.changes   
2017-06-24 08:33:29.932494796 +0200
@@ -1,0 +2,8 @@
+Fri Jun 23 09:14:05 CEST 2017 - [email protected]
+
+- AuotYaST configuration: Set StorageDevices flag disks_valid
+  to true. So libstorage can scan valid disks and "/" partition
+  can be found. (bnc#1043132)
+- 3.3.0
+
+-------------------------------------------------------------------

Old:
----
  yast2-bootloader-3.2.22.tar.bz2

New:
----
  yast2-bootloader-3.3.0.tar.bz2

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

Other differences:
------------------
++++++ yast2-bootloader.spec ++++++
--- /var/tmp/diff_new_pack.m7oghD/_old  2017-06-24 08:33:30.516412229 +0200
+++ /var/tmp/diff_new_pack.m7oghD/_new  2017-06-24 08:33:30.520411663 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           yast2-bootloader
-Version:        3.2.22
+Version:        3.3.0
 Release:        0
 
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build

++++++ yast2-bootloader-3.2.22.tar.bz2 -> yast2-bootloader-3.3.0.tar.bz2 ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/yast2-bootloader-3.2.22/package/yast2-bootloader.changes 
new/yast2-bootloader-3.3.0/package/yast2-bootloader.changes
--- old/yast2-bootloader-3.2.22/package/yast2-bootloader.changes        
2017-06-15 08:56:02.918822057 +0200
+++ new/yast2-bootloader-3.3.0/package/yast2-bootloader.changes 2017-06-23 
09:31:14.505722806 +0200
@@ -1,4 +1,12 @@
 -------------------------------------------------------------------
+Fri Jun 23 09:14:05 CEST 2017 - [email protected]
+
+- AuotYaST configuration: Set StorageDevices flag disks_valid
+  to true. So libstorage can scan valid disks and "/" partition
+  can be found. (bnc#1043132)
+- 3.3.0
+
+-------------------------------------------------------------------
 Wed Jun 14 14:54:38 UTC 2017 - [email protected]
 
 - Use udev device for prep partition if it is available
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/yast2-bootloader-3.2.22/package/yast2-bootloader.spec 
new/yast2-bootloader-3.3.0/package/yast2-bootloader.spec
--- old/yast2-bootloader-3.2.22/package/yast2-bootloader.spec   2017-06-15 
08:56:02.918822057 +0200
+++ new/yast2-bootloader-3.3.0/package/yast2-bootloader.spec    2017-06-23 
09:31:14.505722806 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           yast2-bootloader
-Version:        3.2.22
+Version:        3.3.0
 Release:        0
 
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/yast2-bootloader-3.2.22/src/modules/BootStorage.rb 
new/yast2-bootloader-3.3.0/src/modules/BootStorage.rb
--- old/yast2-bootloader-3.2.22/src/modules/BootStorage.rb      2017-06-15 
08:56:03.198822057 +0200
+++ new/yast2-bootloader-3.3.0/src/modules/BootStorage.rb       2017-06-23 
09:31:14.637722806 +0200
@@ -192,8 +192,10 @@
       if Mode.config
         Mode.SetMode("normal")
         log.info "Initialize libstorage in readonly mode" # bnc#942360
+        # Set StorageDevices flag disks_valid to true. So InitLibstorage
+        # can scan valid disks. (bnc#1043132)
+        StorageDevices.InitDone
         Storage.InitLibstorage(true)
-        StorageDevices.InitDone # Set StorageDevices flag disks_valid to true
       end
 
       # The AutoYaST config mode does access to the system.


Reply via email to