That'll probably fix a lot, but not everything.
On my daedalus system, under /usr:  (find ! -group root -ls | grep -v ./local/)

   407952     16 -rwxr-sr-x   1 root     utmp        14416 Feb 26  2023 ./lib/x86_64-linux-gnu/utempter/utempter
   523692     52 -rwsr-xr--   1 root     messagebus    51272 Sep 24  2023 ./lib/dbus-1.0/dbus-daemon-launch-helper
   690224      4 drwxrwsr-t   2 root     lpadmin        4096 Dec 27  2015 ./share/ppd/custom
   393038      4 drwxrwsr-x  12 root     staff          4096 Oct 22  2023 ./local
   436499    636 -rws--x---   1 root     operator      649688 May 25  2022 ./bin/cdrdao
   411257     16 -rwxr-sr-x   3 root     mail           14608 Sep  3  2021 ./bin/mail-touchlock
   398561     32 -rwxr-sr-x   1 root     shadow         31184 Dec 14  2025 ./bin/expiry
   411257     16 -rwxr-sr-x   3 root     mail           14608 Sep  3  2021 ./bin/mail-lock
   396906     24 -rwxr-sr-x   1 root     mail           23040 Feb  4  2021 ./bin/dotlockfile
   401820    100 -rwsr-sr-x   1 root     mail          101664 Mar  1  2022 ./bin/procmail
   399266     44 -rwxr-sr-x   1 root     crontab        43648 Mar  2  2023 ./bin/crontab
   400977     60 -rwsr-sr-x   1 daemon   daemon         59768 Oct 15  2022 ./bin/at
   397902     80 -rwxr-sr-x   1 root     shadow         80376 Dec 14  2025 ./bin/chage
   402924    120 -rwxr-x---   1 root     operator      121840 Aug  6  2019 ./bin/growisofs
   410565    456 -rws--x---   1 root     operator      463776 Jun 24  2022 ./bin/wodim
   401442     20 -rwxr-sr-x   1 root     mail           18768 Mar  1  2022 ./bin/lockfile
   400077    476 -rwxr-sr-x   1 root     _ssh          485760 Apr  4  2026 ./bin/ssh-agent
   411257     16 -rwxr-sr-x   3 root     mail           14608 Sep  3  2021 ./bin/mail-unlock

Obviously, the list will vary depending on what's installed.  Stuff in /usr/src seems to be owned by $USER:$USER, and stuff in /usr/local is root:staff
And if you've got a usr-merged system (excalibur), there's probably going to be more...

[edit]
here's another list from an excalibur system, not a lot installed there

/usr$ find ! -group root -ls | grep -v ./local/
 66326757     44 -rwxr-sr-x   1 root     shadow      43256 Jun 29  2025 ./sbin/unix_chkpwd
 66331837     24 -r-xr-sr-x   1 root     postdrop    22840 Aug 10 12:35 ./sbin/postqueue
 66331826     24 -r-xr-sr-x   1 root     postdrop    22888 Aug 10 12:35 ./sbin/postdrop
 66337980     60 -rwsr-sr-x   1 daemon   daemon      59768 May  4  2025 ./bin/at
 66324522     32 -rwxr-sr-x   1 root     shadow      31256 Apr 19  2025 ./bin/expiry
 66332196    412 -rwxr-sr-x   1 root     _ssh       420224 May  6 08:33 ./bin/ssh-agent
 66322953    112 -rwxr-sr-x   1 root     shadow     113848 Apr 19  2025 ./bin/chage
 66322893     52 -rwxr-sr-x   1 root     crontab     51936 Jun 13  2025 ./bin/crontab
 66322658     24 -rwxr-sr-x   1 root     mail        23104 Dec 31  2024 ./bin/dotlockfile

First, you'll want to get the vendor-id and product-id of your device.  the lsusb command should give this info:

lsusb
...
Bus 005 Device 024: ID 03f0:4205 HP, Inc ScanJet G3010

In this case, vendor id is 03f0 and product id is 4205.
To create a udev rule, see this post, replacing with your vendor-id and product-id.

[edit]
it appears that /usr/lib/udev/rules.d/99-libsane1.rules is supposed to take care of this, by running /bin/setfacl -m g:scanner:rw on the device file.  For some reason, that doesn't appear to be triggering here.  If run manually,

setfacl -m g:scanner:rw /dev/bus/usb/005/024

then the scanner is accessible to the users in the scanner group.

You can try the (exprimental) netinstall iso at https://files.devuan.org/user/tempforever/, it has a different booting mechanism

To elaborate on Ralph's answer, that value parameter is in seconds.  So to get your desired 1-week setting, the url to bookmark would be https://dev1galaxy.org/search.php?actio … lue=604800

I believe that this can be handled via dpkg-divert?

my /usr/local/{bin,sbin} are owned by group staff, and group has write permission.

You did nothing wrong.  Evidently, task-lxqt-desktop has moved some of its (former) Depends packages to Recommends now.  I hope this was not intentional.  I can manually change it in the installer iso, if it comes to that.  For now, you should be able to apt install lxqt to get what you're missing.

[edit]
Evidently, this was done intentionally

Looking at that commit, it has affected much more than just lxqt.

Please, when you have an opportunity, test the new devuan_freia_7.0-202609031921_amd64_netinstall.iso - it should be on the mirrors by now.  And if you don't mind, report back whether that fixes the issue.

I don't know, haven't taken a poll or anything.  So far it's just a test on the netinstall.  Have you had any issues with it?

The reason for the change: https://www.rsyslog.com/clarifying-ai-f … r-rsyslog/
Of course, you're free to remove syslog-ng and replace it with rsyslog after the installation is complete.  And I may change the default back later, if that's what most users want.

That's odd. Is your nameserver accessible?  What's in /etc/resolv.conf?

I would also point out, according to what you wrote,

If you don't use those options (--write-link, --write-url-link, or --write-desktop-link), this particular issue won't affect you.  If you do use them, and don't want to check the output files, then by all means, update to a newer version (which is probably necessary anyway for it to work with youtube)

OK, your S21ventoy-loop file looks good.

What does this return?

losetup -a

If it returns nothing, try this

sh /lib/debian-installer-startup.d/S21ventoy-loop ; losetup -a

If there's this line: /dev/loop0: 0 /mnt/devuan_excalibur_6.1.1_amd64_netinstall.iso - then try this:

mkdir -p /cdrom ; mount -t iso9660 /dev/loop0 /cdrom

If it mounts correctly, then see if installation will continue.
If there are any errors/info displayed, please report back.