a6c09fd441
Extract the opening of LVM LV devices from `discover_lvm()` to `OSBuildDeviceManager` class as `open_lvm_lv()` method. `open_lvm_lv()` returns the path to the opened device in the devpath set in the underlying `DeviceManager`. The `org.osbuild.lvm2.lv` implementation takes the responsibility for creating and managing device nodes. This means that we don't need to be creating any device nodes directly in `osbuild-image-info`, especially in the current working directory. This was previously causing issues when inspecting two images with different LVM layout in a sequence. Signed-off-by: Tomáš Hozza <thozza@redhat.com> |
||
|---|---|---|
| .. | ||
| test | ||
| check-runners | ||
| check-snapshots | ||
| gen-stage-test-diff | ||
| inline-source.py | ||
| lorax-template-pkgs.py | ||
| osbuild | ||
| osbuild-depsolve-dnf | ||
| osbuild-dev | ||
| osbuild-image-info | ||
| osbuild-json-seq-progress-example-renderer | ||
| osbuild-mpp | ||
| set-env-variables.sh | ||
| solver-dnf.json | ||
| solver-dnf5.json | ||
| tree-diff | ||