Hello community,

here is the log from the commit of package yast2-installation for 
openSUSE:Factory checked in at 2015-08-05 19:14:00
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/yast2-installation (Old)
 and      /work/SRC/openSUSE:Factory/.yast2-installation.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "yast2-installation"

Changes:
--------
--- /work/SRC/openSUSE:Factory/yast2-installation/yast2-installation.changes    
2015-07-22 09:19:37.000000000 +0200
+++ 
/work/SRC/openSUSE:Factory/.yast2-installation.new/yast2-installation.changes   
    2015-08-05 19:14:01.000000000 +0200
@@ -1,0 +2,13 @@
+Wed Aug  5 11:45:25 UTC 2015 - [email protected]
+
+- store cio_ignore settings before installing bootloader
+  (bsc#933177)
+- 3.1.152
+
+-------------------------------------------------------------------
+Fri Jul 24 13:01:22 UTC 2015 - [email protected]
+
+- avoid duplicating release notes for products (bsc#935599)
+- 3.1.151
+
+-------------------------------------------------------------------

Old:
----
  yast2-installation-3.1.150.tar.bz2

New:
----
  yast2-installation-3.1.152.tar.bz2

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

Other differences:
------------------
++++++ yast2-installation.spec ++++++
--- /var/tmp/diff_new_pack.Hfgxxf/_old  2015-08-05 19:14:02.000000000 +0200
+++ /var/tmp/diff_new_pack.Hfgxxf/_new  2015-08-05 19:14:02.000000000 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           yast2-installation
-Version:        3.1.150
+Version:        3.1.152
 Release:        0
 
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build

++++++ yast2-installation-3.1.150.tar.bz2 -> yast2-installation-3.1.152.tar.bz2 
++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/yast2-installation-3.1.150/.travis.yml 
new/yast2-installation-3.1.152/.travis.yml
--- old/yast2-installation-3.1.150/.travis.yml  2015-07-21 11:29:37.000000000 
+0200
+++ new/yast2-installation-3.1.152/.travis.yml  2015-08-05 14:59:11.000000000 
+0200
@@ -5,7 +5,7 @@
     # disable rvm, use system Ruby
     - rvm reset
     - wget 
https://raw.githubusercontent.com/yast/yast-devtools/master/travis-tools/travis_setup.sh
-    - sh ./travis_setup.sh -p "rake yast2-devtools yast2-testsuite 
yast2-core-dev yast2 yast2-network" -g "rspec:2.14.1 yast-rake gettext 
rubocop:0.29.1 simplecov coveralls"
+    - sh ./travis_setup.sh -p "rake yast2-devtools yast2-testsuite 
yast2-core-dev yast2 yast2-network" -g "rspec:3.3.0 yast-rake gettext 
rubocop:0.29.1 simplecov coveralls"
 script:
     - rake check:syntax
     - rake check:pot
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/yast2-installation-3.1.150/doc/proposal_api.md 
new/yast2-installation-3.1.152/doc/proposal_api.md
--- old/yast2-installation-3.1.150/doc/proposal_api.md  2015-07-21 
11:29:37.000000000 +0200
+++ new/yast2-installation-3.1.152/doc/proposal_api.md  2015-08-05 
14:59:11.000000000 +0200
@@ -1,186 +1,8 @@
 # API for YaST2 installation proposal
-## Motivation
-After five releases, YaST2 is now smart enough to make reasonable proposals for
-(near) every installation setting, thus it is no longer necessary to ask the
-user that many questions during installation: Most users simply hit the [next]
-button anyway.
 
-Hence, YaST2 now collects all the individual proposals from its submodules and
-presents them for confirmation right away. The user can change each individual
-setting, but he is no longer required to go through all the steps just to
-change some simple things. The only that (currently) really has to be queried
-is the installation language - this cannot reasonably be guessed (yet?).
+This API lives now in the
+[Installation::ProposalClient 
class](https://github.com/yast/yast-yast2/blob/master/library/general/src/lib/installation/proposal_client.rb)
+which is part of the [YaST basic 
libraries](https://github.com/yast/yast-yast2/).
 
-## Overview
-YaST2 installation modules should cooperate with the main program in a 
consistent API. General usage:
-
-* inst_proposal (main program) creates empty dialog with RichText widget
-
-* inst_proposal calls each sub-module in turn to make proposal
-
-* user may choose to change individual settings (i.e., clicks on a hyperlink)
-
-* inst_proposal starts that module's sub-workflow which runs independently.
-  After this, inst_proposal tells all subsequent (all?) modules to check their
-  states and return whether a change of their proposal is necessary after the
-  user interaction.
-
-* main program calls each sub-module to write the settings to the system
-
-## API functions
-If any parameter is marked as "optional", it should only be specified if
-it contains a meaningful value. Do not add it with a `nil` value.
-
-It is recommended to use Installation::ProposalClient as base class for new 
clients.
-This base class, implemented in yast2-yast, provides automatic method 
dispatching.
-
-### MakeProposal
-Makes proposal for installation.
-
-#### Parameters
-
-* _boolean_ `force_reset` If `true`, discard anything that may be cached and
-  start over from scratch. If `false`, use cached values from the last
-  invocation if there are any.
-
-* _boolean_ `language_changed` The installation language has changed since the 
last call of
-  `MakeProposal`. This is important only if there is a language change 
mechanism in one of the other submodules.
-  If this parameter is "true", any texts the user can see in
-  the proposal need to be retranslated. The internal translator mechanism
-  will take care of this itself if the corresponding strings are once more
-  put through it (the `_("...")` function). Only very few
-  submodules that translate any strings internally based on internal maps
-  (e.g., keyboard etc.) need to take more action.
-
-#### Return Values
-`MakeProposal()` returns a map containing:
-* _list\<string\>_ `links` A list of additional hyperlink ids used in 
summaries returned by this
-      section. All possible values must be included.
-
-* _string_ `preformatted_proposal` (optional) Human readable proposal 
preformatted in HTML. It is possible to use the HTML:: module for such 
formatting.
-
-* _list_ `raw_proposal` (only used if 'preformatted_proposal' is not present 
in the result map). Human readable proposal, not formatted yet. The caller will 
format each
-      list item (string) as a HTML list item `( "<li> ... </li>" )`. The 
proposal can contain hyperlinks with ids listed in the list `links`.
-* _string_ `warning` (optional) Warning in human readable format without HTML 
tags other than `<br>`. The warning will be embedded in appropriate HTML format 
specifications
-      according to 'warning_level' below.
-
-* _symbol_ `warning_level` (optional) Determines the severity and the visual 
display of the warning.
-  Valid values:
-
-  * `:notice`
-  * `:warning (default)`
-  * `:error`
-  * `:blocker`
-  * `:fatal`
-
-  _:blocker_ will prevent the user from continuing the installation. If any 
proposal contains a `:blocker` warning, the "accept"
-  button in the proposal dialog will be disabled - the user needs to fix that 
blocker before continuing.
-
-  _:fatal_ is like `blocker but also stops building the proposal
-
-* _boolean_ `language_changed` This module just caused a change of the 
installation language. This is only relevant for the "language" module.
-* _boolean_ `mode_changed` (optional) This module just caused a change of the 
installation mode. This is only
-  relevant for the "inst mode" module.
-
-* _boolean_ `rootpart_changed` (optional) This module just caused a change of 
the root partition. This is only
-  relevant for the "root part" module.
-
-* _string_ `help` (optional) Helptext for this module which appears in the 
standard dialog
-  help (particular helps for modules sorted by presentation order).
-
-* _map_ `trigger` defines circumstances when the proposal should be called 
again at the end.
-  For intance, when partitioning or software selection changes.
-  Mandatory keys of the trigger are:
-
-  * _map_ `expect` containing _string_ `class` and _string_ `method` that will 
be called and its result compared with `value`
-  * _any_ `value` expected value, if the evaluated code does not match the 
`value`, proposal will be called again
-
-  Example:
-
-      {
-        "trigger" => {
-          "expect" => {
-            "class"  => "Yast::Packages",
-            "method" => "CountSizeToBeDownloaded"
-          }
-          "value" => 88883333
-        }
-      }
-
-### AskUser
-Run an interactive workflow - let user decide upon values he might want to 
change.
-May contain one single dialog, a sequence of dialogs or one master dialog with
-one or more "expert" dialogs. It can be also non-interactive click on 
hyperlink.
-The module is responsible for controlling the workflow sequence (i.e., "next",
-"back" buttons etc.).
-
-Submodules do not provide an "abort" button to abort the entire installation. 
If
-the user wishes to do that, he can always go back to the main dialog (the
-installation proposal) and choose "abort" there.
-
-#### Parameters
-
-* _boolean_ `has_next` Use a "next" button even if the module by itself has 
only one step, thus
-  would normally have an "OK" button - or would rename the "next" button to 
something like "finish" or "accept".
-
-* _string_ `chosen_id` If a section proposal contains hyperlinks and user 
clicks on one of them,
-  this defines the id of the hyperlink. All hyperlink IDs must be set in the 
map retuned by `Description`. If a user did not click
-  on a proposal hyperlink, this parameter is not defined.
-
-#### Return Values
-`AskUser()` returns a map containing:
-
-* _symbol_ workflow_sequence with possible values:
-
-  * `:next` (default) Everything OK - continue with the next step in workflow 
sequence.
-
-  * `:back` User requested to go back in the workflow sequence.
-
-  * `:again` Call this submodule again (i.e., re-initialize the submodule)
-
-  * `:auto` Continue with the workflow sequence in the current direction
-    - forward if the last submodule returned `next, backward otherwise.
-
-  * `:finish` Finish the installation. This is specific to "inst_mode.ycp" when
-    the user selected "boot system" there.
-
-* _boolean_ language_changed (optional) This module just caused a change of 
the installation language. This is
-  only relevant for the "language" module.
-
-### Description
-Return human readable titles both for the RichText (HTML) widget and for 
menuentries.
-
-#### Return Values
-Returns a map containing:
-
-* _string_ `rich_text_title` (Translated) human readable title for this 
section in
-  the `RichText` widget without any HTML formatting. This will be embedded in
-  `<h3><a href="#???"> ... </a></h3>` so make sure not to add any additional 
HTML formatting.
-  Keyboard shortcuts are not (yet?) supported, so do not include any `&` 
characters.
-
-* _string_ `menu_title` (Translated) human readable menuentry for this 
section. Must contain
-  a keyboard shortcut ('&'). Should NOT contain trailing periods ('...') - the 
caller will add them.
-
-* _string_ `id` Programmer readable unique identifier for this section. This 
is not
-  auto-generated to keep the log file readable.
-
-
-This map may be empty. In this case, this proposal section will silently
-be ignored. Proposals modules may use this if there is no useful proposal
-at all. Use with caution - this may be confusing for the user.
-
-In this case, all other proposal functions must return a useful success
-value so they can be called without problems.
-
-### Write
-Write the proposed (and probably modified) settings to the system.
-It is up to the proposal dispatcher how it remembers the settings.
-The errors must be reported using the Report:: module to have
-the possibility to control the behaviour from the main program.
-
-This Write() function is optional. The dispatcher module is required
-    to allow this function to be called without returning an error value
-    if it is not there.
-
-#### Return Values
-Returns true, if the settings were written successfully.
+Autogenerated documentation is available in [Installation::ProposalClient
+documentation](http://www.rubydoc.info/github/yast/yast-yast2/master/Installation/ProposalClient).
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/yast2-installation-3.1.150/package/yast2-installation.changes 
new/yast2-installation-3.1.152/package/yast2-installation.changes
--- old/yast2-installation-3.1.150/package/yast2-installation.changes   
2015-07-21 11:29:37.000000000 +0200
+++ new/yast2-installation-3.1.152/package/yast2-installation.changes   
2015-08-05 14:59:11.000000000 +0200
@@ -1,4 +1,17 @@
 -------------------------------------------------------------------
+Wed Aug  5 11:45:25 UTC 2015 - [email protected]
+
+- store cio_ignore settings before installing bootloader
+  (bsc#933177)
+- 3.1.152
+
+-------------------------------------------------------------------
+Fri Jul 24 13:01:22 UTC 2015 - [email protected]
+
+- avoid duplicating release notes for products (bsc#935599)
+- 3.1.151
+
+-------------------------------------------------------------------
 Tue Jul 21 09:16:03 UTC 2015 - [email protected]
 
 - Moved client code to lib/installation/clients to enable test
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/yast2-installation-3.1.150/package/yast2-installation.spec 
new/yast2-installation-3.1.152/package/yast2-installation.spec
--- old/yast2-installation-3.1.150/package/yast2-installation.spec      
2015-07-21 11:29:37.000000000 +0200
+++ new/yast2-installation-3.1.152/package/yast2-installation.spec      
2015-08-05 14:59:11.000000000 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           yast2-installation
-Version:        3.1.150
+Version:        3.1.152
 Release:        0
 
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/yast2-installation-3.1.150/src/lib/installation/clients/inst_download_release_notes.rb
 
new/yast2-installation-3.1.152/src/lib/installation/clients/inst_download_release_notes.rb
--- 
old/yast2-installation-3.1.150/src/lib/installation/clients/inst_download_release_notes.rb
  2015-07-21 11:29:37.000000000 +0200
+++ 
new/yast2-installation-3.1.152/src/lib/installation/clients/inst_download_release_notes.rb
  2015-08-05 14:59:11.000000000 +0200
@@ -70,15 +70,15 @@
           log.info("Skipping release notes download due to previous download 
issues")
           break
         end
-        if InstData.downloaded_release_notes.include? product["name"]
-          log.info("Release notes for #{product["name"]} already downloaded, 
skipping...")
+        if InstData.downloaded_release_notes.include? product["short_name"]
+          log.info("Release notes for #{product["short_name"]} already 
downloaded, skipping...")
           next
         end
         url = product["relnotes_url"]
         log.debug("URL: #{url}")
         # protect from wrong urls
         if url.nil? || url.empty?
-          log.warn("Skipping invalid URL #{url.inspect} for product 
#{product["name"]}")
+          log.warn("Skipping invalid URL #{url.inspect} for product 
#{product["short_name"]}")
           next
         end
         pos = url.rindex("/")
@@ -108,8 +108,8 @@
           log.info("Downloading release notes: #{cmd} returned #{ret}")
           if ret == 0
             log.info("Release notes downloaded successfully")
-            InstData.release_notes[product["name"]] = 
SCR.Read(path(".target.string"), filename)
-            InstData.downloaded_release_notes << product["name"]
+            InstData.release_notes[product["short_name"]] = 
SCR.Read(path(".target.string"), filename)
+            InstData.downloaded_release_notes << product["short_name"]
             break
           # exit codes (see "man curl"):
           #  7 = Failed to connect to host.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/yast2-installation-3.1.150/src/lib/installation/clients/inst_finish.rb 
new/yast2-installation-3.1.152/src/lib/installation/clients/inst_finish.rb
--- old/yast2-installation-3.1.150/src/lib/installation/clients/inst_finish.rb  
2015-07-21 11:29:37.000000000 +0200
+++ new/yast2-installation-3.1.152/src/lib/installation/clients/inst_finish.rb  
2015-08-05 14:59:11.000000000 +0200
@@ -191,9 +191,9 @@
 
         install_bootloader_steps = [
           "prep_shrink", # ensure that prep partition is small enough for boot 
sector (bnc#867345)
+          "cio_ignore", # needs to be run before initrd is created (bsc#933177)
           "bootloader",
-          ProductFeatures.GetBooleanFeature("globals", "enable_kdump") == true 
? "kdump" : "",
-          "cio_ignore"
+          ProductFeatures.GetBooleanFeature("globals", "enable_kdump") == true 
? "kdump" : ""
         ]
       end
 
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/yast2-installation-3.1.150/src/lib/installation/clients/inst_system_analysis.rb
 
new/yast2-installation-3.1.152/src/lib/installation/clients/inst_system_analysis.rb
--- 
old/yast2-installation-3.1.150/src/lib/installation/clients/inst_system_analysis.rb
 2015-07-21 11:29:37.000000000 +0200
+++ 
new/yast2-installation-3.1.152/src/lib/installation/clients/inst_system_analysis.rb
 2015-08-05 14:59:11.000000000 +0200
@@ -301,7 +301,7 @@
       # push button
       Wizard.ShowReleaseNotesButton(_("Re&lease Notes..."), "rel_notes")
 
-      product_name = Product.name || _("Unknown Product")
+      product_name = Product.short_name || _("Unknown Product")
       InstData.release_notes[product_name] = @media_text
       UI::SetReleaseNotes(product_name => @media_text)
     end


Reply via email to