That I do not know.  I have moved/archived/copied installs this way for several years now.  When using only devuan to copy or rsync an install this was never an issue, so I never used the "--numeric-ids" in my rsync command.  However, once I used a different operating system, this became an issue.  So I tried it on the recommendation in the Void forums, and it worked.  I used devuan to rsync a different linux OS, and "--numeric-ids" worked.

It is mentioned in the rsync man file:

man rsync

Allow me to ask, what operating system did you use to copy the source partition to the destination partition?  Devuan or another?

I do rsync copying pretty often and I recently had a situation where I had to add "--numeric-ids" to the rsync command.  This was because there was a different operating system involved in the mix, not just devuan.  In this instance I used devuan to host a Void virtual machine and I copied the virtual machine onto a locally mounted partition.  Essentially, I moved a VM onto a physical partition.   It worked fine after the fstab file was altered with the new UUID's, grub reinstalled, and the initramfs was rebuilt.

The actual command used that worked for me, from a VM to a locally mounted partition:

rsync -aHAXv --numeric-ids --exclude={"/dev/*","/proc/*","/sys/*","/run/*","/media/*","/mnt/*","/lost+found"} /* root@10.0.0.1:/media/User/Void/ --delete

Hope this helps.

For google-earth,
https://www.google.com/intl/en/earth/versions/

For librewolf,  don't know about Otter
https://librewolf.net/installation/debian/

As for the synaptic file for installed packages, a web search is your friend as I know it can be done.  But, I have never done it, yet.

For the video card issue, I suggest to download the video drivers needed before changing the cards, then install after the hardware change.  If after changing the hardware the X desktop does not come up, you may have to boot into recovery mode to install the drivers.  This is what I have done on several occasions.

pcalvert,

Were you able to do anything regarding alpine linux?  I looked at the packages involved and it is the "live-boot and live-config" packages that are missing and I don't know what could be used to replace their function - if this is possible.

The refracta-tools scripts have spoiled me.

The same thing just happened to me, on a ceres install.

My second profile only displays the url address of 0.0.0.1.

Oh well, I removed and then installed the version from excalibur and all is well, for now.  I did notice that a "Person 1" profile had been created that was deleted.  Don't know if I created it by clicking on a profile button in the browser or whether the bad update created it.

Yes, and the purpose of this command is to specify the information to add to the /etc/rc.local file

Which in my case lists these two devices which are my usb mouse and keyboard so that I can use either one to wake the system.

/sys/bus/usb/devices/1-5/product:USB Receiver
/sys/bus/usb/devices/1-6/product:USB Receiver

Note the "1-5" and "1-6" which is necessary information to add to the rc.local file.  I do not know why this command is not working for you, and I can't think of anything else to try.  If you were to manually change these while in a running state and save the changes, it may work until a reboot.  Upon rebooting, the changes would revert back to their original settings... hence is is necessary to have this in the rc.local file so that it gets set right when booting. 

There is also a way to do this by way of a bash script, but the rc.local way was easier, and both ways need the same command to be run to set the information correctly.  So this way would not help either.

DE is desktop environment - Xfce, KDE, Mate, etc.  The energy settings are usually located in the menu.  For example, Menu > Settings > Power Manager in Xfce.

This is what helped me -

https://askubuntu.com/questions/848698/ … usb-device

In short, you identify the usb devices in use and then add an entry to /etc/rc.local.

A better write-up as it pertains to devuan is located here:  https://dev1galaxy.org/viewtopic.php?id=5973

Hope this helps.

default-dbus-session-bus and dbus-session-bus are not found in the chimaera repositories.  However, they are listed as virtual packages by apt.  This would explain why the following command shows them as non-existent.  I would imagine that a standard dbus install would provide this need.

These virtual packages are provided by the package dbus.

At this point, this is all I can think of for you to check.  If your /etc/apt/sources.list file is correct, you should not be getting this message.  Please check this sources.list file again.  Look for any other lines that might mention any other repository.  Also, look in the folder /etc/apt/sources.list.d and see if any files in this folder mention any other reporitories.  If you do have any other lines, post them here.  I think that you might have a left over line from another repository that may be messing things up.

Is this a bug with task-gnome-desktop only?  Try this, do you get any errors if you try to install ?

And the output of ?

As far as running an installation disk from within a running vps instance, I am not aware of how to do this.

I want to ask, have you considered migrating the debian vps to devuan?

If you can "attach" the iso to the vps machine-
The simpliest way would be to "attach" the iso to the virtual machine, but not all commercial vps providers offer this capability.  Is this a possibility?  If so, simply "attach" and reboot the server and the devuan install disk should start.  I assume here that you have the capability to see the "virtual physical" screen to navigate through the installation process.

Another option would be to build your devuan.iso disk locally, or use a devuan release live.iso build and upload and attach it to the vps.  This way, with a live build you could access the vps by way of ssh and run the refractainstaller program.

If this "attach" capability is not available, I have known a provider to install a custom .iso that I requested.  You might want to request this from your provider.

Last idea, use rsync to transfer your custom iso build to the vps and in essence to overwrite all that is there.  This would replace what you currently have on the vps with what you have built locally.  Or, instead of building what you want, use an official devuan live disk release.  This is more advanced, but it is possible.  I have done this several times and it is a lifesaver.  Let me know if this interests you.

This is also an excellent reason to have a virtual machine program on your local end to test these options out, before attempting on a production vps.

To add a little more here, the problem may show up again.  If you purge the "systemd-standalone-sysusers" package, and pin it in apt so it does not get reinstalled, in  /etc/apt/preferences.d/nosystemd  like so:

And then reinstall the packages that got removed when "systemd-standalone-sysusers" was purged, it should install a compatible package called "opensysusers".   This is what I did a month ago to proceed with updating as I was getting the same error message(s).