gfxboot is needed on the host for certain boot graphics
operations. It's used if the boot theme provides a gfxboot.cfg
In this case the tool is also required. The setup of the
boot themes is differently implemented in each of the
distributions we support. In addition on suse distributions
gfxboot is no longer in the core system. Given that we are
not able to find a common base on requirement of the package
we changed gfxboot from a required to a recommended package
and deleted the requirement on debian based distros
In the implementation of the ramdisk installer from
SUSE/ramdisk_deployment(4fdeee3faa) an error for the
standard case was introduced such that the lsblk call
was invalid. This lead to no devices being present
for the installation. This patch Fixes#877
For filesystem images the rsync call was missing a finale slash for
the source path causing the sync also the containing directory. With
this change the filesystem image does not include the rootfs in any
subdirectory.
Fixes#875
This commit adds the history section in contianerconfig. With it
'author', 'created_by' and 'comment' can be customized. In addition
'created' is always included with the image creation date time.
'created_by' entry is set to 'KIWI __version__' by default if nothing
is provided.
Fixes#852
By default none of the image formats were stored as compressed
file. The reason behind this was the assumption that some
formats automatically makes use of compression, which is true
but only in their processing and not in their data blocks at
creation time. Storage and handling of the image file itself
becomes cumbersome and therefore we change the default bundle
setup for image formats to be compressed. This means the image
as it gets packed by KIWI needs to be uncompressed before use.
The following image formats are affected by the change in a
call of the result bundler:
kiwi result bundle ...
* qcow2 (.qcow2.xz)
* vdi (.vdi.xz)
* vhd (.vhd.xz)
* vhdx (.vhdx.xz)
* vmdk (.vmdk.xz)
All other image formats already defined a custom bundling
setup including compression and are not affected by this change.
This Fixes#650
In a kiwi initrd the function baseStripFirmware can be
used to strip down the firmware to the actually used
kernel drivers in that initrd. The code to do this was
broken due to the changes in #64cb5b003140a. This
patch done by Ruediger Oertel <ro@suse.de> fixes the
method to work correctly again.
A LVM-enabled oem image spuriously did not resize its PV / LVs. Tracking
this down, I discovered that lsblk was sometimes racing with udev and
the disk was just not available during get_partition_node_name().
Call udev_pending() before all lsblk calls to avoid that.
(lsblk man page also advocates this to synchronize with udev)
The output from the sphinx build does not render css
and java script correctly on github pages, thus switch
back to travis-sphinx to generate that data
Apparently dictionary keys are not sorted equaly in py2 and py3. While
the code does not relay on command flags order the test command
validation does. This commit ensures the umoci command is the same for
both, py2 and py3, with all the flags in the same order.
In the past we used the travis-sphinx script to deploy
the documentation to gh-pages via the travis CI. However
with the change to the travis github App we need to
change this deployment into a real deployment stage
of the travis setup
