Devuan Excalibur missing incus-base and incus-client

I am trying to install incus on Devuan Excalibur (based on Trixie Debian 13) however the apt install incus installation fails as neither incus-base or incus-client packages can be found to download, although 318 other dependencies were downloaded.

Any suggestions (other than building from source!) how to workaround?

Hmm, a quick glance indicates Devuan excalibur has merged the latest Incus packaging from Debian unstable. I don’t run any Devuan systems, but the output of apt install would be useful to see how/why it’s failing.

Use the packages from the Zabbly repo?

Ah yes, I found them here GitHub - zabbly/incus: Incus package repository

I will try the Zabbly Debian 13 package to see if that solves the problem.

Many thanks for the tip.

I doubt they will work, since Devuan doesn’t support systemd; the Zabbly packages only have systemd services, IIRC.

Hmm … yes that might be a problem unless there is an easy way to convert Systemd configs into configs for SysVinit that I am running.

Will see how it goes.

I wondered about that; I don’t know if Devuan has anything in the way of shims to make things to work with systemd configs.

If not, I guess you could take the Zabbly packages, and copy in the init scripts from the Devuan packages; you might be able to cobble something together. I don’t think building from source would help - you’ll still have the same problem with init scripts.

Otherwise, your problems are probably best dealt with upstream with Devuan - or use a more conventional base distro (in a VM if necessary).

An update.

After editing the Zabbly stable repository to ‘Suites: trixie’ I was able to install incus on Devuan Excalibur, however it threw the warning during installation that “systemd wasn’t found on this system” and “As a result, the incus units have not been enabled”

In checking on another system that is running Ubuntu it became clear that Incus uses a potpourri of systemd services that cannot all easily be identified and re-created in SysVinit format.

So I will follow up with the Devuan team to see what can be done to fix the problem from the Devuan side.