This is an update to my older post at muwlgr.dreamwidth.org/52029.html .
I still have one remote Ubuntu 18.04 32-bit (i386) instance which is waiting for its CPU or MoBo upgrade. My older version of upgrade-lubuntu3264.sh had too many special cases to prevent it from failing when upgrading our real Ubuntu 18.04 installations, which had quite a lot of side-addons, such as Canon printer drivers, Remmina from Ubuntu PPA, and the like. To simplify the script, I installed 32-bit LUbuntu 18.04 into a virtual machine and tested the script by applying it to the initial 32-bit snapshot until I became satisfied with the upgrade results with a noticeably shorter script version (-43 lines).
The script upgrade-bionic-to-bookworm.sh has been renamed into upgrade-bionic-to-trixie.sh , with added step of upgrading Debian BookWorm to Trixie.
The script build-lubuntu-on-bookworm.sh has been renamed into build-lubuntu-on-debian.sh and gained logic for downloading Bionic .deb and source packages from within debootstrapped Bionic chroot, since updated apt in Trixie stopped supporting SHA1 signature verification. Also, more patching and rebuilding of Bionic packages has been added to reflect the changed structure of LXDE menus and required Debian/Ubuntu packages. As before, it creates a .tar archive in /tmp/ folder which you then need to copy onto any Ubuntu system recently upgraded to Debian and unpack it there.
The script install-lubuntu-on-bookworm.sh has been renamed into install-lubuntu-on-debian.sh and requires having .deb packages unpacked from the above mentioned .tar in the same folder where the script is run.
All these complex procedures became necessary to preserve the familiar experience of working with the system for not overly experienced users. As we remember, LUbuntu did not have essential changes from 10.04 up till 18.04, after which Canonical decided to migrate it to LXQt.
Most probably, after upgrading my last Ubuntu system to Debian, further development of these scripts will be stopped and they will become only historical curiosities, maybe useful for some borrowing and customization but not for direct use.
I still have one remote Ubuntu 18.04 32-bit (i386) instance which is waiting for its CPU or MoBo upgrade. My older version of upgrade-lubuntu3264.sh had too many special cases to prevent it from failing when upgrading our real Ubuntu 18.04 installations, which had quite a lot of side-addons, such as Canon printer drivers, Remmina from Ubuntu PPA, and the like. To simplify the script, I installed 32-bit LUbuntu 18.04 into a virtual machine and tested the script by applying it to the initial 32-bit snapshot until I became satisfied with the upgrade results with a noticeably shorter script version (-43 lines).
The script upgrade-bionic-to-bookworm.sh has been renamed into upgrade-bionic-to-trixie.sh , with added step of upgrading Debian BookWorm to Trixie.
The script build-lubuntu-on-bookworm.sh has been renamed into build-lubuntu-on-debian.sh and gained logic for downloading Bionic .deb and source packages from within debootstrapped Bionic chroot, since updated apt in Trixie stopped supporting SHA1 signature verification. Also, more patching and rebuilding of Bionic packages has been added to reflect the changed structure of LXDE menus and required Debian/Ubuntu packages. As before, it creates a .tar archive in /tmp/ folder which you then need to copy onto any Ubuntu system recently upgraded to Debian and unpack it there.
The script install-lubuntu-on-bookworm.sh has been renamed into install-lubuntu-on-debian.sh and requires having .deb packages unpacked from the above mentioned .tar in the same folder where the script is run.
All these complex procedures became necessary to preserve the familiar experience of working with the system for not overly experienced users. As we remember, LUbuntu did not have essential changes from 10.04 up till 18.04, after which Canonical decided to migrate it to LXQt.
Most probably, after upgrading my last Ubuntu system to Debian, further development of these scripts will be stopped and they will become only historical curiosities, maybe useful for some borrowing and customization but not for direct use.