In my mind, the term "immutable distro" is a marketing term that really means "I, 'the vendor', knows best; Just pay us and we'll fix it.".... a variant of "secure boot", I'd say.

Thanks. Good advice. I'll probably look at doing that eventually.
(I'm not using my bluetooth headset much at the moment)

It could possibly be helpful to the debian maintainer of bluez-alsa-util to lodge a bug regarding outdated codecs. Especially if there is a patch included. I guess the packaging project is on salsa.debian.org.

Yes try https://pkginfo.devuan.org/bluez-alsa-utils rather
(golinux' URL includes the AI bot distraction so it's not sharable)

Are we searching for a distinct meaning of a marketing term?

There is cryptsetup which according to its man page handles VeraCrypt encryption format.
It still will need two separate steps, like

cryptsetup open --type tcrypt /dev/sdb2 secrets
mount /dev/mapper/secrets /mnt/secrets

The first step creates the virtual partition (/dev/mapper/secrets) being the decryption of the real partition (/dev/sdb2), and the second step mounts that partition's filesystem on /mnt/secrets.

As per man page, if the VeraCrypt encryption has "personalized iteration count", you may need additional options to the open command.

Afaict tcplay does the same thing as cryptsetup, i.e. it creates that virtual partition for decrypted content access, and it doesn't mix in the filesystem mounting (which is an interpretation of the decrypted content).

Which kind of virtual machine is it?
Which time sync program do you use?

Ah, so you don't want help. Fair enough.

@zapper: I'm guessing you need to resize the "home" logical volume to use up all the volume group space, and you then need to enlarge the filesystem inside the logical volume to fill all available logical volume space.

Possibly it all can be done in a sinlge command, something like:

# lvresize -l 100%VG -r $LVM

where you replace $LVM with the identity fo the logical volume.

A backup might be handy.

The labels "excalibur", "excalibur-security", "excalibur-updates", etc are known as "codenames" and as such they identify "repositories" (not "distributions"). Each system (yours or mine) is set up with a package system that looks into one or more repositories for packages, which it (i.e. your system or my system) organises by package versions so as to get "the most recent version" of any package across those repositories.

A "distribution" is rather some particular collage of packages from some particular collective of repositories, that is formed and published so as to make a particular end user experience (and typically allowing for a smaller range of variations in experience).

HTH, Ralph.

Right. That's wrong for debootstrapping Devuan. You need to use Devuan's debootstrap for that.
Where did you get that "excalibur" script from?

Which deboostrap version are you using?

EDIT: the reason I'm asking is because "merge_usr" is defined in the "functions" that come with the debootstrap installation, since excalibur.

Perhaps you could show the tail end of the debootstrap.log file, for the failing case.