Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
This splits out the used_keys functionality from set_keyfile.
This is so that the keys used may be queried separately from
keyfile loading.
|
|
|
|
See #691376.
sbuild::chroot_block_device_base::set_device was called from
the chroot_block_device_base ctor, and called
sbuild::chroot_facet_mountable::set_mount_device for all chroot
types except lvm-snapshot. However, dynamic_cast<> fails during
construction, leading to the mount device being overwritten, and
--recover-session mounting the source LV rather than the snapshot
LV. This patch moves the call to set_mount_device to the session
clone operation in sbuild::chroot_facet_session_clonable, which
is where the equivalent operation is done for lvm-snapshot. This
is done prior to lvm-snapshot to ensure that the snapshot is not
overwritten here either.
|
|
Also adjust sbuild::chroot_block_device_base to match the docs.
|
|
This had exactly the same function as the chroot name, so merge
into a single property.
|
|
|
|
|
|
not available
Signed-off-by: Roger Leigh <rleigh@debian.org>
|
|
Before a chroot is fully initialised, it is possible for some
properties to be empty strings. Don't fail in this case.
|
|
Signed-off-by: Roger Leigh <rleigh@debian.org>
|
|
|
|
Split into two facets, chroot_facet_source_clonable (for chroots
providing clone_source functionality) and chroot_facet_source
(for the resulting clone). This separation means that a single
class doesn't need to cater for two essentially separate uses.
The ability to list the installed facets, and name each facet for
human consumption has been added.
|
|
This is the first step to separating all derived chroot functionality
such that it will not be derived from the sbuild::chroot class, but
instead be contained within the chroot.
|
|
|
|
|
|
In order to support union mounts on block devices, it can't
conflict with the chroot_source support for lvm_snapshot.
Therefore split into a base class, block_device_base, from
which block_device and lvm_snapshot derive. Each can then
implement chroot_source and/or chroot_union independently.
block_device now has an explicit protected copy constructor
for lvm_snapshot in order to allow its use as a source
chroot type.
This will prevent lvm_snapshot from gaining chroot_union
support due to being directly derived from chroot_block_device.
|