- Make sure _build_main_system is in loop context

- Drop py3.9 from workflow
  Does not support union type annotations

• Files Changed
• Browse Source

- Cast to type and prevent Any

- Apply different cherry-pick strategy
  cherry picking merge commits is not easily possible. Thus get
  the list of commits and check if it can be applied in a series

- Fixed custom ISO boot template
  The archlinux integration test used a custom iso boot
  template which still contained the terminal_setup variable.
  This commit fixed the template to use the new terminal_input
  and terminal_output variables

- Move FileSystem to context manager
  Change the FileSystem class to be a context manager. All code using
  FileSystem was updated to the following with statement:
  with FileSystem.new(...) as filesystem:
  filesystem.some_member()
  This is related to Issue #2412

• Files Changed
• Browse Source

- Delete clicfs from documentation API

- Update unit test data to schema v8.0

- Update major schema version from 7.6 -> 8.0
  With the switch to schema v8.x we allow for non compatible
  changes in regards to the v7.x stream. Thus this commit also
  deletes the support for clicfs from the schema

- Drop clicfs support
  clicfs was a fuse userspace implementation of an overlay
  filesystem. Since overlayfs became the default overlay filesystem
  there is no reason for kiwi to keep the clicfs support

- Use obsrepositories for the CentOS 9 image
  We were relying on the repos being parsed from the kiwi description but this can
  cause problems and gives us less flexibility when it comes to fixing repository
  setup issues.
  This fixes https://github.com/OSInside/kiwi/issues/2335

- Bump version: 9.25.22 → 10.0.0

- Move workflow runs to main branch
  Make sure all github actions runs from main

- Add compliance action
  Check if the commits of a pull request can be cherry-picked to
  the master, which is the kiwi v9.x.x code stream.

- Move LoopDevice class to context manager

• Files Changed
• Browse Source

- Bump version: 9.25.21 → 9.25.22

- Fixed regression in GRUB_SERIAL_COMMAND setup
  The condition to write the serial line setup was broken.
  This commit fixes it. Related to Issue #2419

- Fixed grub terminal setup
  The grub terminal setup is divided into the setting for the output
  and the input console. For both settings different parameters exists.
  So far kiwi did not differentiate between the two parts of the
  console setup and that could lead to a wrong setting if only one
  value is provided in kiwi's console= attribute which lead to the
  grub setting, GRUB_TERMINAL=value. If value is set to e.g gfxterm
  grub takes this for both input and output and it's obviously
  wrong for the input. To make this less error prune the kiwi code
  changes with this commit to set GRUB_TERMINAL_INPUT and
  GRUB_TERMINAL_OUTPUT rather than GRUB_TERMINAL and also runs sanity
  checks on the provided values if they are applicable. The information
  for setting up the console in the schema stays untouched though.
  That's because it's used for all bootloaders and also because grub
  supports multiple values for the console in/out setting in one
  GRUB_TERMINAL variable even though kiwi does no longer use it.
  To make this clear for the users also the documentation for the
  console attribute setup has been updated. If we want to wish two
  distinct attributes for input and output console settings a schema
  change and also differentiation between bootloaders is needed and
  that I only see for the kiwi-10 branch if at all. This Fixes #2419

• Files Changed
• Browse Source

- Fix tox.ini
  python 3.12 unit target did not specify a 3.12 interpreter

- Fix overwrite of kiwi_oemunattended
  In case rd.kiwi.oem.installdevice is set, there is an overwrite
  of the kiwi_oemunattended setting. However the variable was set
  in local scope of a function and therefore the change was not
  effective in other methods which also evaluates this variable.
  This commit fixes it such that the overwrite happens in the early
  initialize method which provides the environment for all code
  running in the dracut module. This is related to jira#PED-7180

- Ensure setfiles is detected inside the image-root
  We do not actually use setfiles from the host, we use it from the
  image root we create for the image build. Thus, we should look in
  the image root instead of on the host system.
  This prevents us from incorrectly detecting that setfiles is not
  available for setting SELinux contexts.
  Fixes: https://github.com/OSInside/kiwi/issues/2414
  Fixes: 2a22901ddd11ae23b6724b5e1aaa4261f219ccb6

- Use xdist on the CI to speed up the test runs

- Add unit test job using python 3.12

- Only run the job for this python environment

- [ci] Switch runner to ubuntu-latest

- Add missing raw string identifier infront of regexes

• Files Changed
• Browse Source

- Bump version: 9.25.20 → 9.25.21

- Cleanup tox targets
  Align tox targets with github workflows and fix targets
  not associated with a specific python version to use
  the python3 version installed on the host

- Bump version: 9.25.19 → 9.25.20

- Fixed unit tests for parallel invokation

- Make sure selinux policy is effectively applied
  setup_selinux_file_contexts is now called after the config.sh
  script. This makes sure that eventual policy related changes
  done in the optional config.sh are covered by a late setfiles
  call. In addition setup_selinux_file_contexts is called again
  at the end of any chroot based script hook. So we assume that
  any optional script target can change the system in a way that
  a new setfiles call might be required. It can happen that
  setfiles is called more often than required but as we cannot
  know what custom scripts does, it's better to call it more
  often compared to not often enough. This Fixes bsc#1210604

- Decrease image size for encrypted integration test
  Encrypted images do not compress well, therefore the size
  should be smaller such that we don't produce monsters

- Use ext4 for rawhide integration test

- Fixed typo in error message

• Files Changed
• Browse Source

- package: Drop unused xorriso dep on dracut-kiwi-live subpackage
  We do not actually use xorriso anywhere inside of the dracut module,
  nor do we pull in any utilities from the xorriso package into the
  generated initramfs anyway.
  Fixes: https://github.com/OSInside/kiwi/issues/2404

- Include either partx or partprobe to dracut
  The code in the 99kiwi-lib dracut module can either use
  partprobe or partx to do the job. We prefer partx over
  partprobe and error out if none of them could be found
  This Fixes #2400

• Files Changed
• Browse Source

- Update test-image-MicroOS
  Incorporate latest changes from upstream MicroOS and
  also add an encrypted profile build for testing

• Files Changed
• Browse Source

- Bump version: 9.25.18 → 9.25.19

- Fix typo in workflow overview doc section

• Files Changed
• Browse Source

- Add missing documentation for oem-unattended-id

- Allow install disk overwrite from cmdline
  Add rd.kiwi.oem.installdevice=DEVICE. Configures the disk device
  that should be used in an OEM installation. This overwrites any
  other oem device setting, e.g device filter or maxdisk and just
  continues the installation on the given device. However, the
  device must exist and must be a block special.
  This Fixes jira#PED-7180

- Update mailmap

• Files Changed
• Browse Source

- Replace the regex-based loader entry fix with string parsing (#2388)
  A user building RHEL images ran into issues with the initrd.
  It turns out that RHEL uses some patches that mean the
  initrd/linux files in RHEL are not installed to /boot, which trips
  up the original regex. The new fix doesn't rely on matching the
  path in boot, instead just finding the initrd/linux files and rewriting
  them in place.
  This change also adds the pre-and-post fix loader entries to the debug logs.
  Reference: https://bugzilla.suse.com/1208701
  Fixes suse bsc#1208701

- Fix mbrid setup for read-only systems
  On filesystems without a UUID (e.g squashfs) the fallback boot id
  setup should apply if neither UUID nor MBR ID is present. This
  is a followup fix for Issue #2391

- Fixed test-image-disk-legacy test description
  The configured embedded ESP image size is too big, max 30MB
  are possible as El Torito boot load size

• Files Changed
• Browse Source

- Don't make toml a requirement

• Files Changed
• Browse Source

- Fixed grub mbrid file search
  To identify the root device for ISO images (live and install media)
  that boots via grub2, kiwi uses a grub2 --file search. The searched
  file was named /boot/mbrid, however this is not a unique name and
  could be found on other devices of the system as well. To connect
  the search to the correct media this commit changes the search to
  an ID based method which is unique to the image build process.
  This Fixes #2389

- Don't use kernel-install
  kernel-install does a lot more then making the kernel available
  to the ESP. It calls dracut, it creates loader entries and all
  that is unexpected and also breaks the boot because the way
  dracut is called in the image build case where host != target
  leads to broken results. This commit refactors the systemd-boot
  support in kiwi to prevent the use of kernel-install

- Add check_efi_fat_image_has_correct_size
  Add runtime check for to check that the efifatimagesize
  does not exceed the max El Torito load size

- Add support for ISO boot via systemd-boot
  Create proper EFI FAT image via bootctl to be used as
  alt loader in xorriso. This allows to boot the ISO
  via EFI e.g kvm -bios /usr/share/qemu/ovmf-x86_64.bin -cdrom file.iso
  Please note, hybrid boot is done via grub's hybrid MBR and
  as systemd-boot does not provide one, hybrid boot is out
  of scope yet. This Fixes #2281

- Support TOML markup

• Files Changed
• Browse Source

- Bump version: 9.25.17 → 9.25.18

- Add partx to module-setup of kiwi-lib too

- Change partprobe fallback to partx
  Informing the kernel about a new partition geometry can be done in a
  busy state and is also effective for new devices and new mounts based
  on the new geometry. busy state mounts of course will not see it until
  swap of the busy state but a complete refuse of operation like it
  happens with blockdev is imho not required. Just as partprobe, partx
  is less restrictive on the busy state. That's why this commit changes
  the partprobe fallback to use partx instead of blockdev

- Create live persistent storage without busy state
  With the former logic the live ISO was already mounted when an
  eventual persistent storage partition was created. This leads
  to an issue on re-reading the partition table, not for all but
  several tools. This commit changes the order of tasks such that
  the setup of the persistent write storage is performed prior
  mounting the live ISO. In addition to this change an alternative
  method using blockdev to re-read the partition was added in case
  partprobe is not present. This also allows to get rid of the
  parted dependency which provides partprobe

• Files Changed
• Browse Source

- Bump version: 9.25.16 → 9.25.17

• Files Changed
• Browse Source

- Fixed argument processing of config.bootoptions
  Instead of adding an extra space to make the subsequent reading
  to work, use an awk script that does it without nasty workarounds

- Allow test-image-disk-ramdisk to be build locally

- Bump version: 9.25.15 → 9.25.16

- Fixed doc search field
  The search in the documentation is broken with the rtd
  schema and latest sphinx. Stick with sphinx 5.0.0 for the
  moment which fixes the issue

• Files Changed
• Browse Source

- Bump version: 9.25.14 → 9.25.15

- Make codacy happy

- Support release version in signkey URLs
  Using one of the $releasever/${releasever} variable placeholders
  in an URL as part of a <signing key="..."/> element did not replace
  the placeholder with the value of the <release-version> element.
  This commit fixes this and also makes sure that the result list
  for downloading signing keys is unique. This Fixes #2381

- Bump version: 9.25.13 → 9.25.14

- Update pypi release to trusted workflow

- Added unit test for testing grub prefix
  Cover the condition if an extra boot partition is used

- Fix documentation for btrfs_set_default_volume
  The behavior documentation regarding the fstab entry when
  using the btrfs_set_default_volume attribute was wrong.
  This commit fixes the docs to match the code. Related
  to Issue #2366

- use / prefix when boot partition is used

• Files Changed
• Browse Source

- Fix typo in 'image results' doc section

- Fixed root entry in fstab for btrfs layout
  A root (/) entry in fstab for btrfs is only required if no
  default volume is configured. This commit adapts the code
  path which adds an fstab entry for (/) to be effective only
  if btrfs_set_default_volume is set to false.
  Additionally, the documentation around btrfs_set_default_volume
  was clarified to describe the behavior the switch triggers.
  This Fixes #2366

- Remove community repository from Arch images
  Community repository is no longer needed for the test image. OBS does
  not pull any package from this repository and in Arch linux there is not
  the concept of empty repositories, so the build fails in an OBS context
  if this repository is included within the build stack.
  Signed-off-by: David Cassany <dcassany@suse.com>

- use os.path.join to create path
  os.path.join to create the path for the early_boot.write functions
  this will prevent paths from containing double slashes //

- PKGBUILD: Drop unused Python dependencies
  We haven't used some of these dependencies in years...

- add info on none console type

- allow value of GRUB_TERMINAL to be empty
  allow value of GRUB_TERMINAL to be empty. When setting grub_console="none"
  this now leads to an empty setting of GRUB_TERMINAL in the /etc/default/grub

• Files Changed
• Browse Source

- Bump version: 9.25.12 → 9.25.13
- Make verity metadata always readonly
  If a partition is verity protected, it can never be writable,
  since verity is by-definition read-only.


- Add kiwi_live_volid variable to profile
  As part of the profile environment only the kiwi_install_volid
  variable existed with the default value 'INSTALL'. This information
  is correct when building an oem image with installiso set to
  true. The resulting .install.iso image has the configured volid
  or the mentioned default 'INSTALL'. However, when building a live
  ISO image the default volid value is set to 'CDROM' but the profile
  environment contains kiwi_install_volid which is misleading and
  in case no volid is provided in the configuration file, the
  default value would also be a wrong information. This commit cleans
  up the mess and provides kiwi_install_volid for install ISO media
  and kiwi_live_volid for Live ISO media with their respective
  default values

• Files Changed
• Browse Source

- Fixed mounting of subvolumes for data sync
  The subvolumes must be mounted below the root of the
  filesystem tree such that the sync mechanism correctly
  shuffles the data to the correct volumes.
  This Fixes #2356

- Require DNF 5 in Fedora >= 41, not Fedora > 38
  The switch to DNF 5 has been postponed to (likely) Fedora 41.

- Add some hints about KIWI extensions and dependencies for SLE (#2348)
  SUSE Linux Enterprise Server (SLES) has KIWI as a package.
  However, some KIWI plugins and their dependencies can
  be unavailable.
  This commit introduces a new section which deals with this
  aspect.
  Fixes bsc#1209302

- Package lockdev no longer exists on TW
  Update TW based integration tests and delete the install
  of the lockdev package

- Update GitHub Actions "actions/*" part
  Update to the latest versions:
  * actions/checkout@v3
  * action/setup-python@v4
  * action/cache@v3

• Files Changed
• Browse Source