- update the driver handling for the imageConfig data structure
  * take advantage of the private helper methods implemented for
    package handling
  * eliminates code duplication
  * simplifies implementation of driver handling methods
- update the unit tests to adjust for minor differences in messages
- resolve suse version checking to zero if the suse_version
  macro is not defined. This allows the package build going
  easily also in non-suse based distros
- fixed typo in setupFilesystem() which caused a fat16 filesystem
  even though a fat32 filesystem was requested.
- changed the efi boot partition type to fat16
- added ext2 modules to the bootx64.efi module
- added parted to openSUSE 12.2 JeOS template
- added support for a jump partition which is added before the
  actual boot partition. This is used for grub2 efi based disk
  images now. kiwi just put the created grub2 bootx64.efi module
  onto the fat16 based jump partition and let grub2 read all
  data from the second ext3 based boot partition. This allows
  standard linux filesystem based boot partitions and it has
  also turned out that this disk layout might be required for
  arm based images as well. But so far this system is connected
  to the efi setup only
- fixed logical volume name building in resizeLVMVolumes()
  the function only evaluates volume names at the primary
  level e.g /opt. As soon as you have a volume e.g /opt/bob
  it failed to resize
- fixed cleanup of temporary copy of sysconfig/proxy. If there
  is a fillup template for the file and the file hasn't changed
  as part of the build process the fillup template is restored
  instead of removing the file (bnc #777151)
- changed behavior of --fat-storage option. Instead of syslinux
  we now use grub2 to boot from the fat partition. It has turned
  out that grub2 is more stable and behaves better when using
  the image on a USB stick. The grub2 theme support also makes
  it easier to use custom branded boot graphics
- v5.04.26 released
- fixed broken postImage() filesystem check which prevented the
  creation of the system image .md5 file
- v5.04.27 released
- added sanity check for mount() method to fail
  if no source information is passed
- fixed setupInstallStick() if called in Studio mode. If this
  function is called with a disk device as reference it expects
  the target USB stick to be plugged in, in order to create the
  install image directly on that stick. For Studio this does
  not work because the target stick is never attached to the
  containment within this call happens. Thus this fix creates
  the install USB stick image in a loop device
- removed obsolete mount code from setupInstallStick()
- cleanup setupInstallStick(), the reference to this->{loop}
  might be undefined depending on the environment better use
  the contents of $haveDiskDevice
- cleanup global mount method to use the getPartDevice() function
  to search for partition devices
- fixed spec file, syslinux exists on ix86 and x86_64 only
- remove searchUSBStickDevice() function. When kiwi was called
  with a target disk device the assumption was made that the
  install media should also be created on a device directly.
  If the install media is a USB stick (installstick="true")
  kiwi searches for stick devices during the process and:

  a) exits with an error if it can't find one
  b) asks which one to use if it finds more than one

  This behavior is a pita for automatic build processes and
  it also fails if the stick media does not set the 'removable'
  state in its meta data correctly. Additionally the assumption
  that the install media is present as a device just because
  the image was created from an existing device also sucks

  This commit removes the search for stick devices and always
  creates the install media through a loop as a file which
  then needs to be dumped on the target device
Merge branch 'master' of http://github.com/openSUSE/kiwi