Revised migration page on www

golinux · 2022-08-08 00:56:36

Recent user feedback prompted some revisions to the Migrate from Debian Bullseye to Chimaera page on devuan.org.

In addition to classic, hands-on manual instructions there are now 2 more prominently highlighted scripts to partially automate the process.

Please review, test if possible and provide constructive feedback if warranted.

Not included on the revised www page but worth a mention here for those who use ansible is jaromil's debian-to-devuan-ansible-role.yaml for the non-interactive migration of Debian 11 "Bullseye" to Devuan 4 "Chimaera".

auanta · 2022-08-08 03:11:12

Excellent work, go team, thank you! I will test this ASAP!!

tomasz · 2022-08-08 03:20:54

Looks like someone's forgotten about the network again. Or is this on purpose?

auanta · 2022-08-08 03:41:25

tomasz wrote:

Looks like someone's forgotten about the network again. Or is this on purpose?

Please share the output of the error you are seeing?

tomasz · 2022-08-08 05:03:05

auanta wrote:

tomasz wrote:
Looks like someone's forgotten about the network again. Or is this on purpose?
Please share the output of the error you are seeing?

Are you feeling accused?

golinux · 2022-08-08 13:56:57

Reminder: This is a technical forum. Not group therapy.

fsmithred · 2022-08-08 17:12:32

tomasz, what network issue did you run into on migrating from bullseye to chimaera? If you already explained it in a previous post, then yes, it was forgotten. I've been away for a few days. Help me out here and provide a link to the previous post or explain it here. Thanks.

tomasz · 2022-08-08 17:38:27

@fsmithred

I don't remember that issue. I'd have to meditate, it was so long ago. I might not recall. What I meant about networking here was linked to my other thread about this topic here and post #6 in particular.

delgado · 2022-08-08 18:31:31

EDIT / mostly deleted.

Network setup for migration seems to rely on network-manager and NOT dhcp, to circumvent the device name change to eth0.

10 minutes later ... But that is not true for rrq's migration script.

Now I'm confused. I'll go for migration in chroot and look for the network afterwards.

Last edited by delgado (2022-08-09 19:09:46)

auanta · 2022-08-11 21:24:36

Here I go, testing..

Let's get this perfect. I follow manual instructions with an x200 running a fresh net-install of Debian Bullseye, no configuration, base packages.

After the root@debian:~# apt-get update --allow-insecure-repositories step, it does not result that... Oh, "should now be installed" -- can we change the wording on that to "Now, we should" because when phrased in the past tense it implied that following that command, somehow the keys would be installed. I know it sounds silly but the clear wording helps..

Everything looks good on this machine. This time no struggle! I should retry on the other.. Not over yet.. Rebooting now..

If I can reboot... Reboot and shutdown commands are not working lol..

root@debian:~# reboot
bash: reboot: command not found
root@debian:~# shutdown -t time now
bash: shutdown: command not found
root@debian:~#

So I log out and this happens.. https://odysee.com/VID_20220811_173448

No worries let's see..

Last edited by auanta (2022-08-11 21:47:14)

Dutch_Master · 2022-08-11 21:43:55

You can fix that with the following (and it should be in the instructions too!)

echo "ALWAYS_SET_PATH yes" >> /etc/default/su

This forces the shell to set the root path if you elevate permissions from a regular user to root, using su. It works, even skeptical me was converted. This was default behavior until upstream Debian changed it, citing "this was originally as intended under Unix" or something of that nature

auanta · 2022-08-11 21:52:03

Dutch_Master wrote:

echo "ALWAYS_SET_PATH yes" >> /etc/default/su
This forces the shell to set the root path if you elevate permissions from a regular user to root, using su. It works, even skeptical me was converted. This was default behavior until upstream Debian changed it, citing "this was originally as intended under Unix" or something of that nature

~~Good idea! Sadly, no dice for me.. I am using a fresh Debian. What gives.. I don't feel like pressing the power button so I'm gonna keep searching commands~~

I take that back! I just needed to type su again, and reboot command works now.

Continuing on because why double post. https://odysee.com/VID_20220811_174931:8

I am plugged in directly to the router to eliminate complexity. After reboot, the network stopped working, so dist-upgrade does not work.

My solution (for wireless might need to install an app at the eudev and sysvinit-core step or long before messing with the apt sources list):

ip and dhclient is installed by default on a new debian so this should be the generic solution.

ip link (to check that your interface is up while plugged in)
dhclient
apt dist-upgrade
apt-get install task-xfce-desktop (because this is the default for devuan)
root@devuan:~# apt-get autoremove --purge
root@devuan:~# apt-get autoclean

So this is what should happen to most typical users (a lot of people use Gnome, X200s are popular, xfce is default, wired connection)

Last edited by auanta (2022-08-11 22:43:56)

golinux · 2022-08-11 22:23:17

@auanta . . . perhaps you would like to collect all the little fixes you are discovering and publish them in md on our git? Or the forum?

auanta · 2022-08-11 22:44:44

golinux wrote:

@auanta . . . perhaps you would like to collect all the little fixes you are discovering and publish them in md on our git? Or the forum?

I'll put them in git!

golinux · 2022-08-11 23:36:26

auanta wrote:

golinux wrote:
@auanta . . . perhaps you would like to collect all the little fixes you are discovering and publish them in md on our git? Or the forum?
I'll put them in git!

Great! Would be very useful for those who are just arriving. All the info is documented *somewhere* but having it in one place would be quite handy!

auanta · 2022-08-12 04:01:45

I need to figure that out tomorrow, but for now let me put my second attempt at migration here before I forget.

So I did it differently this time around. I installed and used sudo, wireless firmware, the MATE desktop, anki, zim, and kdeconnect. This is actually a selection of my fav daily apps from the other machine. So the mayhem begins upon reboot.

The reboot was normal but systemd failed to load a bunch of stuff and was hanging at boot. I managed to log in with CTRL + ALT + F1/F2/F3/F4 (switching between them until one of them gave me a tty) and landed on tty1.

From there I logged in. Could not use arrow keys, this would result in systemd spitting errors at me about failed to load stuff. I ALSO had to struggle to type on the keyboard, hitting every button twice to register. Got it on camera so I can review tomorrow.

I had to use wpa_supplicant in order to do dist-upgrade, but first I had to configure a config file, and the only way the system permitted me to do it (using sudo here) was to manually edit one and then pass the config in the wpa_supplicant command. There should probably be a way to do it in one line without much hastle, for later review.. It was awful to type anything at all. I ended up making use of CTRL-R to search and save me the frustration of mistyped commands and navigated the line with CTRL-A and CTRL-E.

After passing a sudo wpa_supplicant etc, I did dhclient and got connected. Ran dist-upgrade. This time the exact same type of breakage I saw before on the other machine happened. The system is now unable to perform the migration, essentially, and is in an uncertain state. I will leave it for now at this step.

I now know how to reproduce the issue, sadly maybe not all systems can be migrated depending on what packages they have installed on their system.

golinux · 2022-08-12 04:07:34

Thanks for posting again. Chances of migration success are best with a vanilla install. I think there is something to that effect in the notes. (Too tired to check atm.)

See you tomorrow.

auanta · 2022-08-12 14:02:53

golinux wrote:

Thanks for posting again. Chances of migration success are best with a vanilla install. I think there is something to that effect in the notes. (Too tired to check atm.)
See you tomorrow.

Noting from the errors that in fact it is complaining about dependencies on systemd, I decided to proceed with the next step in removing systemd. I turned on my laptop and the same errors with systemd hanging and failing to load stuff but actually this time (I think thanks to dist-upgrade) I got to the login manager. Uh.. and just as I type this the screen dims and the login manager is gone! OK back on tty1 let's try finishing this.

Removing systemd and libnss-systemd

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
libpam-systemd : Depends: systemd but it is not going to be installed
elogind but it is not going to be installed
consolekit but it is not going to be installed
systemd-sysv : PreDepends: systemd but it is not going to be installed
Recommends: libnss-systemd but it is not installable
udev : Depends: libudev1 (= 247.3-7)
E: Unmet dependencies. Try 'apt --fix-broken-install' with no packages (or specify a solution).

apt autoremove --purge and apt autoclean also spit out a cycle of similar dependency hell messages.

If we know which dependencies will conflict, it should be possible to run a command prior to the migration to scan for those packages and either inform the user to abort the migration, or uninstall the offending packages prior to migration and reinstall them later.

farmatito · 2022-08-17 13:10:19

Hi,
I've taken care of most of the problems you have experienced in this script.

https://git.devuan.org/farmatito/migration

You are welcome If you want to take a look for inspiration or
if you volunteer as a tester.

Ciao.

auanta · 2022-09-18 22:07:40

Hi, I'm working on some home server stuff today and it leads me to do another migration so here we go, testing.

On this particular Debian I haven't installed much, just MATE Desktop, KDE Connect, LibreOffice, Firefox.. I haven't had it for much time.

So,

$ sudo nano /etc/apt/sources.list
$ sudo apt update --allow-insecure-repositories
[sudo] password for x: 
Get:1 http://deb.devuan.org/merged chimaera InRelease [33.5 kB]
Get:2 http://deb.devuan.org/merged chimaera-updates InRelease [26.1 kB]
Get:3 http://deb.devuan.org/merged chimaera-security InRelease [26.2 kB]
Ign:1 http://deb.devuan.org/merged chimaera InRelease
Get:4 http://deb.devuan.org/merged chimaera/main amd64 Packages [8,313 kB]
Ign:2 http://deb.devuan.org/merged chimaera-updates InRelease
Ign:3 http://deb.devuan.org/merged chimaera-security InRelease
Get:5 http://deb.devuan.org/merged chimaera/main Translation-en [6,480 kB]     
Get:6 http://deb.devuan.org/merged chimaera-updates/main amd64 Packages [2,612 B]
Get:7 http://deb.devuan.org/merged chimaera-updates/main Translation-en [2,343 B]
Get:8 http://deb.devuan.org/merged chimaera-security/main amd64 Packages [186 kB]
Get:9 http://deb.devuan.org/merged chimaera-security/main Translation-en [2,178 B]
Fetched 15.1 MB in 39s (385 kB/s)                                              
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
142 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: GPG error: http://deb.devuan.org/merged chimaera InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 94532124541922FB
W: The repository 'http://deb.devuan.org/merged chimaera InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://deb.devuan.org/merged chimaera-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 94532124541922FB
W: The repository 'http://deb.devuan.org/merged chimaera-updates InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://deb.devuan.org/merged chimaera-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 94532124541922FB
W: The repository 'http://deb.devuan.org/merged chimaera-security InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
$ sudo apt install devuan-keyring --allow-unauthenticated
[sudo] password for x: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
  grub-pc-bin
Use 'sudo apt autoremove' to remove it.
The following NEW packages will be installed:
  devuan-keyring
0 upgraded, 1 newly installed, 0 to remove and 142 not upgraded.
Need to get 36.1 kB of archives.
After this operation, 68.6 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  devuan-keyring
Authentication warning overridden.
Get:1 http://deb.devuan.org/merged chimaera/main amd64 devuan-keyring all 2022.09.04 [36.1 kB]
Fetched 36.1 kB in 2s (18.3 kB/s)       
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend requires a screen at least 13 lines tall and 31 columns wide.)
debconf: falling back to frontend: Readline
Selecting previously unselected package devuan-keyring.
(Reading database ... 163914 files and directories currently installed.)
Preparing to unpack .../devuan-keyring_2022.09.04_all.deb ...
Unpacking devuan-keyring (2022.09.04) ...
Setting up devuan-keyring (2022.09.04) ...
$ sudo apt update
Get:1 http://deb.devuan.org/merged chimaera InRelease [33.5 kB]
Get:2 http://deb.devuan.org/merged chimaera-updates InRelease [26.1 kB]
Get:3 http://deb.devuan.org/merged chimaera-security InRelease [26.2 kB]
Fetched 85.8 kB in 2s (54.0 kB/s)   
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
142 packages can be upgraded. Run 'apt list --upgradable' to see them.
$ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  fonts-quicksand grub-pc-bin libplymouth5 plymouth plymouth-label
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
  clearlooks-phenix-deepsea-theme deepsea-icon-theme dmz-cursor-theme gnome-extra-icons gtk3-nooverlayscrollbar initscripts insserv
  linux-image-5.10.0-18-amd64 startpar sysv-rc
The following packages have been kept back:
  apt apt-utils init libapt-pkg6.0 libcolord2 libpolkit-agent-1-0 libpolkit-gobject-1-0 libsystemd0 libudev1 policykit-1 udev udisks2
  util-linux
The following packages will be upgraded:
  avahi-autoipd avahi-daemon base-files bsdextrautils bsdutils colord colord-data dbus dbus-x11 desktop-base distro-info-data dpkg
  eject fdisk firefox-esr fonts-opensymbol gir1.2-gdkpixbuf-2.0 grub-common grub-efi grub-efi-amd64 grub-efi-amd64-bin
  grub-efi-amd64-signed grub-pc-bin grub2-common gstreamer1.0-gtk3 gstreamer1.0-plugins-good init-system-helpers krb5-locales
  libavahi-client3 libavahi-common-data libavahi-common3 libavahi-core7 libavahi-glib1 libayatana-appindicator3-1 libblkid1 libc-bin
  libc-l10n libc6 libcolorhug2 libcpupower1 libcurl3-gnutls libcurl4 libdbus-1-3 libdpkg-perl libfdisk1 libgdk-pixbuf-2.0-0
  libgdk-pixbuf2.0-bin libgdk-pixbuf2.0-common libgnutls30 libgssapi-krb5-2 libhttp-daemon-perl libjavascriptcoregtk-4.0-18
  libjuh-java libjurt-java libk5crypto3 libkrb5-3 libkrb5support0 libldb2 liblibreoffice-java liblightdm-gobject-1-0 libmount1
  libpcre2-16-0 libpcre2-8-0 libpcsclite1 libpoppler-cpp0v5 libpoppler-glib8 libpoppler102 libprocps8 libreoffice-base-core
  libreoffice-calc libreoffice-common libreoffice-core libreoffice-draw libreoffice-gtk3 libreoffice-help-common
  libreoffice-help-en-us libreoffice-impress libreoffice-math libreoffice-style-colibre libreoffice-writer libridl-java libsmartcols1
  libsmbclient libsnmp-base libsnmp40 libtirpc-common libtirpc3 libudisks2-0 libuno-cppu3 libuno-cppuhelpergcc3-3
  libuno-purpenvhelpergcc3-3 libuno-sal3 libuno-salhelpergcc3-3 libunoloader-java libuuid1 libwbclient0 libwebkit2gtk-4.0-37
  libxslt1.1 lightdm linux-image-amd64 locales mokutil mount poppler-utils popularity-contest procps publicsuffix python3-ldb
  python3-reportbug python3-uno reportbug rsyslog samba-libs sysvinit-utils task-desktop task-english task-laptop task-mate-desktop
  tasksel tasksel-data tzdata uno-libs-private unzip ure util-linux-locales xserver-common xserver-xorg-core xserver-xorg-legacy
  zlib1g
129 upgraded, 10 newly installed, 0 to remove and 13 not upgraded.
Need to get 295 MB of archives.
After this operation, 339 MB of additional disk space will be used.
Do you want to continue? [Y/n]                                           
# series of "Get:# http://deb.devuan.org/merged chimaera/main amd64 packagename all 1:4.1 [#### kB] 
# series of messages unpacking and processing packages
# done, no errors
$ sudo apt install eudev sysvinit-core
[sudo] password for x: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  fonts-quicksand grub-pc-bin libplymouth5
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  elogind libelogind0 libeudev1 libpam-elogind libudev1
  orphan-sysvinit-scripts udev
Suggested packages:
  bootlogd
The following packages will be REMOVED:
  dbus-user-session libnss-systemd libpam-systemd libsystemd0 plymouth
  plymouth-label systemd systemd-sysv systemd-timesyncd
The following NEW packages will be installed:
  elogind eudev libelogind0 libeudev1 libpam-elogind orphan-sysvinit-scripts
  sysvinit-core
The following packages will be upgraded:
  libudev1 udev
2 upgraded, 7 newly installed, 9 to remove and 10 not upgraded.
Need to get 2,460 kB of archives.
After this operation, 16.7 MB disk space will be freed.
Do you want to continue? [Y/n] 
Get:1 http://deb.devuan.org/merged chimaera/main amd64 udev amd64 1:3.2.9+devuan4 [2,964 B]
Get:2 http://deb.devuan.org/merged chimaera/main amd64 eudev amd64 3.2.9-10~chimaera1 [1,072 kB]
Get:3 http://deb.devuan.org/merged chimaera/main amd64 libeudev1 amd64 3.2.9-10~chimaera1 [97.7 kB]
Get:4 http://deb.devuan.org/merged chimaera/main amd64 libudev1 amd64 1:3.2.9+devuan4 [2,724 B]
Get:5 http://deb.devuan.org/merged chimaera/main amd64 libelogind0 amd64 246.10-2 [250 kB]
Get:6 http://deb.devuan.org/merged chimaera/main amd64 elogind amd64 246.10-2 [657 kB]
Get:7 http://deb.devuan.org/merged chimaera/main amd64 libpam-elogind amd64 246.10-2 [208 kB]
Get:8 http://deb.devuan.org/merged chimaera/main amd64 sysvinit-core amd64 2.96-7+devuan2 [156 kB]
Get:9 http://deb.devuan.org/merged chimaera/main amd64 orphan-sysvinit-scripts all 0.07 [12.6 kB]
Fetched 2,460 kB in 7s (376 kB/s)                                              
Reading changelogs... Done
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend requires a screen at least 13 lines tall and 31 columns wide.)
debconf: falling back to frontend: Readline
Preconfiguring packages ...
(Reading database ... 176137 files and directories currently installed.)
Removing dbus-user-session (1.12.20-2) ...
Removing libnss-systemd:amd64 (247.3-7) ...
Checking NSS setup...
Removing plymouth-label (0.9.5-3) ...
Removing plymouth (0.9.5-3) ...
update-initramfs: deferring update (trigger activated)
Removing systemd-timesyncd (247.3-7) ...
dpkg: systemd: dependency problems, but removing anyway as you requested:
 systemd-sysv depends on systemd.
 mate-power-manager depends on systemd | elogind | consolekit; however:
  Package systemd is to be removed.
  Package elogind is not installed.
  Package consolekit is not installed.
 libpam-systemd:amd64 depends on systemd (= 247.3-7).

Removing systemd (247.3-7) ...
systemd is the active init system, please switch to another before removing syst
emd.
dpkg: error processing package systemd (--remove):
 installed systemd package pre-removal script subprocess returned error exit sta
tus 1
dpkg: too many errors, stopping
Errors were encountered while processing:
 systemd
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)
$ sudo apt -f install 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  fonts-quicksand grub-pc-bin libplymouth5
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 13 not upgraded.

Reboot.

Then I get messages:

[FAILED] Failed to start Avahi mDNS/DNS-SD Stack.
[FAILED] Failed to start System Logging Service.
[FAILED] Failed to start WPA Supplicant.
[FAILED] Failed to start Network Manager.

Then I get to the login screen, I log in, everything looks normal, but of course, I can't get on the network. Networking services are disabled, network-manager is disabled.

A minute later, it goes to a black screen and a blinking cursor, and not because of screensaver, because I was using the computer.

The system is unresponsive, and I have to move to tty1 but while fighting with the keyboard (pressing the same keys twice to get a single press). Can't start X. The above error messages appear again.

I can't actually proceed now with this machine because wifi doesn't work anymore and I have no ethernet port.

And that concludes my migration adventures, I don't think migration works, maybe systemd is just too much of a beast. A clean install is best. I would write in the guide that migrations are generally not recommended.

Last edited by auanta (2022-09-18 22:35:42)

PedroReina · 2022-09-19 08:59:12

auanta wrote:

wifi doesn't work anymore and I have no ethernet port.

I have an USB to ethernet adapter at hand, just in case.

delgado · 2022-09-20 19:20:10

What worked for me was a slight modification of the order:
apt install sysvinit-core
reboot
Then following the manual instructions.

The basic idea was to change pid 1 to init before doing something else.
That was after reading https://dev1galaxy.org/viewtopic.php?id=5147 post#6, and rrq's migration script and jaromil's ansible.
EDIT: Or if you want to follow the original procedure successfully, then consult farmatito's script for additional measures.

Last edited by delgado (2022-09-25 12:17:18)

The officially official Devuan Forum!

#1 2022-08-08 00:56:36

Revised migration page on www

#2 2022-08-08 03:11:12

Re: Revised migration page on www

#3 2022-08-08 03:20:54

Re: Revised migration page on www

#4 2022-08-08 03:41:25

Re: Revised migration page on www

#5 2022-08-08 05:03:05

Re: Revised migration page on www

#6 2022-08-08 13:56:57

Re: Revised migration page on www

#7 2022-08-08 17:12:32

Re: Revised migration page on www

#8 2022-08-08 17:38:27

Re: Revised migration page on www

#9 2022-08-08 18:31:31

Re: Revised migration page on www

#10 2022-08-11 21:24:36

Re: Revised migration page on www

#11 2022-08-11 21:43:55

Re: Revised migration page on www

#12 2022-08-11 21:52:03

Re: Revised migration page on www

#13 2022-08-11 22:23:17

Re: Revised migration page on www

#14 2022-08-11 22:44:44

Re: Revised migration page on www

#15 2022-08-11 23:36:26

Re: Revised migration page on www

#16 2022-08-12 04:01:45

Re: Revised migration page on www

#17 2022-08-12 04:07:34

Re: Revised migration page on www

#18 2022-08-12 14:02:53

Re: Revised migration page on www

#19 2022-08-17 13:10:19

Re: Revised migration page on www

#20 2022-09-18 22:07:40

Re: Revised migration page on www

#21 2022-09-19 08:59:12

Re: Revised migration page on www

#22 2022-09-20 19:20:10

Re: Revised migration page on www

Board footer