Hello community,
here is the log from the commit of package yast2-installation for
openSUSE:Factory checked in at 2017-04-12 17:09:52
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/yast2-installation (Old)
and /work/SRC/openSUSE:Factory/.yast2-installation.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "yast2-installation"
Wed Apr 12 17:09:52 2017 rev:384 rq:486430 version:3.2.37
Changes:
--------
--- /work/SRC/openSUSE:Factory/yast2-installation/yast2-installation.changes
2017-03-29 13:23:26.933977897 +0200
+++
/work/SRC/openSUSE:Factory/.yast2-installation.new/yast2-installation.changes
2017-04-12 17:09:54.308865305 +0200
@@ -1,0 +2,19 @@
+Wed Apr 5 11:31:12 CEST 2017 - [email protected]
+
+- Use y2start script instead of y2base (bsc#1027181)
+- 3.2.37
+
+-------------------------------------------------------------------
+Wed Apr 5 10:31:12 CEST 2017 - [email protected]
+
+- Added configuration-management to inst_finish.
+ (FATE#319830)
+- 3.2.36
+
+-------------------------------------------------------------------
+Tue Apr 4 14:16:28 UTC 2017 - [email protected]
+
+- Renamed Controller Node to Administration Node (bsc#1032057).
+- 3.2.35
+
+-------------------------------------------------------------------
Old:
----
yast2-installation-3.2.34.tar.bz2
New:
----
yast2-installation-3.2.37.tar.bz2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ yast2-installation.spec ++++++
--- /var/tmp/diff_new_pack.mSFj9Z/_old 2017-04-12 17:09:54.980770190 +0200
+++ /var/tmp/diff_new_pack.mSFj9Z/_new 2017-04-12 17:09:54.984769624 +0200
@@ -17,14 +17,15 @@
Name: yast2-installation
-Version: 3.2.34
+Version: 3.2.37
Release: 0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
Source0: %{name}-%{version}.tar.bz2
Url: http://github.com/yast/yast-installation
-Requires: yast2-ruby-bindings >= 3.1.8
+# new y2start script
+Requires: yast2-ruby-bindings >= 3.2.10
Summary: YaST2 - Installation Parts
License: GPL-2.0
++++++ yast2-installation-3.2.34.tar.bz2 -> yast2-installation-3.2.37.tar.bz2
++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-installation-3.2.34/doc/control-file.md
new/yast2-installation-3.2.37/doc/control-file.md
--- old/yast2-installation-3.2.34/doc/control-file.md 2017-03-28
23:05:44.313840292 +0200
+++ new/yast2-installation-3.2.37/doc/control-file.md 2017-04-07
14:59:25.082466244 +0200
@@ -798,6 +798,7 @@
System Roles, if defined in the control file, are presented during
the first stage of the installation. The user will select one of them
and they will affect the proposed configuration of Partitioning and Software.
+It also allows to modify configuration of Systemd Services.
A role can also define additional dialogs that are shown when a given role is
selected. It is a common installation dialog with *Abort*, *Cancel* and *Next*
@@ -805,6 +806,20 @@
When going back, it will first show the last additional dialog and when going
back through all additional dialogs, it will show again the roles selection.
+System roles by default preselect first defined entry unless user set it.
+If the first role has an attribute *no_default* then no role will be
+preselected.
+
+Example snippet for no\_default:
+```xml
+<system_roles config:type="list">
+ <system_role>
+ <id>plain</id>
+ <no_default config:type="boolean"> true </no_default>
+ </system_role>
+<system_roles>
+```
+
They were requested in FATE#317481 and they are an evolution of the earlier
concept of Server Scenarios used in SLE 11.
@@ -822,13 +837,25 @@
<system_role>
<id>virtualization_host_kvm</id>
+ <!-- partitioning override -->
<partitioning>
<proposal_lvm config:type="boolean">true</proposal_lvm>
</partitioning>
+ <!-- software override -->
<software>
<default_patterns>base Minimal kvm_server</default_patterns>
</software>
+ <!-- few additional dialogs needed for this role -->
<additional_dialogs>kvm_setup,virt_manager_setup </additional_dialogs>
+ <!-- enable few additional services -->
+ <services config:type="list">
+ <service>
+ <name>salt-minion</name>
+ </service>
+ <service>
+ <name>devil-master</name>
+ </service>
+ </services>
</system_role>
</system_roles>
@@ -871,6 +898,9 @@
and *software* are merged with the corresponding top-level definitions. See
[Partitioning](#partitioning) and [Software](#software).
+The *services* part currently supports only enabling additional services which
+is done by specifying *service* with its *name* as seen in the example.
+
### System Scenarios
System scenarios contain definition of dialog *inst\_scenarios* in the
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-installation-3.2.34/doc/installer_extension.md
new/yast2-installation-3.2.37/doc/installer_extension.md
--- old/yast2-installation-3.2.34/doc/installer_extension.md 1970-01-01
01:00:00.000000000 +0100
+++ new/yast2-installation-3.2.37/doc/installer_extension.md 2017-04-07
14:59:25.082466244 +0200
@@ -0,0 +1,180 @@
+# Modifying the Installation by an Add-on
+
+The YaST installation workflow can be easily changed or extended by add-ons.
+
+## Configuring the Add-on Metadata
+
+The product package on the add-on medium (usually a `*-release` RPM package)
+should link to a package providing the installer extension by a
+`Provides: installerextension(<package_name>)` dependency.
+
+That referenced package should contain the `installation.xml` file and
optionally
+the `y2update.tgz` archive in the root directory. The package should never
+be installed into system, it is used just to provide the temporary data for the
+installer. After the installation is finished the files are not needed anymore.
+
+## Modifying the Installation Workflow
+
+This `installation.xml` example has two parts:
+
+- The first part adds a new step into the add-on installation workflow in
already
+ installed system.
+- The second part adds a new step into the initial installation workflow.
+
+```xml
+<?xml version="1.0"?>
+<productDefines xmlns="http://www.suse.com/1.0/yast2ns";
xmlns:config="http://www.suse.com/1.0/configns";>
+ <workflows config:type="list">
+ <!-- Installation on a running system -->
+ <workflow>
+ <stage>normal</stage>
+ <mode>installation,normal</mode>
+
+ <defaults>
+ <enable_back>no</enable_back>
+ <enable_next>no</enable_next>
+ </defaults>
+
+ <modules config:type="list">
+ <module>
+ <label>Extension Configuration</label>
+ <name>testing_extension</name>
+ <execute>inst_testing_extension</execute>
+ <enable_back>yes</enable_back>
+ <enable_next>yes</enable_next>
+ </module>
+ </modules>
+ </workflow>
+ </workflows>
+
+ <update>
+ <workflows config:type="list">
+ <workflow>
+ <defaults>
+ <enable_back>yes</enable_back>
+ <enable_next>yes</enable_next>
+ </defaults>
+
+ <!-- First Stage Installation -->
+ <stage>initial</stage>
+ <mode>installation</mode>
+
+ <!-- Insert new steps -->
+ <insert_modules config:type="list">
+ <insert_module>
+ <before>system_role</before>
+ <modules config:type="list">
+ <module>
+ <label>Extension Configuration</label>
+ <name>testing_extension</name>
+ <!-- Name of the executed file without the .rb
extension -->
+ <execute>inst_testing_extension</execute>
+ </module>
+ </modules>
+ </insert_module>
+ </insert_modules>
+ </workflow>
+ </workflows>
+ </update>
+</productDefines>
+```
+
+## Adding a New System Role
+
+This `installation.xml` example adds a new role:
+
+```xml
+<?xml version="1.0"?>
+<productDefines xmlns="http://www.suse.com/1.0/yast2ns";
xmlns:config="http://www.suse.com/1.0/configns";>
+ <update>
+ <system_roles>
+ <insert_system_roles config:type="list">
+ <insert_system_role>
+ <system_roles config:type="list">
+ <system_role>
+ <id>mail_role</id>
+ <software>
+ <default_patterns>base Minimal
mail_server</default_patterns>
+ </software>
+ </system_role>
+ </system_roles>
+ </insert_system_role>
+ </insert_system_roles>
+ </system_roles>
+ </update>
+
+ <!-- Don't forget to add the texts -->
+ <texts>
+ <mail_role>
+ <label>Testing Extension Role</label>
+ </mail_role>
+ <mail_role_description>
+ <label>• Mail server software pattern
+• This is just an example!</label>
+ </mail_role_description>
+ </texts>
+</productDefines>
+```
+
+In this case it just configures the default software patterns but it is
possible
+to define any other defaults like partitioning, etc...
+
+## Adding New YaST Code
+
+The installer extension package can optionally contain `y2update.tgz` archive
+with executable YaST code in the usual directory structure. E.g. the clients
are
+read from the `/usr/share/YaST2/clients` directory in the archive.
+
+### YaST Client Example
+
+Here is a trivial example client which just displays a pop up dialog with a
message:
+
+```ruby
+module Yast
+ class TestingExtensionClient < Client
+ include Yast::I18n
+
+ def initialize
+ textdomain "testing-extension"
+ Yast.import("Popup")
+ end
+
+ def main
+ # TRANSLATORS: A popup message
+ Popup.Message(_("This is an inserted step from the testing-extension
addon."\
+ "\n\nPress OK to continue."))
+ return :auto
+ end
+ end
+end
+
+Yast::TestingExtensionClient.new.main
+```
+
+Save this file to `usr/share/YaST2/clients/inst_testing_extension.rb` file
(including
+the directory structure) and then create the `y2update.tgz` archive with
command
+
+```
+tar cfzv y2update.tgz usr
+```
+
+and include it in the installer extension RPM package.
+
+# An Example Add-on
+
+A minimalistic but complete example add-on can be found in the
[YaST:extension](
+https://build.opensuse.org/project/show/YaST:extension) OBS project.
+
+The [testing-extension-release package](
+https://build.opensuse.org/package/show/YaST:extension/testing-extension-release)
+links to the installer extension using `Provides:
+installerextension(testing-extension-installation)`.
+
+The [testing-extension-installation package](
+https://build.opensuse.org/package/show/YaST:extension/testing-extension-installation)
+contains the `installation.xml` file which defines an additional role and
+adds a new installation step before the role selection dialog. The new
installation
+step is defined in the included `y2update.tgz` file.
+
+
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-installation-3.2.34/package/yast2-installation.changes
new/yast2-installation-3.2.37/package/yast2-installation.changes
--- old/yast2-installation-3.2.34/package/yast2-installation.changes
2017-03-28 23:05:44.333840292 +0200
+++ new/yast2-installation-3.2.37/package/yast2-installation.changes
2017-04-07 14:59:25.098466244 +0200
@@ -1,4 +1,23 @@
-------------------------------------------------------------------
+Wed Apr 5 11:31:12 CEST 2017 - [email protected]
+
+- Use y2start script instead of y2base (bsc#1027181)
+- 3.2.37
+
+-------------------------------------------------------------------
+Wed Apr 5 10:31:12 CEST 2017 - [email protected]
+
+- Added configuration-management to inst_finish.
+ (FATE#319830)
+- 3.2.36
+
+-------------------------------------------------------------------
+Tue Apr 4 14:16:28 UTC 2017 - [email protected]
+
+- Renamed Controller Node to Administration Node (bsc#1032057).
+- 3.2.35
+
+-------------------------------------------------------------------
Mon Mar 27 13:39:38 UTC 2017 - [email protected]
- Move CaaSP specific code to yast2-caasp (bsc#1030874)
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-installation-3.2.34/package/yast2-installation.spec
new/yast2-installation-3.2.37/package/yast2-installation.spec
--- old/yast2-installation-3.2.34/package/yast2-installation.spec
2017-03-28 23:05:44.333840292 +0200
+++ new/yast2-installation-3.2.37/package/yast2-installation.spec
2017-04-07 14:59:25.098466244 +0200
@@ -17,7 +17,7 @@
Name: yast2-installation
-Version: 3.2.34
+Version: 3.2.37
Release: 0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
@@ -26,7 +26,8 @@
Group: System/YaST
License: GPL-2.0
Url: http://github.com/yast/yast-installation
-Requires: yast2-ruby-bindings >= 3.1.8
+# new y2start script
+Requires: yast2-ruby-bindings >= 3.2.10
Summary: YaST2 - Installation Parts
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-installation-3.2.34/src/lib/installation/clients/inst_finish.rb
new/yast2-installation-3.2.37/src/lib/installation/clients/inst_finish.rb
--- old/yast2-installation-3.2.34/src/lib/installation/clients/inst_finish.rb
2017-03-28 23:05:44.345840292 +0200
+++ new/yast2-installation-3.2.37/src/lib/installation/clients/inst_finish.rb
2017-04-07 14:59:25.114466244 +0200
@@ -391,7 +391,8 @@
"installation_settings",
"roles",
"services",
- "services-manager"
+ "services-manager",
+ "configuration_management"
].freeze
def save_settings_steps
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-installation-3.2.34/src/lib/installation/widgets/system_role.rb
new/yast2-installation-3.2.37/src/lib/installation/widgets/system_role.rb
--- old/yast2-installation-3.2.34/src/lib/installation/widgets/system_role.rb
2017-03-28 23:05:44.357840292 +0200
+++ new/yast2-installation-3.2.37/src/lib/installation/widgets/system_role.rb
2017-04-07 14:59:25.122466244 +0200
@@ -34,10 +34,11 @@
module Widgets
# This widget is responsible of validate and store the introduced location
# which must be a valid IP or FQDN.
+ # bsc#1032057: old name: Controller Node, new name: Administration Node.
class ControllerNode < CWM::InputField
def label
# intentional no translation for CAASP
- "Controller Node"
+ "Administration Node"
end
# It stores the value of the input field if validates
@@ -60,8 +61,8 @@
return true if Yast::IP.Check(value) || Yast::Hostname.CheckFQ(value)
Yast::Popup.Error(
- # TRANSLATORS: error message for invalid controller node location
- _("Not valid location for the controller node, " \
+ # TRANSLATORS: error message for invalid administration node location
+ _("Not valid location for the administration node, " \
"please enter a valid IP or Hostname")
)
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-installation-3.2.34/startup/YaST2.call
new/yast2-installation-3.2.37/startup/YaST2.call
--- old/yast2-installation-3.2.34/startup/YaST2.call 2017-03-28
23:05:44.369840292 +0200
+++ new/yast2-installation-3.2.37/startup/YaST2.call 2017-04-07
14:59:25.134466244 +0200
@@ -154,7 +154,7 @@
set_splash 100
#=============================================
- # Setup y2base options
+ # Setup y2start options
#---------------------------------------------
Y2_UI_ARGS="--fullscreen --noborder --auto-fonts"
@@ -206,7 +206,7 @@
# NCURSES mode as fallback ?
# ---
log "\tX-Server couldn't be started, falling back to
ncurses"
- Y2_MODE_FLAGS='("text_fallback")'
+ Y2_MODE_FLAGS="--arg text_fallback"
SELECTED_MEDIUM="NCURSES"
prepare_for_ncurses
Y2_MODE=ncurses
@@ -329,10 +329,10 @@
log "\tQT_IM_MODULE: $QT_IM_MODULE"
if [ "$Y2GDB" != "1" ]; then
- $OPT_FBITERM y2base \
+ $OPT_FBITERM y2start \
"$Y2_MODULE_NAME" \
$Y2_MODE_FLAGS \
- $Y2_MODULE_ARGS \
+ $Y2_MODULE_ARGS \
$Y2_MODE \
$Y2_UI_ARGS
Y2_EXIT_CODE=$?
@@ -341,11 +341,11 @@
echo tty /dev/tty10 > $GDBCMDS
echo set args "$Y2_MODULE_NAME" \
$Y2_MODE_FLAGS \
- "'"$Y2_MODULE_ARGS"'" \
+ $Y2_MODULE_ARGS \
$Y2_MODE \
$Y2_UI_ARGS >> $GDBCMDS
echo set pagination off >> $GDBCMDS
- /usr/bin/gdb -x $GDBCMDS /usr/lib/YaST2/bin/y2base | \
+ /usr/bin/gdb -x $GDBCMDS /usr/lib/YaST2/bin/y2start | \
tee /var/log/YaST2/gdb-log
Y2_EXIT_CODE=$?
fi
@@ -653,7 +653,10 @@
# 8) Call YaST2
#---------------------------------------------
Y2_MODULE_NAME=${1:-installation}; shift
-Y2_MODULE_ARGS=\(\"$*\"\)
+Y2_MODULE_ARGS=""
+for i in "$@"; do
+ Y2_MODULE_ARGS="$Y2_MODULE_ARGS --arg $i"
+done
start_yast
#=============================================
