- added kernel boot option 'disableProgressInfo=1' which allows
  to deactivate the progress information when the image download
  or install starts (bnc #771104)
- map openSUSE 12.3 to 12.2 configs for now
- reformated spec file by current spec_file_formater
- changed the way how zypper repos are used. move the repo data
  including cache data into the image root directory instead of
  storing this information in /var/cache/kiwi/zypper on the build
  host. On the build host we only store a shared package cache
  in /var/cache/kiwi/packages. This allows to keep the repo meta
  data per image and thus it can be re-used on operations like
  kiwi --upgrade which speed up the build as this is called as
  part of the the kiwi --create step too
- fixed spec file to write openSUSE instead of OpenSuSE (bnc #770825)
- follow up fix for the change of the zypper repo handling. The
  repo meta data will stay on the host again but is going to
  be re-used to prevent unneeded reloading of repo metadata
- avoid double slashes (//) in zypper repo files
- fixed copy of overlay files for boot images (initrd). make
  sure hidden files like e.g root/.ssh are handled correctly
- added support for ssh access into the boot image (initrd). Of
  course this requires an active network connection which is by
  design possible in the netboot and oemboot (in PXE boot mode)
  boot images. So the following is not supported for the isoboot
  and vmxboot boot images because they don't setup a network.
  The feature is based on the dropbear ssh server because it's
  so small to fit into an initrd. In order to have dropbear in
  the boot image you have to add the following to the system
  image configuration:

  <packages type="image">
       <package name="dropbear" bootinclude="true"/>
  </packages>

  and make sure one of your repos provides it. It's required to
  be in debug mode to be able to access the initrd. Thus you
  have to boot with 'kiwidebug=1' enabled. In order to access
  the initrd passwordless via ssh kiwi provides a key pair
  whereas the pubkey is stored in the authorized_keys file
  inside the oem- and netboot images for all supported OS
  versions:

  ssh -i /usr/share/kiwi/keys/id_dropbear root@<ip>

  For openSUSE >= 12.2 rsync is available in the netboot and
  oemboot boot images. For older versions it might be required
  to add tool packages bootincluded to be able to extract
  data from the boot image via ssh easily. In order to copy
  e.g the boot log file the following command can be used
  if rsync exists in the boot image:

  RSYNC_RSH='ssh -i /usr/share/kiwi/keys/id_dropbear -l root'
  rsync -avz <ip>:/var/log/boot.kiwi .
- DB: update documentation, add some information about the
  clic_udf feature as well as the support for ssh into the
  boot image. Also removed some obsolete data about aufs
- DB: rebuild documentation
- fixed check for disk in main::mount() function. searching for
  the string 'boot sector' also applies to the file output from
  a boot partition. The patch will call blkid on the given file
  or device and assumes a disk if no block id information exists
- added support for EFI boot with grub2 for the disk based
  image types oem and vmx (bnc #771327)
- netboot: fixed use of multicast for compressed images.
  With commit 7a7389f2e3f2b3d92b38c08455b0c6da15569269
  support for multicast based transfer of compressed
  images was added. Thus the checks which disable it
  are obsolete now (bnc #771898)
- show ssh login message only if an ip address was assigned
- added support for EFI boot with grub2 for install ISO media
  live iso media is still not EFI capable. In order to use
  EFI boot you have to bootinclude the grub2-efi package:

  <packages type="image">
      <package name="grub2-efi" bootinclude="true"/>
      ...
  <packages/>

  kiwi will check if there are efi modules inside the initrd and
  will then setup either a multiboot (iso) or plain gpt based
  image (bnc #771327)
- fixed mkisofs application ID setup when calling kiwi --installcd manually
- fixed grub2 chainloader setup
- fix validation test configuration files to meet new stricter
  consistency requirements
- New consistency check for package specification
  * At present the user can specify packages to be installed for
    a given image type even if this image type is not defined.
    While the packages get ignored and no harm is done, the
    superfluous specification is confusing and the XML definition
    is for all intent and purposes inconsistent.
- Unit tests for new consistency check
- add initial new-root directories according to the
  used package manager (bnc #743844)