Calamares and I had disagreements about my partitioning scheme.
Last time I tried it, it needed around 125mb of software to work. That was a few years ago.

I've never had to load any extra modules on an expert install. I see that screen and just OK it without selecting anything, and I always have the full selection of filesystem types. If just looking at that screen is enough, then I guess the instructions would be "Don't skip any sections or you'll be missing stuff."

Check the sha256sum on the iso to make sure it didn't get corrupted on download.

Update: The item is called "Load installer components from installation media" and it does load stuff you need even if you don't check any of the boxes. So I guess the advice would be "Load installer components if you want to install the system." And I think I might feel insulted if it said that.

Edit2: I just want to add that manual partitioning is available in both expert and regular install. I've noticed that some people think you have to choose expert to do manual partritioning. You don't.

When you found the link on your search results, did you notice the color showed that you've been here before?

1. I can't reproduce your problem. Both refractasnapshot and refractainstaller start from the menu or from root terminal. If you start it from a live session, you don't need to enter a password.

2. The first screen on both programs has a Help button. The first sentence of the second paragraph of the refractasnapshot help says to read the config file. In the config file is a setting for where the newly created file is put. There's also an option in the menu to edit the config file or the excludes list.

In case you missed all of those, there's a summary screen that tells you where to find the finished snapshot. (in /home/snapshot or wherever you set it if you edited the config file)

When you quote a post, you should use quote tags or at least use quotation marks and a citation so that readers can distinguish my words from yours.

Cool, it worked! (on excalibur) I had to look inside the DEBBUILD file to see what the dependencies were so I could install them first as root. My user is not in the sudo group. I couldn't find an option for easydeb to print the deps list. Did I miss that, or it doesn't exist?

Also, I found an old version of hot-babe from medibuntu on my hard drive. I installed that on chimaera and there are a couple of differences. The buntu version has a nudity warning in a debconf dialog so you can cancel the install if you think you might be offended; that's missing in the DUR build. And buntu puts it in the Accessories menu instead of the Games menu. Other than that, they seem to be the same. I might need to compile a kernel to get a more thorough test.

I don't know why a link to a git repo got nuked. I looked at it, but I couldn't figure out what to do with it. Are there instructions somewhere?

Neither can I.

Are you just complaining or are you looking for a solution?

How do you know that deps are missing and what do you mean by "missing"? To me, it looks like the dependencies are the same for gparted in ceres and excalibur.

Second question for you: Which packages do you think are missing?

Suggestion:  Separate repos for each user's contributions, and name the repo something like DUR_fsmithred/ and if I want someone else to have upload privs to my DUR, I can just add them in my settings. Explore repos with search string "DUR" and they will all be listed (by "DUR_username" which may not be helpful) or search by project name, and all projects by that name will be listed (DUR* or otherwise).

Runit will use sysvinit scripts if there's no runscript for the service. Not all services have runscripts because not all maintainers of service packages are interested in runit. The runit-services package has additional scripts to the ones that come with runit-init.

Bug reports go to bugs.devuan.org or bugs.debian.org depending on if it's a forked package or not. The runit packages are from debian.

Here's a readme that might have some relevant information:
https://salsa.debian.org/runit-team/run … ian/README

I'm running ceres in qemu with openbox and no display manager. I use startx to get a graphical session. It's working normally with elogind 255.17-4 and friends. I notice you didn't list libelogind-compat. That also got upgraded with the others here. I also have seatd and libseat1 installed. If you're missing any of those, maybe adding them would fix it. That's a guess.

tempforever's gpg key is listed on this page:
https://www.devuan.org/os/team

And here if you search for tempforever:
https://keyring.devuan.org/

Which will show you that his key has been signed by another devuan dev:
https://keyring.devuan.org/pks/lookup?o … 4768BE620B

He's one of us, for sure. Unfortunately, his key didn't get added to the devuan-keyring package until a couple days ago. It's currently in ceres (version 2026.01.13)

runit-services has runscripts for lightdm, sddm, xdm and slim. I don't see gdm3 in the list. Also, someone else posted about a problem with gdm3 not working in excalibur.

Devuan has the exact same support for runit that Debian has. The runit maintainer sometimes posts on this forum. You might get a more informative answer.