Just in case someone is interested, this link helped me out recently.  I had a Peppermint Devuan install and found it easier to just remove the dmo packages and revert to an all devuan install - including their multimedia packages.  I noticed no difference with no breakage.  Upgrades were easier too.

How to remove dmo packages - deb.multimedia
https://forums.linuxmint.com/viewtopic.php?t=227270

I ran into this problem yesterday while trying to do an upgrade of a ceres install.  This is my daily driver so it gets updated almost daily.  Therefore it was current to within a one to two day period.  When trying to do an apt upgrade I get this:

If I try to do an apt dist-upgrade, I get this:

There are no held packages.  The command "apt-mark showhold" produces no output, and there are no locked packages in synaptic as I do not use synaptic in ceres.

I know there was a lot of work done in the past to eliminate libsystemd0 from our system and I wonder if something new is trying to pull it back in?

Edit: added the held package information.

Thank you ffp!  This got pipewire working on a daedalus install that has been dist-upgraded from ascii > beowulf > chimaera > to daedalus!

I was wondering the same thing, but delgado posted before I did.

This WSL is good for a some people, but I only need windows to run my tax program once or twice a year, and a couple other programs during the year.  I prefer to use a windows virtual machine in a devuan host system than to use WSL in a windows machine.  But this was fun to play with.

From the link above,

or "<your-name>" for the script.  Make it executable.

Change this line in the script, or keep it as is:

- or -

Follow the instructions on adding the symlinks.  Then try to use the usual service commands to start/stop/status:
service <your-name> start/stop/status

Put your wireguard profile file in /etc/wireguard .  Give it your preferred name, maybe "wg0" or <your-name>.  The name you give it should be the same through the sysvinit script, and the profile name, I think.

Does openrc use sysvinit scripts?  I am not too familiar with openrc/runit/s6, yet, so if I am totally incorrect, please forgive me.

I used this info to create a sysvinit start script using my own wireguard profile config.  I hope it helps.

https://www.procustodibus.com/blog/2021 … it-script/

Maybe not yet.
But it has been added to the testing/ceres repo.

I apologize even before I ask this as I hope that I do not appear to be impatient, but will php packages for daedalus be built by tdrnetworks.com any time soon?  Just trying to plan an upgrade eventually.  I have used these packages without issue for over 3 years now, so I trust them.

I did run a test by upgrading to deb.sury.org's packages for daedalus and they appear to work fine, so this is a possibility.  If using sury.org's repo one will need to install "systemd-standalone-tmpfiles" beforehand. 

But I did get an awful feeling when I willfully installed something with "systemd" in its name.

I have read more than once in several places on the 'net that virtualbox requires systemd.  This is not correct.  This is the output on a ceres install:

To get back on topic, well, I don't speak german so I can't comment on the linked article in the original post.

I have been using both testing and ceres branches since around ascii.  I have installed on my hard drive the oldstable, stable, testing, and unstable versions - currently this is chimaera, daedalus, excalibur, and ceres.  As devuan gets upgraded to a new named version, I simply adjust the partitions, and grub.  Each is an installed snapshot of the stable - using refracta-tools.  I recycle the update/upgrade packages to keep these updated so as not to overuse the download mirrors.  Plus, to update each, I do it from within a chroot.  This works fine for me and I like it.

In my usage, I always use ceres as my daily driver and on the rare occasion that it does break**, I boot into the testing version and use it.  If it breaks, I go to stable.  This has worked fine for many years now and I have learned a lot.  I only recall one instance for a week or so where both the unstable and testing systems were unusable.  Fixing the unstable is usually done by doing nothing and waiting for a package fixed (dependency issue), and sometimes I have to temporarily pin (or mark) a package to a lower level.

In my experience, when using testing/unstable, I always update with "apt upgrade" and not "apt dist-upgrade".  This has saved me from breaking my systems about 15 to 20 times over the years.  Occasionally, in using testing/unstable, I do have to remove and reinstall a previous package, and I have to use the nvidia driver package to get suspend/hibernate to work as expected.  I do have to remember to reinstall all dkms packages when a new kernel is installed as they don't work initially, and have to be re-installed.  This has been happening with me for a few years now and I have not found a solution, yet.  (I haven't looked hard either, (-; )  Once in a while I will run an "apt dist-upgrade" to remove old and outdated packages, but I pay attention to what it wants to remove.  If in doubt, I leave it there and wait a while longer.  These are the only current issues I can recall. 

**A lot of problems with testing/unstable will sort itself out if you just wait a little while.  After all, these are not "stable" and problems are to be expected.  Don't use these developer tools if you don't want to learn.  It would be frustrating.

I don't think is it fixed in version 2.12~rc1-9 of grub-pc, which appeared in the repos yesterday:

After the upgrade produced this error, I did a complete removal of grub with:

And then installed with:

And it still produced the error above.
/etc/grub.d/25_bli is there and it contains:

#!/usr/bin/sh
set -e

# <comments removed>

cat << EOF
if [ "\$grub_platform" = "efi" ]; then
  insmod bli
fi
EOF

lines #290-305 of /usr/sbin/grub-mkconfig are:

for i in "${grub_mkconfig_dir}"/* ; do
  case "$i" in
    # emacsen backup files. FIXME: support other editors
    *~) ;;
    # emacsen autosave files. FIXME: support other editors
    */\#*\#) ;;
    *)
      if grub_file_is_not_garbage "$i" && test -x "$i" ; then
        echo
        echo "### BEGIN $i ###"
        "$i"
        echo "### END $i ###"
      fi
    ;;
  esac
done

Thanks sangam:

It sure did, and it installed without error after doing an "apt dist-upgrade"

This package will need to be edited after installing or updating, or rebuilt.

A small typo in this line hunter0one:

You can also downgrade to version 237-2, which is the daedalus version.  This will fix it.

Activate the daedalus stanza in the sources.list, and "apt update".

Comment out the daedalus stanza, or remove, from the sources.list file.

Then hold in apt with the command

The current broken version is 238-2, so the fixed version should have a higher number.
When it is fixed, remove hold with

Then update as usual.