File _patchinfo of Package patchinfo.17297

<patchinfo incident="17297">
  <issue tracker="bnc" id="1176129">SLE 12 and 15 containers have /dev 0700 permissions</issue>
  <issue tracker="bnc" id="1176977">Derived images built with kiwi have dangling symlink in /usr/lib/sysimage/rpm</issue>
  <issue tracker="bnc" id="1176134">[Build 20.3] JeOS images 15sp3 do not boot in uefi mode</issue>
  <issue tracker="bnc" id="1175729">Secure boot could not be determined when booting JeOS images from default/fallback EFI</issue>
  <issue tracker="bnc" id="1170863">kiwi build-tests/s390/suse/test-image-vmx/appliance.kiwi does produce a bootable qcow2 image</issue>
  <packager>dcassany</packager>
  <rating>moderate</rating>
  <category>recommended</category>
  <summary>Recommended update for python-kiwi</summary>
  <description>This update for python-kiwi fixes the following issues:

Update from version 9.21.7 to version 9.21.23
    
- Do not exclude filesystem folders in OCI images. (bsc#1176129)
  
  This commit does not exclude filesystem folders during the rsync call
  in OCI images. It has been noted that including an empty /dev folder does
  not hurt and it can eventually help to work around some limitations of
  container related tools such as buildah.
    
- Fix/Refactor s390 support (bsc#1170863, bsc#1176977, bsc#1170863,bsc#1175729, bsc#1176134)

  - On s390 the boot process is based on zipl which boots into an
  initrd from which a userspace grub process is started to support
  the grub capabilities. The implementation of this concept is
  provided via the grub2-s390x-emu package. Once installed the
  setup of the bootloader is done via the grub2-mkconfig and
  grub2-install commands and therefore from a caller perspective
  the same as with any other grub2 setup process. For kiwi this
  means no extra zipl bootloader target code is needed. Therefore
  this commit deletes the zipl setup from kiwi and puts on the standard grub2 process. 
    
  - To support different targettypes the grub2-s390x-emu provided
  zipl template must be adapted. Parts of the former zipl bootloader
  setup therefore now applies to an update of the zipl2grub
  template file
    
  - Support for CDL/LDL DASD targets has been disabled in the schema
  When testing 4k devices and a respective zipl2grub template
  setup for CDL/LDL targettype it has turned out that grub2-install
  is not able to run on such a device. My assumption is that
  the device code in grub2-install does not work for 4k devices
  with an fdasd created partition table. As this needs further
  investigations and most probably adaptions on the grub toolchain
  for s390, we disabled the setup of these modes for now.
  emulated DASD (FBA) and SCSI targets stays supported.
    
  - Fix compat link for rpmdb location
  Fix the symlink creation for `/var/lib/rpm`. More specific
  or derived container images in which the base root tree already
  included the `/var/lib/rpm` the link, the `ln` command was creating a
  symlink inside the `/var/lib/rpm` folder given that it was following
  the already existing symlink. Adding the `--no-target-directory` force
  `ln` command to treat `/var/lib/rpm` path as the fully qualified symlink name.
        
  - Fixed s390/sle15 Virtual disk integration test
  The integration test used FBA mode as target. As the target
  is expected to be KVM this is the wrong setting. SCSI should
  be used instead.
    
  - Support dynamic linux/linuxefi in any case
  Instead of restricting the dynamic linux vs. linuxefi setup
  to a specific grub version, support this setup for any version
  of grub. 
</description>
</patchinfo>