I don't get it, but now having also tried the desktop live I have the same problem so I'll have to open a new thread, possibly I have an unrelated issue

Yeah, I've spent 2 days on this now (many hours) and looked through all of it including the git repo. Why do you ask?

Let me be clear, I'm aware that the documentation is presented on the website, but when I choose the language of separating them it is because I know behind the server, documentation and web dev are different skillsets. Yes, the end result is they both show up on the website.

And the actual live website, I am speaking about this separately from the git repos. Yes, what I am saying is there is an inconsistency between the live site and the repos. My not finding documentations within the www repo is because the documentation lives in its own "documentation" repo, not the www repo as far as I see when I look at the files.

Writing to confirm for anyone else out there that in 2022 the minimal-live still does not boot on eufi, as I tried on different machines. It will show the boot menu but you can't actually do anything, hitting enter on any of the options results in errors such as "you need to load a kernel first".

I think I'm up to speed now.

I'm searching up and down, and only see one documentation repo. So I think we're ok on that.

The networking issues should be addressed in the documentation. It is possible that this will happen again...or not, depending on the correct instructions.

Before we can do any further testing on the migration at all, we need someone to clarify the correct workflow - details in the bug report.

Wow.. Well, hell is on fire, I started having DNS problems and therefore can't do any actions with apt. Commenting out the network config I made didn't change anything. I rebooted into a new rescue shell. Still can't resolve name servers to debian.org or google.com. The --fix-broken option just removed all my apps for no reason. But the devuan sysvinit-core is installed! I should have waited for further instruction... My bad. Not the end of the world though, I still have my configs.

The old guide doesn't work for me, I try to remove libpam-systemd and it says "virtual packages like libpam-systemd can't be removed". It brings more doubts as to whether that guide applies to this version.

I think my apt and network are too confused to go any further. To make my life a bit easier I'll go ahead and do a regular install on this machine, but I'll test a migration with a spare, when ya'll are ready.

Hey folks I booted into a debian 11 netinstall and am in rescue shell, my system is otherwise fine besides boot issue, it seems the first task is to fix the dependency hell from within rescue shell. My system doesn't want to install eudev. Here's what it looks like:

# apt install eudev
Reading package lists... Done
Building dependency tree... Done
Reading state informatian... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
eudev : Depends: libeudev1 (= 3.2.9-10-chimaera1) but it is not going ta be installed
     Breaks: systemd (> 220) but 247.3-7 is to be installed 
libpam-elogind : Depends: elogind (= 246.10.2) but it is not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

When I try apt install eudev libeudev1 it complains that it conflicts with libudev1.

Not sure if I need to uninstall libpam-elogind.

In anticipation of network issues when boot is fixed I configured the network manually according to instructions here https://git.devuan.org/devuan/documenta … uration.md

Oops, forgot to mention that, it went smoothly with the keyring installed. If there's any difference through apt I would have to redo the migration, and see if apt complains. As this is not a virtual machine, I have to rescue my computer first.

No, I've never heard of tomoyo before, I haven't used MAC either, only MAC addresses obviously It seems to be very confused of even what kind of system I have. Ok, the openrc being there was just a guess. So I guess I got sysvinit but it's missing configuration scripts...

Ah nope, can't enter any runlevel, it just prompts me again. But if I turn it off and boot into recovery mode, I can do runlevel 1 but then it says "no more processes left in this runlevel"