Hello community,
here is the log from the commit of package yast2-installation for
openSUSE:Factory checked in at 2015-11-12 19:39:43
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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-10-20 16:21:56.000000000 +0200
+++
/work/SRC/openSUSE:Factory/.yast2-installation.new/yast2-installation.changes
2015-11-12 19:39:44.000000000 +0100
@@ -1,0 +2,7 @@
+Fri Nov 6 11:59:26 UTC 2015 - [email protected]
+
+- Ensure second stage and YaST-Firstboot don't get killed by
+ getty when running over serial console (bsc#935965)
+- 3.1.162
+
+-------------------------------------------------------------------
Old:
----
yast2-installation-3.1.161.tar.bz2
New:
----
yast2-installation-3.1.162.tar.bz2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ yast2-installation.spec ++++++
--- /var/tmp/diff_new_pack.IlajOP/_old 2015-11-12 19:39:45.000000000 +0100
+++ /var/tmp/diff_new_pack.IlajOP/_new 2015-11-12 19:39:45.000000000 +0100
@@ -17,7 +17,7 @@
Name: yast2-installation
-Version: 3.1.161
+Version: 3.1.162
Release: 0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++++++ YaST2-Firstboot.service ++++++
--- /var/tmp/diff_new_pack.IlajOP/_old 2015-11-12 19:39:45.000000000 +0100
+++ /var/tmp/diff_new_pack.IlajOP/_new 2015-11-12 19:39:45.000000000 +0100
@@ -1,7 +1,7 @@
[Unit]
Description=YaST2 Firstboot
After=apparmor.service local-fs.target YaST2-Second-Stage.service
plymouth-start.service
[email protected] display-manager.service network.service
NetworkManager.service
[email protected] [email protected] display-manager.service
network.service NetworkManager.service
ConditionPathExists=/var/lib/YaST2/reconfig_system
[Service]
++++++ YaST2-Second-Stage.service ++++++
--- /var/tmp/diff_new_pack.IlajOP/_old 2015-11-12 19:39:45.000000000 +0100
+++ /var/tmp/diff_new_pack.IlajOP/_new 2015-11-12 19:39:45.000000000 +0100
@@ -3,7 +3,7 @@
# If xinetd is enabled, make sure it's already running so we can stop it during
# initialization of the VNC server
After=apparmor.service local-fs.target plymouth-start.service
[email protected] display-manager.service network.service
NetworkManager.service SuSEfirewall2_init.service SuSEfirewall2.service
[email protected] [email protected] display-manager.service
network.service NetworkManager.service SuSEfirewall2_init.service
SuSEfirewall2.service
ConditionPathExists=/var/lib/YaST2/runme_at_boot
[Service]
++++++ yast2-installation-3.1.161.tar.bz2 -> yast2-installation-3.1.162.tar.bz2
++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-installation-3.1.161/doc/control-file.md
new/yast2-installation-3.1.162/doc/control-file.md
--- old/yast2-installation-3.1.161/doc/control-file.md 2015-10-15
09:54:10.000000000 +0200
+++ new/yast2-installation-3.1.162/doc/control-file.md 2015-11-06
15:41:38.000000000 +0100
@@ -198,7 +198,7 @@
The following listing shows a typical installation workflow:
-```
+```xml
<workflows config:type="list">
<workflow>
<!-- 'label' is what the user will see -->
@@ -265,7 +265,7 @@
possible using the control file.
-```
+```xml
<proposal>
<type>network</type>
<stage>continue,normal</stage>
@@ -297,7 +297,7 @@
proposals. The following examples shows how the network proposal is
called as a workflow step:
-```
+```xml
<module>
<label>Network</label>
<name>proposal</name>
@@ -330,7 +330,7 @@
the following example shows all options above
-```
+```xml
<globals>
<enable_autologin config:type="boolean">true</enable_autologin>
<language>de_DE</language>
@@ -339,6 +339,7 @@
<io_scheduler>as</io_scheduler>
</globals>
```
+
### Special Installation and Product Variables
These options usually enable or disable some installation feature.
@@ -409,7 +410,7 @@
This example shows how content of the */root/* directory is copied
to the */root/inst-sys/* directory on the installed system:
-```
+```xml
<globals>
<save_instsys_content config:type="list">
<save_instsys_item>
@@ -444,7 +445,7 @@
See the example:
-```
+```xml
<globals>
<copy_to_system config:type="list">
<copy_to_system_item>
@@ -519,7 +520,7 @@
This is an example of AC setup:
-```
+```xml
<productDefines xmlns="http://www.suse.com/1.0/yast2ns";
xmlns:config="http://www.suse.com/1.0/configns";>
<globals>
@@ -619,7 +620,7 @@
list of regular expressions matching installed product name
(SuSE-release).
-```
+```xml
<!-- Delete old packages of all products but OES, SLES 9, SLE 10 and SLD
10 -->
<software>
<delete_old_packages config:type="boolean">true</delete_old_packages>
@@ -649,7 +650,7 @@
defined as list of regular expressions matching installed product
name (SuSE-release).
-```
+```xml
<!-- For SLES10, packages are not downgraded -->
<software>
<silently_downgrade_packages
config:type="boolean">true</silently_downgrade_packages>
@@ -670,7 +671,7 @@
Inverts the *only\_update\_selected* for products defined as list of
regular expressions matching installed product name (SuSE-release).
-```
+```xml
<!--
Only update packages but install new packages
when upgrading any SUSE Linux or openSUSE
@@ -690,7 +691,7 @@
List of known products supported for upgrade (SuSE-release). Old
releases or other distributions will report warning.
-```
+```xml
<software>
<products_supported_for_upgrade config:type="list">
<regexp_item>^Novell LINUX Desktop 9.*</regexp_item>
@@ -739,7 +740,7 @@
Example of supported desktops:
-```
+```xml
<productDefines xmlns="http://www.suse.com/1.0/yast2ns";
xmlns:config="http://www.suse.com/1.0/configns";>
<software>
@@ -817,7 +818,9 @@
- (string) *packages*
- (whitespace-separated).
+ List of packages (whitespace-separated) that identify and verify which
+ desktop has been selected by user (or automatically). These packages are
+ *not* selected for installation by Yast, use *patterns* for that.
- (integer) *order*
@@ -828,7 +831,7 @@
- (string) *patterns*
- Patterns to select for the desktop (whitespace-separated).
+ Patterns to select for a particular desktop (whitespace-separated).
- (string) *icon*
@@ -847,7 +850,7 @@
Example of configured scenarios:
-```
+```xml
<productDefines xmlns="http://www.suse.com/1.0/yast2ns";
xmlns:config="http://www.suse.com/1.0/configns";>
<software>
@@ -916,7 +919,7 @@
Selection labels must be defined in [texts](#control_texts) section.
Scenarios *id*s are used as link identificators.
-```
+```xml
<software>
<system_scenario>
<id></id>
@@ -1172,7 +1175,7 @@
*use\_flexible\_partitioning* option must be se to *true* and
*partitions* must be surrounded with *flexible\_partitioning* tag.
-```
+```xml
<partitioning>
<use_flexible_partitioning
config:type="boolean">true</use_flexible_partitioning>
@@ -1210,7 +1213,7 @@
A more complete example with other options is shown below:
-```
+```xml
<partitioning>
<use_flexible_partitioning
config:type="boolean">true</use_flexible_partitioning>
@@ -1263,7 +1266,7 @@
using CDATA sections to avoid confusion with the XML syntax. The
following example shows how scripts can be embedded in the control file:
-```
+```xml
<module>
<name>info</name>
<arguments>false,true</arguments>
@@ -1287,7 +1290,7 @@
The structure is rather easy:
-```
+```xml
<texts>
<!-- Unique tag that identifies the text -->
<some_text_id>
@@ -1464,7 +1467,7 @@
its own proposals, workflows etc. The control file has a special
section, which defines changes to the existing workflow and proposals.
-```
+```xml
<?xml version="1.0"?>
<productDefines xmlns="http://www.suse.com/1.0/yast2ns";
xmlns:config="http://www.suse.com/1.0/configns";>
@@ -1613,7 +1616,7 @@
appropriate set of .mo-files must be present to have the texts related
to the control file translated.
-```
+```xml
<textdomain>OES</textdomain>
```
@@ -1623,7 +1626,7 @@
workflow for the standalone installation must have the mode and stage
set
-```
+```xml
<mode>installation</mode>
<stage>normal</stage>
```
@@ -1634,7 +1637,7 @@
name has to be specified, other options (enable\_skip, architecture) are
optional. The modes, stages, and architectures do not
-```
+```xml
<proposal>
<label>OES Installation Settings</label>
<mode>installation,demo,autoinstallation</mode>
@@ -1651,7 +1654,7 @@
Adding an item to a proposal is possible at the end only. If the
proposal has tabs, the items are added to a newly created tab.
-```
+```xml
<append_modules config:type="list">
<append_module>module_1</append_module>
<append_module>module_2</append_module>
@@ -1660,7 +1663,7 @@
### Removing an item from a proposal
-```
+```xml
<remove_modules config:type="list">
<remove_module>module_3</remove_module>
<remove_module>module_4</remove_module>
@@ -1673,7 +1676,7 @@
by one or more new clients. If you need M:N use remove and replace
together.
-```
+```xml
<replace_modules config:type="list">
<replace_module>
<replace>old_module</replace>
@@ -1690,7 +1693,7 @@
The workflow to update is identified the same way as other workflows.
The archs, modes, and installation don't need tobe alligned to the same
groups as in the base product workflows.
-```
+```xml
<workflow>
<defaults>
<archs>all</archs>
@@ -1705,7 +1708,7 @@
### Append steps to the end of installation sequence
-```
+```xml
<append_modules config:type="list">
<module>
<heading>yes</heading>
@@ -1724,7 +1727,7 @@
```
### Insert steps to installation sequence
-```
+```xml
<insert_modules config:type="list">
<insert_module>
<before>perform</before>
@@ -1740,7 +1743,7 @@
```
### Remove steps from installation sequence
-```
+```xml
<remove_modules config:type="list">
<remove_module>finish</remove_module>
[...]
@@ -1748,7 +1751,7 @@
```
### Replace steps in installation sequence
-```
+```xml
<replace_modules config:type="list">
<replace_module>
<replace>language</replace>
@@ -1775,7 +1778,7 @@
#### Before chroot
-```
+```xml
<inst_finish_stages config:type="list">
<before_chroot>
<label>Copy Theme</label>
@@ -1788,7 +1791,7 @@
```
#### Running in chroot
-```
+```xml
<inst_finish_stages config:type="list">
<chroot>
<label>Update Configuration</label>
@@ -1801,7 +1804,7 @@
```
#### Before unmounting the system
-```
+```xml
<inst_finish_stages config:type="list">
<before_umount>
<label>Disconnect Network Disks</label>
@@ -1821,7 +1824,7 @@
To replace a workflow, just create workflows as in base product control
file. The important is that the stage of the workflow is set to
-```
+```xml
<stage>continue</stage>
```
@@ -1842,7 +1845,7 @@
accessible via ProductFeatures module. No new option groups can be
defined. Options which are defined by the base product, but not by the
add-on product, are kept unchanged (base product's value is used).
-```
+```xml
<globals>
<additional_kernel_parameters></additional_kernel_parameters>
</globals>
@@ -1857,7 +1860,7 @@
At the end of the installation, a profile for AutoYaST can be generated.
The profile will be generated using modules from the base product and
modules specified in the add-on product control file.
-```
+```xml
<clone_modules config:type="list">
<clone_module>printer</clone_module>
[...]
@@ -1873,7 +1876,7 @@
installation workflow, selecting and installing packages is missing,
these steps need to be prepended to the workflow.
-```
+```xml
<?xml version="1.0"?>
<productDefines xmlns="http://www.suse.com/1.0/yast2ns";
xmlns:config="http://www.suse.com/1.0/configns";>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-installation-3.1.161/package/YaST2-Firstboot.service
new/yast2-installation-3.1.162/package/YaST2-Firstboot.service
--- old/yast2-installation-3.1.161/package/YaST2-Firstboot.service
2015-10-15 09:54:10.000000000 +0200
+++ new/yast2-installation-3.1.162/package/YaST2-Firstboot.service
2015-11-06 15:41:38.000000000 +0100
@@ -1,7 +1,7 @@
[Unit]
Description=YaST2 Firstboot
After=apparmor.service local-fs.target YaST2-Second-Stage.service
plymouth-start.service
[email protected] display-manager.service network.service
NetworkManager.service
[email protected] [email protected] display-manager.service
network.service NetworkManager.service
ConditionPathExists=/var/lib/YaST2/reconfig_system
[Service]
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-installation-3.1.161/package/YaST2-Second-Stage.service
new/yast2-installation-3.1.162/package/YaST2-Second-Stage.service
--- old/yast2-installation-3.1.161/package/YaST2-Second-Stage.service
2015-10-15 09:54:10.000000000 +0200
+++ new/yast2-installation-3.1.162/package/YaST2-Second-Stage.service
2015-11-06 15:41:38.000000000 +0100
@@ -3,7 +3,7 @@
# If xinetd is enabled, make sure it's already running so we can stop it during
# initialization of the VNC server
After=apparmor.service local-fs.target plymouth-start.service
[email protected] display-manager.service network.service
NetworkManager.service SuSEfirewall2_init.service SuSEfirewall2.service
[email protected] [email protected] display-manager.service
network.service NetworkManager.service SuSEfirewall2_init.service
SuSEfirewall2.service
ConditionPathExists=/var/lib/YaST2/runme_at_boot
[Service]
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-installation-3.1.161/package/yast2-installation.changes
new/yast2-installation-3.1.162/package/yast2-installation.changes
--- old/yast2-installation-3.1.161/package/yast2-installation.changes
2015-10-15 09:54:10.000000000 +0200
+++ new/yast2-installation-3.1.162/package/yast2-installation.changes
2015-11-06 15:41:38.000000000 +0100
@@ -1,4 +1,11 @@
-------------------------------------------------------------------
+Fri Nov 6 11:59:26 UTC 2015 - [email protected]
+
+- Ensure second stage and YaST-Firstboot don't get killed by
+ getty when running over serial console (bsc#935965)
+- 3.1.162
+
+-------------------------------------------------------------------
Fri Oct 9 13:32:36 UTC 2015 - [email protected]
- Language selection screen fixed to immediately apply the keyboard
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-installation-3.1.161/package/yast2-installation.spec
new/yast2-installation-3.1.162/package/yast2-installation.spec
--- old/yast2-installation-3.1.161/package/yast2-installation.spec
2015-10-15 09:54:10.000000000 +0200
+++ new/yast2-installation-3.1.162/package/yast2-installation.spec
2015-11-06 15:41:38.000000000 +0100
@@ -17,7 +17,7 @@
Name: yast2-installation
-Version: 3.1.161
+Version: 3.1.162
Release: 0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
