Sync from SUSE:ALP:Source:Standard:1.0 python-kiwi revision b0eeed092504feb26a37dd6c820781f7
This commit is contained in:
parent
24a175d466
commit
c299efffff
2
PKGBUILD
2
PKGBUILD
@ -12,7 +12,7 @@ makedepends=(python-setuptools gcc shadow grep)
|
||||
provides=(kiwi-ng kiwi)
|
||||
source=("${pkgname}.tar.gz")
|
||||
changelog="${pkgname}.changes"
|
||||
md5sums=('6bbd27ea5eabf8e0bf5de250d51cfe2a')
|
||||
md5sums=('71e993802d05c9b5f0217a59859e4844')
|
||||
|
||||
|
||||
build() {
|
||||
|
@ -1,3 +1,21 @@
|
||||
-------------------------------------------------------------------
|
||||
Mon Mar 25 12:26:24 CET 2024 - Marcus Schäfer <marcus.schaefer@gmail.com>
|
||||
|
||||
- Live ISO Wait for udev events after repart
|
||||
|
||||
Make sure to wait for the event queue to become empty after
|
||||
the creation of the write partition. When kiwi calls the
|
||||
code to create the write partition this emits new udev events.
|
||||
It's important to wait for the event queue to become empty
|
||||
to avoid a potential regression on the use of the device nodes.
|
||||
In the processing of the events it can happen that a device
|
||||
gets removed and re-added. If we don't want for udev
|
||||
to process the entire queue it can happen that the
|
||||
wrong block device is used. This wrong selection is only
|
||||
possible because the way how hybrid ISOs are designed exposes
|
||||
both, the disk and the partition for the root device with
|
||||
the same label. This Fixes bsc#1213595
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Tue Mar 19 09:33:17 CET 2024 - Marcus Schäfer <marcus.schaefer@gmail.com>
|
||||
|
||||
|
BIN
python-kiwi.tar.gz
(Stored with Git LFS)
BIN
python-kiwi.tar.gz
(Stored with Git LFS)
Binary file not shown.
Loading…
x
Reference in New Issue
Block a user