When the PC is online on the internet, an update is easily done via the console, I have done it already without issues. Prepare yourself by reading the available documentation:
https://files.devuan.org/devuan_daedalu … _notes.txt
https://www.devuan.org/os/documentation … o-daedalus
https://www.devuan.org/os/install

Most likely you haven't installed the meta packages linux-image-amd64 and linux-headers-amd64. They make sure kernel and headers are updated and consistent.

Also check if you have security enabled in your sources.list. Some read: https://www.devuan.org/os/packages

A patch is on its way through Debian repos ...

Your entry into the sources.list is wrong. You could use:

deb http://archive.devuan.org/merged ascii main

But I wouldn't fiddle and change the sources.list of my Daedalus for a single program.

Alternative: on the right hand top of the forum page is a link behind Packages to a search of the complete Devuan repo. Use that to search for leafpad. In the list of results then click on the ASCII package and you get another page with all available info about the latest version including a link to the file itself (look for Filename:). Click on the link and you get the deb downloaded. You can install it with dpkg -i or gdebi.

Normally deb.devuan.org should do the job alright. This is no real mirror but a round robin that should pick the next or fasted server available. If the picked out server has a problem then deb.devuan.org doesn't work.

But these issues should only be present temporarily.

In any case, I haven't seen any issue here in Germany with deb.devuan.org in the last days.

apt update/upgrade works for me on my main Daedalus system and on the two Excalibur VMs I tested yesterday.

This is not the latest version, thats Linux 6.1.0-17-amd64 x86_64. Havent't you got linux-image-amd64 installed?

Have a look at Synaptic.

Neofetch is 360k installed, no dependencies.
Screenfetch is 280k installed and requires additional dependencies.

Yes, Devuan kernels are 1:1 Debian kernels. No modification, look at the package names.

Got the same message on my two Testing/Excalibur VMs, not on my laptop running Chimaera and Daedalus. All three with usrmerge applied.

Looked at the linked FAQ: What I understand from my limited English Debian is broken, there are completely contradicting messages and no solution. The team does not seem to know how to attack this usrmerge process.

Have a look at this article: https://dev1galaxy.org/viewtopic.php?id=3192 - A description how it works.

# apt list fvwm*

fvwm-crystal/stable,stable 3.4.1+dfsg-3 all
fvwm-icons/stable,stable 20070101-7 all
fvwm1/stable 1.24r-57+b1 amd64
fvwm1/stable 1.24r-57 i386
fvwm3/stable 1.0.6a+ds-1 amd64
fvwm3/stable 1.0.6a+ds-1 i386
fvwm/stable 1:2.7.0-2 amd64
fvwm/stable 1:2.7.0-2 i386

3 different versions in the repo.

Then you were lucky for two years. Too bad. Try again tomorrow ...