vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit 51f9e9f2926fa67417ff50aa6140397d70df4cbe
Merge: 4065dec 6179124
Author: Luca Boccassi <bluca@debian.org>
Date: Mon Apr 22 20:44:06 2024 +0000
Merge branch 'new_ci' into 'master'
CI update
See merge request live-team/live-boot!51
commit 6179124273e4085b55d47ef7caef9c99de75d6ad
Author: MexIT <mexit.dev@gmail.com>
Date: Mon Apr 22 22:14:21 2024 +0200
CI update
commit 4065decb95c5eef2d6120bf7f35a98354492fb61
Merge: 4364b22 2cb049f
Author: Luca Boccassi <bluca@debian.org>
Date: Tue Apr 9 08:10:58 2024 +0000
Merge branch 'jschaer-master-patch-11800' into 'master'
Use "tmpfs" instead of "/dev/shm" as tmpfs device name
See merge request live-team/live-boot!46
commit 4364b2208a76e33ab1451c98ad4bb58beb5302b3
Merge: 51b57c3 1754c91
Author: Luca Boccassi <bluca@debian.org>
Date: Tue Apr 2 10:52:20 2024 +0000
Merge branch 'simplify-setup_loop' into 'master'
setup_loop: simplify and fix dependency on kernel defaults
See merge request live-team/live-boot!47
commit 1754c91483eac84922981c73c16fad929ef31d77
Author: Thore Sommer <debian@thson.de>
Date: Sat Feb 24 17:22:08 2024 +0100
setup_loop: simplify and fix dependency on kernel defaults
This removes some of the options that are the same for every caller.
We now use losetup -f to detect free loop devices. This has the advantage that
this also works when the kernel is compiled with:
CONFIG_BLK_DEV_LOOP_MIN_COUNT=0
commit 2cb049fb7502d11f344d14c567aab2592f19e77b
Author: Jan Schär <jan@jschaer.ch>
Date: Wed Feb 7 13:10:37 2024 +0000
Use "tmpfs" instead of "/dev/shm" as tmpfs device name
A tmpfs does not have a device, so usually, "tmpfs" is used as the device name.
When "/dev/shm" is used instead, this confuses systemd, which repeatedly prints this error in system logs:
Failed to open /dev/shm device, ignoring: Inappropriate ioctl for device
commit 51b57c3347366b05cb50b1bb411d6c6ecc998d04
Merge: 082e7a9 d2be333
Author: Luca Boccassi <bluca@debian.org>
Date: Sat Mar 18 16:45:32 2023 +0000
Merge branch 'luks-label' into 'master'
Introduce lukslabel option + fix for is_active_luks_mapping()
See merge request live-team/live-boot!44
commit d2be333ca62e98c5fdd0b4c618600e5483bac8b3
Author: Thore Sommer <debian@thson.de>
Date: Sat Mar 18 15:49:54 2023 +0200
Introduce lukslabel option
When "lukslabel" is set for persistence-encryption then live-boot only
tries to open containers that have the label "persistence" set. It
takes precedence over the "luks" option.
The behavior of the "luks" option is to prompt the user to open any LUKS
container. This was required for LUKS1 because it did not support labels,
but LUKS2 does. On systems were there are multiple encrypted containers
this is not ideal, because for users it is not clear why they should
decrypt their internal hard drive to boot a live system.
commit 769531e47b3649d6007c6b374723cfaf862a925b
Author: Thore Sommer <debian@thson.de>
Date: Sat Mar 18 15:46:25 2023 +0200
luks: is_active_luks_mapping() check explicitly for type
cryptsetup status also works on other device mapper devices that are not
LUKS or LUKS2.