I believe those extra steps are only needed if you installed the first package made today, dated 2022.09.03, but the second package with date 2022.09.04 copies the new file for you.

Use option '--no-install-recommends' when you install the nvidia driver. This will prevent nvidia-persistenced from being installed and will eliminate the conflict. You won't miss the package when it's absent.

FDE usually refers to a setup that has /boot part of the encrypted volume. I recommend using one of the live isos. Refractainstaller knows how to do it. I can never remember all the steps and the right words, which is why I put it into a script.

Tell the installer you want to encrypt the root partition and don't select a separate boot. Added bonus - don't select a swap partition and let the installer put a small swap file on the encrypted root partition.

If you would rather diagnose and fix your current situation, you probably should show us what's in crypttab, fstab, a menuentry from grub.cfg and whatever you put into /etc/default/grub. And maybe fdisk -l, too.

I can't reproduce the error. I'm running daedalus, installed mariadb-server, then installed the version from ceres. So I upgraded from 1:10.6.8-1 to 1:10.6.9-1 without error. The service got stopped and started successfully.

I don't know what else to do. Maybe someone running ceres would get a different result.

Well, maybe dpkg --configure -a or dpkg-reconfigure mariadb-server-10.6

There's an old version of setnet in ascii and an older version in experimental. I'm pretty sure it's still in the minimal-live isos.

Make sure that policykit-1-gnome is installed.
See the section on Session Management and policykit backends in the beowulf release notes:
https://files.devuan.org/devuan_beowulf … _notes.txt

You might want to switch from consolekit to elogind.

If you have not already deleted that file, please wait. Below is the last changelog entry for the package that provided that file in the past. Latest version of the package should remove all the old files, including avoid-systemd. Please see if devuan-baseconf is installed. Let me know if it is.

If it's not, please install it and see if it removes avoid-systemd. Let me know that, too. Thanks.

If you already deleted it, then don't worry about it. It's no longer needed.

devuan-baseconf (0.6.4+devuan3.2) unstable; urgency=medium

  * Disable debian/install and debian/postinst.
  * Keep postrm to remove old files.
  * Keep package until nothing depends on it.

 -- fsmithred <fsmithred@gmail.com>  Sun, 05 Jan 2020 17:12:00 -0500

I've used refractainstaller to install to lvm. You have to use the cli version of the installer, not the gui. And you have to do a lot of the work manually, which you seem to be doing anyway. Maybe something in my Howto will help you.
https://dev1galaxy.org/viewtopic.php?id=2323

One important change. The howto says that your logical volume names should end in a digit. I fixed the installer so that is no longer true. You can use all alpha characters in your /dev/mapper/names.

Here's the themerc for openbox with the sapphire hexes. The one in the current package is unchanged from the original clearlooks-phenix theme. Replace the one in the sapphire theme package with this one. If you can figure out why it doesn't work,  please let us know.
https://paste.debian.net/1248088/

paste is good for 90 days.

First mistake was excusable - OP believed the screen that asked him to load firmware from external media. Almost everyone who sees this screen should ignore it and continue. The firmware usually gets installed automatically.

We should probably put a screenshot of that in the install guide. I'm not sure how to get that. The screen doesn't seem to come up when booting a VM. Maybe a camera shot of a hardware boot?

Welcome to Devuan. In Debian and Devuan, openrc uses the sysvinit scripts. That's about all I know about it. I think there are some on-screen instructions when you install it that talk about fixing links that might be relevant if you're replacing sysvinit but get done automatically if you choose openrc when installing the system. That's based on my memory of doing a couple of test installs in the past few years, worth what you paid for it.

Removed packages sometimes leave config files behind. Purging the package instead will remove the configs. To see all leftover configs and remove them:

aptitude search ~c
aptitude purge ~c
# or be specific
aptitude purge <package package...>

This might be of interest. (more package manager commands)
https://dev1galaxy.org/viewtopic.php?id=511

There are a few people here using openrc. You'll get better answers from them. Also, search the forum for past discussions on openrc. There have been a few.

Fixed version of refractainstaller is now in ceres and will migrate down to daedalus. I'll have to pull some strings to get it into chimaera-proposed-updates. If you're in a hurry to get it, you can download it from the repo.

refractainstaller-base
https://pkgmaster.devuan.org/devuan/poo … .2_all.deb

refractainstaller-gui
https://pkgmaster.devuan.org/devuan/poo … .2_all.deb

This one will correctly remove the diversion of anacron and rename it so it runs. It also contains a postinst script, so that when you upgrade the installer to this version, it will check your system for the leftover cruft from the diversion and correct it. It does not restart anacron, so logs won't rotate until after a reboot or a manual restart of anacron.