Yum cannot handle spaces between the key and the value.
This patch provides a method to tell ConfigParser to use
no spaces for the '=' delimiter and thus Fixes#357
* Updated the docs for system_create command
* Reverted dracut image initialization
* Updated yum comment about repo_gpgcheck option
* Updated variable name in disk builder
* Typo correction
This commit extends the behavior of --signing-key options in order
to import the provided key file into the boot image, in addition to
the regular image root tree.
Related to #342
editbootconfig and editbootinstall scripts needs to be
called from within the correct directory to allow access
to the written bootloader config files. For live images
the working directory was set to the wrong place. This
Fixes#353
the binaries groupadd and useradd used in the preinstall
scriptlet and provided by the shadow package needs a pre
requirement on shadow to make sure they exist when the
package gets installed. Fixes (bsc#1040256)
This commit fixes the validation of an existing root directory
for the command 'system build'. System build used to create the root
directory before performing the root existance check, thus the
check was always failing in any case. The root directory is created
inside the RootInit class within the 'create' method.
Fixes#349
This commit extends support for --siging-key to the Apt package
manager. However it has only been included for the chrooted
operations, as current implementation of the bootstrap procedure does
not provide signature check capabilities.
Related to #342
This commit extends the --signing-key options support to Yum and Dnf
package managers. In addition, signature check for repositories
had to be disabled for Yum and Dnf, as kiwi unrelated issues were
found while testing. Nevertheless, package signature checks are
fully functional.
Related to #342
This commit adds --signing-key option which sets a key file to import
into the package manager trusted keys database. This commit adds this
flag support only for zypper.
Fixes#342
The auto generated xml_parse.py uses the python warnings module
The unit tests uses the coverage module in py.test to create
a report. The latest py.test update now also creates a warnings
report which is unwanted because some of the unit tests
intentionally causes the creation of a warning as the expected
result but we don't want to see that in a py.test warnings
report. Therfore this patch switches off the creation of that
warnings report
The build command automatically used an existing root tree
from a former build attempt. However this could cause an
inconsistent image if the former build root was not based on
the same image type setup. Thus it is better to allow this
only if the --allow-existing-root option is specified along
with the build command call
The system prepare and build commands now provides the
option --clear-cache which deletes all cache data
associated with the repositories to build the image.
This Fixes#341
dracut was called in a way to create an uncompressed initrd archive
and kiwi later runs the xz compression on it. That way the default
compression parameters used by dracut get lost. Fixes#335
Adapt to style as used in the live iso chapter and add
references to low level topics regarding the setup of
the image to work in the public cloud. Related to #323
According to the gdisk documentation the gdisk maps the partitions IDs
to the MBR codes, but they are multiplied by 0x0100 in hexa. Meaning
0x8300 code is equivalent to 0x83 in MBR. This commit only considers
the first two characters of the sgdisk partition code output. With this
change the partition types are comparable, regardless of using MBR or
GPT.
This commit updates the boot code for oem images. In case
oem-partition-install flag was set, the boot code was not capable
to find an appropriate partition due to not attaching properly the
raw image as a loopback device. KIWI was calling 'losetup' command
with wrong arguments.
Fixes bnc#1039469
On Fedora and Mageia systems, the Yum package manager binary is named
'yum-deprecated', and 'yum' redirects to DNF. This is a problem for
being able to build images of Linux systems that use Yum as its package
manager, like RHEL/CentOS 7.
So, in order to ensure we use the right package manager, we check for
the 'yum-deprecated' binary and use it if it exists.
The low level topic references information from the base
topic. In this case the name of the previously built image.
I think we should provide information on each low level
topic which references information from a base topic.
This commit adds support for the rpm-check-signatures flag, which
sets the package manager to verify or not each package signature.
By default KIWI assumes no gpg checks are done.
