File _patchinfo of Package patchinfo.18782

Overview Repositories Revisions Requests Users Attributes Meta

File _patchinfo of Package patchinfo.18782

<patchinfo incident="18782">
  <issue tracker="bnc" id="1182211">[aarch64] JeOS images RaspberryPi and/or KVM may need shim package</issue>
  <issue tracker="bnc" id="1182264">KDE LiveCD 20210210 fails to boot (dracut-initqueue timeout errors)</issue>
  <issue tracker="bnc" id="1182963">[RPi] Resizing sdcard partition on first boot doesn't also resize the filesystem</issue>
  <issue tracker="bnc" id="1183059">RPi JeOS - Swap UUID incorrect</issue>
  <issue tracker="bnc" id="1178670">In a PXE (Kiwi) image, sysroot.mount ends after initrd-switch-root.service</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:

Upgrade from version 9.23.19 to  version 9.23.20
  
- Require `qemu-img` in any filesystem based image.
  Move the qemu-img requirement into the `kiwi-systemdeps-filesystems` 
  to ensure ISO, OEM and PXE images include it in the build service. 
  This is also required for images that are simple root-trees in a filesystem `(image=ext4)`.
- Add a requirement for `kiwi-systemdeps-iso-media` on disk images.
  Add a requirement for `kiwi-systemdeps-iso-media` in `kiwi-systemdeps-disk-images`. 
  This is to ensure that installing `kiwi-systemdeps-disk-images` is enough to build OEM 
  images including install media.
- Turn `fb-util-for-appx` requirement into a recommendation.
  Relax the requirement for `fb-util-for-appx` since the utiliy is not part of all 
  SUSE Linux Enterprise 15 Service Packs.
- Refactor grub2 installation. (bsc#1182211)
  Split the installation in two parts. Former `grub2.install` method was meant to run the 
  `grub2-install` tool, however, in addition it was also running the secure boot installation `shim-install`.
  The install method in `KIWI` is skipped for those architectures and firmware combinations for which 
  bios support doesn't exist. This was leading to skip the secure boot installation.
  The current approach strips the secure boot installation logic from the `grub2.install` method, 
  so skipping the install method does not automatically result in skipping the secure boot installation.
- Fix `lsblk` flags to get sorted output (bsc#1182264, bsc#1182963, bsc#1183059)
  Modify the `lsblk` command flags to get a sorted output according to the disk layout.
- Avoid using generators in `pre-mount` hooks (bsc#1178670)
  Delete the generator that was creating the `sysroot.mount` unit for ramdisk deployments. 
  Generators, specially the `sysroot.mount` is expected to be created on very early stages of the boot 
  procedure as this has impact on relevant targets such as `initrd-root-fs.target`, which does not depend on 
  `sysroot.mount` if the unit is not there.
  In ramdisk deployments some data is known on pre-mount stage as it is downloaded from the PXE server. 
  At this stage it is not safe to generate a `sysroot.mount` unit that depends on `initrd-root-fs.target` as
  the target is close to finalize or even finalized already and could potentially skip `sysroot.mount` exection.
  Instead include a mount hook which is only executed on ramdisk deployments that simply runs the mount 
  command to mount `/sysroot`.
  </description>
</patchinfo>

Places

File _patchinfo of Package patchinfo.18782

Places