The officially official Devuan Forum!

yeti

Member

From: I'm not here: U R halucinating

Registered: 2017-02-23

Posts: 324  

Transgrading DeBIan -> DeVUan

((( Quasi-reply to Index » ARM Builds » Updating kernel (Raspberry pi 2). )))

Still no kernel updates?

Phewww...

Long ago (ASCII days?) I transgraded some Cubietrucks (UBoot images) from Debian to Devuan and so Debian's kernel update automagism survived.

I repeated that some days ago for two Debian12/RasPi2 and one Debian12/RasPi1 and doing that with two Debian12/RasPi4 is on my to do list.  The dist-upgrade step of the migration included a kernel update, so I'm now ommmmmmptimistically awaiting the next regular kernel update.

—▷ https://www.devuan.org/os/documentation … o-daedalus

Redoing this on some Cubietrucks (and maybe BananaPi-R1) is on my to do list too, but I'm fighting a ™Dark Energy Infection™ in that list...  YKWIM...

Maybe we should look at Debian's RasPI image generator and fork it to generate Devuan images directly?  Or is someone ommmmmmptimistic enough to ask the [Debian Raspberry Pi Maintainers] to add Devuan directly?  I'm not ... *sigh!*

—▷ https://salsa.debian.org/raspi-team/image-specs

OTOH:  Does accidentally someone know why DeBIan's daily builds of RasPI images are stuck since 2024-03-30?  Or has the page changed to a different URL and that one contains newer builds?

—▷ https://raspi.debian.net/daily-images/

---

(-:  𝙸 𝚍𝚘 𝚗𝚘𝚝 𝚙𝚕𝚊𝚢 𝙽𝚎𝚝𝚑𝚊𝚌𝚔.  𝙸 𝚍𝚘 𝚙𝚕𝚊𝚢 𝙶𝙽𝚄𝚂.  :-)
<𝚋𝚘𝚍𝚢 𝚘𝚗𝚕𝚘𝚊𝚍='𝚍𝚘𝚌𝚞𝚖𝚎𝚗𝚝.𝚋𝚘𝚍𝚢.𝚒𝚗𝚗𝚎𝚛𝙷𝚃𝙼𝙻="𝙳𝚒𝚜𝚊𝚋𝚕𝚎 𝙹𝚂!";'>
𝔓𝔩𝔢𝔞𝔰𝔢 𝔩𝔢𝔞𝔳𝔢 𝔶𝔬𝔲𝔯 𝔣𝔞𝔲𝔩𝔱𝔰 𝔦𝔫 𝔱𝔥𝔢 𝔰𝔢𝔠𝔱𝔦𝔬𝔫 𝔟𝔢𝔩𝔬𝔴 𝔞𝔫𝔡 𝔡𝔬𝔫'𝔱 𝔣𝔬𝔯𝔤𝔢𝔱 𝔱𝔬 𝔲𝔫𝔰𝔲𝔟𝔰𝔠𝔯𝔦𝔟𝔢!

yeti

Member

From: I'm not here: U R halucinating

Registered: 2017-02-23

Posts: 324  

Re: Transgrading DeBIan -> DeVUan

Observations so far:

Packages adding UIDs/GIDs being reïnstalled over this process sometimes get different numeric IDs then and some files (e.g. in /var/{lib,spool,...}) need to be corrected manually.  With packages having multiple different UIDs and GIDs (e.g. postfix), this can be a pain.

Better catch a detailed listing of all files, their IDs and modes before starting.

Transgrading systems that were installed from Debian12 (armel/armhf) images and immediately got transgraded, everything was smooth.  I think ...  o;-)

With a system that was older (Debian11/armel -> Debian12 -> Devuan5) I noticed SSH not working after the transgrade.

Guess why:

~$ ls -l /etc/rc?.d/*ssh
lrwxrwxrwx 1 root root 13 Aug 29  2018 /etc/rc2.d/S01ssh -> ../init.d/ssh
lrwxrwxrwx 1 root root 13 Aug 29  2018 /etc/rc3.d/S01ssh -> ../init.d/ssh
lrwxrwxrwx 1 root root 13 Aug 29  2018 /etc/rc4.d/S01ssh -> ../init.d/ssh
lrwxrwxrwx 1 root root 13 Aug 29  2018 /etc/rc5.d/S01ssh -> ../init.d/ssh

Later I found the same glitch on a Debian11/amd64 system (still to be transgraded).

Better check this before transgrading headless systems.

When systemd's NTP functionality is deinstalled on a system without RTC, the system time will be 1970-1-1 after the next reboot.  Maybe installing ntpsec or chrony before the 1st reboot is a nice idea?

Two Debian12 Pi4 and a Debian11 Thinkpad T510 are still in the queue to be transgraded.  For quite a while I already installed new systems (x86, amd64) directly as Devuan, but that T510 is left over.  For ARMIsh systems it is a restart with Devuan.

Last edited by yeti (Today 14:25:08)

---

(-:  𝙸 𝚍𝚘 𝚗𝚘𝚝 𝚙𝚕𝚊𝚢 𝙽𝚎𝚝𝚑𝚊𝚌𝚔.  𝙸 𝚍𝚘 𝚙𝚕𝚊𝚢 𝙶𝙽𝚄𝚂.  :-)
<𝚋𝚘𝚍𝚢 𝚘𝚗𝚕𝚘𝚊𝚍='𝚍𝚘𝚌𝚞𝚖𝚎𝚗𝚝.𝚋𝚘𝚍𝚢.𝚒𝚗𝚗𝚎𝚛𝙷𝚃𝙼𝙻="𝙳𝚒𝚜𝚊𝚋𝚕𝚎 𝙹𝚂!";'>
𝔓𝔩𝔢𝔞𝔰𝔢 𝔩𝔢𝔞𝔳𝔢 𝔶𝔬𝔲𝔯 𝔣𝔞𝔲𝔩𝔱𝔰 𝔦𝔫 𝔱𝔥𝔢 𝔰𝔢𝔠𝔱𝔦𝔬𝔫 𝔟𝔢𝔩𝔬𝔴 𝔞𝔫𝔡 𝔡𝔬𝔫'𝔱 𝔣𝔬𝔯𝔤𝔢𝔱 𝔱𝔬 𝔲𝔫𝔰𝔲𝔟𝔰𝔠𝔯𝔦𝔟𝔢!