- 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

- Bump version: 9.25.11 → 9.25.12

- Fix double grub entries in hybrid ISO images
  As consequence of using the "source" grub command instead
  of the "configfile" command to load the grub config we now
  see double loading of the same file on ISO media. The reason
  here is that kiwi ISO media is always hybrid which means it
  embeds an MBR into the ISO for which the "source" command now
  can read the same file through two different device paths.
  This does not happen with the "configfile" grub command.
  Thus this patch uses "configfile" if we produce an ISO image
  and "source" for all other image types. The commit also fixes
  the custom grub template used for ISO images in a way that
  we only set the "serial" command if there is a serial
  configuration provided along with the image description.

- Update x86/tumbleweed/test-image-systemd-boot
  systemd package has been splitted and provides
  systemd-boot in an extra package now

- Limit scope of grub _fix method
  Only apply _fix_grub_to_support_dynamic_efi_and_bios_boot for
  the x86_64 or ix86 architectures. This Fixes #2343

- remove trailing whitespace

- add GRUB_TIMEOUT_STYLE menu option
  revert trailing space removal

• Files Changed
• Browse Source

- Bump version: 9.25.10 → 9.25.11

• Files Changed
• Browse Source

- rpm spec: add missing requires of typing_extensions for python < 3.8

- rpm spec: bump copyright year

• Files Changed
• Browse Source

- Fixed linter errors
  Latest changes regarding type hints introduced linter errors.
  Also adapt the workflow run which is expected to detect them

- Bump version: 9.25.9 → 9.25.10

- Fixed python interpreter for Release target

- Bump version: 9.25.8 → 9.25.9

- Fixed workflow interpreter name
  Specifying py 3.10 has to be quoted

- Bump version: 9.25.7 → 9.25.8

- Fixed doc publishing
  The github action to do this was still based on py3.6
  but the latest changes on tox.ini requires a newer version
  of tox which doesn't exist for py3.6. Thus run the workflow
  on a newer python version

- Fix type hints of IsoToolXorrIso.init_iso_creation_parameters

- xorriso: handle case when isohdpfx.bin not found

- Fix type hints for the Pacman package manager

- Type hint the Path module

- Add better type hints to ContainerImageOCI and ContainerImageAppx

• Files Changed
• Browse Source

- Bump version: 9.25.6 → 9.25.7

- Fix linter check, whitespace after :

- Bump version: 9.25.5 → 9.25.6

- Use 'source' instead of 'configfile' in generated grub.cfg
  Details are outlined in issue #2320

• Files Changed
• Browse Source

- Pass rootflags if no default volume is set
  In case of btrfs and if btrfs_set_default_volume is explicitly
  switched off, we create the correct rootflags= kernel cmdline
  entry to tell the system about the root volume for booting

• Files Changed
• Browse Source

• Files Changed
• Browse Source

- Make sure btrfs root volume is used when needed
  With the possibility to switch off setting the default volume
  an issue at other parts in the kiwi code which mounted the
  btrfs based system were uncovered. Without any default volume
  set it's required to transport the root volume if different
  from / and pass the respective subvol= option to the mount.
  This commit fixes it at the places where kiwi trusted btrfs
  to have a correct default volume set

• Files Changed
• Browse Source

• Files Changed
• Browse Source

- update Fedora integration test
  The setting of a default volume is unwanted here

- add btrfs_set_default_volume attribute
  By default kiwi runs btrfs set-default on the volume that is
  considered the default volume according to the btrfs settings
  and defaults. btrfs_set_default_volume="false" allows
  to deactivate this action. Along with the change also the
  misleading name of the btrfs_create_toplevel_subvolume has
  been changed to root_is_subvolume

• Files Changed
• Browse Source

- Fixed check for extended attributes
  Only if libc reports errno 95 Operation not supported the method
  should return that extended attributes are not supported. Also
  add a debug information about the result of the call to get further
  information in the log file

- Import modules in OCI.new() explicitly
  Also, add a type hint to the return type of OCI.new() so that this can now be
  verified with mypy

- Fixed writing correct keyfile path to etc/crypttab
  The keyfile path was not correctly set in etc/crypttab which
  caused systemd not being able to read the keyfile, consequently
  asking for a passphrase. This commit fixes the writing of the
  crypttab and also fixes a python name clash with the "os"
  namespace.

• Files Changed
• Browse Source

- Fixed call of tox for xdist
  Passing arguments to modules called by tox has changed
  its syntax

- Take subvol mount option for root into account
  If the rootfs is btrfs based make sure the fstab entry for
  it takes the name of the root subvolume into account

- Fix fallback secure boot setup
  Don't copy the same file. This case happens when rebuilding
  an image using --allow-existing-root when the fallback setup
  has done its job already in the first run

- Update contributing chapter
  Fix and update the information how to contribute. Due to
  the latest changes in tox.ini some requirements regarding
  the tox and python versions came up. This commit updates
  the docs in this regard

- Added py3.11 tox target

- Cleanup condition for SECURE_BOOT=yes|no
  The statement serves the purpose for an if/else construction
  to become a better read. In addition delete the probably
  left-over print statement from the test

- Delete pyxattr from setup.py
  Followup on Issue #2330. Forgot to delete pyxattr requirement
  from setup.py

• Files Changed
• Browse Source