Here we are:

Paketdateien:
 100 /var/lib/dpkg/status
     release a=now
 500 http://deb.devuan.org/merged beowulf-security/main amd64 Packages
     release v=3.0.0,o=Devuan,a=stable-security,n=beowulf-security,l=Devuan-Security,c=main,b=amd64
     origin deb.devuan.org
 500 http://deb.devuan.org/merged beowulf-updates/main amd64 Packages
     release v=3.0.0,o=Devuan,a=stable-updates,n=beowulf-updates,l=Devuan,c=main,b=amd64
     origin deb.devuan.org
 500 http://deb.devuan.org/merged beowulf/non-free amd64 Packages
     release v=3.0,o=Devuan,a=stable,n=beowulf,l=Devuan,c=non-free,b=amd64
     origin deb.devuan.org
 500 http://deb.devuan.org/merged beowulf/contrib amd64 Packages
     release v=3.0,o=Devuan,a=stable,n=beowulf,l=Devuan,c=contrib,b=amd64
     origin deb.devuan.org
 500 http://deb.devuan.org/merged beowulf/main amd64 Packages
     release v=3.0,o=Devuan,a=stable,n=beowulf,l=Devuan,c=main,b=amd64
     origin deb.devuan.org
Mit Pinning verwaltete Pakete:

My the "v=3.0" cause the issue?

Thanks to @golinux I have got the pre-beta-deepsea-theme-package and replaced my bluespace look with it. That meets exactly my taste in computer environment and fits perfect with the pre-beta Chimaera, which I have just running (btw: this refracta snapshot is very, very good and stable like a rock).

Grub

slim

fluxbox

Now my chimaera looks all of a piece.
I expected to find a small deepsea chimaera hidden between images and icons, but I was wrong. No magnificent beast at all.

Regards
Berni

@golinux: I am sure that you are not so old - compared with me.

SInce 2 weeks I'm working with a machine with a chimaera image (from refracta). The system works fine for and seems to be rock solid. Unfortunately it comes without the @golinux deepsea theme - it comes without any theme. As I like deepsea but dont want to copy the deepsea idea, I modified my chimaera with a, lets 's say bluespace theme. So I integrated a tga image to Grub and png images into slim and openbox.
Now my chimaera looks like this:

Grub:

Display Manager slim:

Openbox background:

Far away from a perfect corporate identity, but good enough for me.

Regards
Berni

Hey, great thread!! Thanks to @mcc for sharing the link with Devuan images for the Raspberry 4. c0rnelius made a fine job and the system runs properly and rock solid.
OK, it was a little bit tricky to set up a German keymap, but now it works as well as X. Now I have an alternative to raspian.
Again, many thanks to @C0rnelius and @mcc.

Regards
Berni

Great job, thanks again.
Maybe it's time to say Goodbye to my last Debian machine - only to see, how the new iso will work during installation.

Regards
Berni

Yesterday I installed firstly Exe Gnu/Linux - a very, very, very good looking system with its Trinity desktop. On another ssd than I installed the Refracta snapshot with chimaera. Minimalistic, nice & easy - exactly that what I prefer.
So I installed some important packages and ran into a problem: php-fpm is depending from systemd, which is not installable. PHP and php-fpm are a must for me due to my cms system Grav.

Any hint how I can solve this problem?

Regards
Berni

Sorry in advance for a silly question: Is there an installable ceres image available?
I could not find one yet

We (7 people) live in a shared house with several computers:

4 x Devuan (all Beowulf meanwhile)
1 x Debian Buster (only to have one systemd machine for comparision)
2 x OpenBSD 6.7
5 x NetBSD 9.0

After a litle bit trouble with Beowulf on a NUC now all Devuan machines are running rock solid. But, to be seriously, even Debian Buster runs very good. Looks like the Debian people do a good job regarding systemd.
No word about the BSD machines: they simply run perfect.

Regards
Berni

Changing to ATTR now brings again one error message less than before:

[    2.607622] udevd[132]: starting version 3.2.7
[    2.610145] udevd[133]: starting eudev-3.2.7
[    5.010561] udevd[461]: starting version 3.2.7
[    5.025778] udevd[461]: specified group 'kvm' unknown
[    5.028777] udevd[461]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14
[    5.028904] udevd[461]: invalid rule '/etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14'
[    5.073976] udevd[461]: starting eudev-3.2.7

Yes Sir. Here are the two files:

/etc/udev/rules.d/60-brother-brscan4-libsane-type1.rules
=============================================================
#
#   udev rules
#

ACTION!="add", GOTO="brother_mfp_end"
SUBSYSTEM=="usb", GOTO="brother_mfp_udev_1"
SUBSYSTEM!="usb_device", GOTO="brother_mfp_end"
LABEL="brother_mfp_udev_1"
SYSFS{idVendor}=="04f9", GOTO="brother_mfp_udev_2"
ATTRS{idVendor}=="04f9", GOTO="brother_mfp_udev_2"
GOTO="brother_mfp_end"
LABEL="brother_mfp_udev_2"
ATTRS{bInterfaceClass}!="0ff", GOTO="brother_mfp_end"
ATTRS{bInterfaceSubClass}!="0ff", GOTO="brother_mfp_end"
ATTRS{bInterfaceProtocol}!="0ff", GOTO="brother_mfp_end"
#MODE="0666"
#GROUP="scanner"
ENV{libsane_matched}="yes"
#SYMLINK+="scanner-%k"
LABEL="brother_mfp_end"
--------------------------------------------------------------
/etc/udev/rules.d/60-brother-libsane-type1-inst.rules
=========================================================
#
#   udev rules sample for Brother MFP
#         version 1.0.2-0
#
#   Copyright (C) 2012-2017 Brother. Industries, Ltd.
#
#   copy to /etc/udev/rules.d or /lib/udev/rules.d
#

ACTION!="add", GOTO="brother_mfp_end"
SUBSYSTEM=="usb", GOTO="brother_mfp_udev_1"
SUBSYSTEM!="usb_device", GOTO="brother_mfp_end"
LABEL="brother_mfp_udev_1"
SYSFS{idVendor}=="04f9", GOTO="brother_mfp_udev_2"
ATTRS{idVendor}=="04f9", GOTO="brother_mfp_udev_2"
GOTO="brother_mfp_end"
LABEL="brother_mfp_udev_2"
ATTRS{bInterfaceClass}!="0ff", GOTO="brother_mfp_end"
ATTRS{bInterfaceSubClass}!="0ff", GOTO="brother_mfp_end"
ATTRS{bInterfaceProtocol}!="0ff", GOTO="brother_mfp_end"
#MODE="0666"
#GROUP="scanner"
ENV{libsane_matched}="yes"
#SYMLINK+="scanner-%k"
LABEL="brother_mfp_end"

It must be mentioned that the Brother printers (5 x DCPJ525W) are all connected by Wifi, not via USB. The Beowulf machine serves the printers for that machines, which don't have drivers for the printers, e.g. computers with OpenBSD and NetBSD.
That works fine, independent from the error messages in the logfile.