- force disk activation when Storage reports no disk was found
  (bnc#810823)
- 2.24.1
Merge pull request #33 from jsuchome/master

port from SP3
- show dialog for all available disk controlers (bnc#807026)
- 2.24.2
Merge pull request #34 from jsuchome/master

backport of SP3 fix
- call unicode_start/stop and initviocons only on consoles (bnc#800790)
- fixed check for missing initviocons
- fixed typos
Merge pull request #35 from aschnell/master

- call unicode_start/stop and initviocons only on consoles (bnc#800790)
- fixed check for missing initviocons
- fixed typos
- increased version
- startup scripts: if RC_LANG is not set, use en_US as default
  (bnc#815265)
- 2.24.4
Merge pull request #36 from jsuchome/master

 startup scripts: if RC_LANG is not set, use en_US as default
Calling rpmcopy_secondstage all now uses unique IDs

- This solves issue with some steps being disabled because their names
  were not unique (bnc#813072)
- SLED control file
Calling rpmcopy_secondstage all now uses unique IDs

- This solves issue with some steps being disabled because their names
  were not unique (bnc#813072)
- SLES control file
Calling rpmcopy_secondstage all now uses unique IDs

- This solves issue with some steps being disabled because their names
  were not unique (bnc#813072)
- openSUSE control file
Changes file entry (related to the latest three commits)
Merge pull request #42 from kobliha/master

Using unique IDs while calling rpmcopy_secondstage
Making rpmcopy_secondstage steps unique also for SLES-for-VMware

- bnc#813072
Backported changes done for openSUSE in Build Service

- These changes are already in openSUSE:Factory
- Made by openSUSE release manager
use WFM::ClientExists() call instead of checking *.ycp file

presence (works also with non-YCP clients and checks also e.g.
/y2update/clients path)
Merge pull request #46 from yast/use_clientexists

use WFM::ClientExists() call instead of checking *.ycp file
Let udev handle only changed devices in kernel_finish. bnc#774301

Added --action=change option to udevadm trigger. Without that
all devices are handled as NEW and it has some side effects.
At least one of them is that device emulated on top of lcs on
s390 is lost. In such case installation cannot continue to
second stage when installing over network.
Updated changelog

Conflicts:
	VERSION
	package/yast2-installation.changes