Upgrading from Trixie to Forky in late 2025(proposal)

Upgrading from Trixie to Forky in late 2025(proposal) - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone Pro (https://forum.pine64.org/forumdisplay.php?fid=177)
+--- Forum: PinePhone Pro Software (https://forum.pine64.org/forumdisplay.php?fid=179)
+--- Thread: Upgrading from Trixie to Forky in late 2025(proposal) (/showthread.php?tid=20047)

Upgrading from Trixie to Forky in late 2025(proposal) - biketool - 10-20-2025

This is a proposal for a guide to upgrade to Forky(Mobian testing) from Trixie(the previous testing release)
This has not yet been tested so I am putting it out here for comment as a modification of the Bookworm --> Trixie guide
https://blog.mobian.org/posts/2025/10/new-stable-rotating-keys/
It seems there are errors but we can fix these.

I will first recommend everyone with disk space use the tow-boot blue light special bulk storage mode and save the / of your PP or PPp to your computer, this will take a while to do but even if encryptde is pretty easy, in my ubuntu derivitave OS the GUI asked if I wanted to decrypt the volume, entered password, and I had access to my root. A alternative is to use a USB mass storage device over an adapter or a big SD card to save your root or at least your /home.

below is form the guide linked above with some lined out do-not instructions and my edits in green
_______________________________________________________________

keep your device plugged to a power source: such an upgrade can be a rather long process, you don’t want to run out of battery half-way there!
backup all your personal data
really, we mean it: backup all your personal data!
install

Code:
openssh-server
and execute the entire upgrade process over SSH (and preferrably using

Code:
screen
or a similar tool, so the upgrade can carry on even if the network connection is lost)
ensure your Bookworm installation is fully up-to-date; as the GPG key we use for signing the package repository has expired since the Bookworm release, you’ll probably need to run

Code:
apt update && apt dist-upgrade
at least twice: the first time it will update the Mobian keyring package, the second invocation will pull in the latest updates for Mobian-specific packages
reboot, then edit both

Code:
/etc/apt/sources.list
and

Code:
/etc/apt/sources.list.d/mobian.list
, replacing all occurences of

Code:
bookworm
with

Code:
trixie
6B reboot, then edit both

Code:
/etc/apt/sources.list.d/debian.sources
and

Code:
/etc/apt/sources.list.d/mobian.list
, replacing all occurences of

Code:
trixie
with

Code:
forky
in both files; you should then stop the

Code:
greetd
service (this will stop all running graphical applications, and is why SSH is needed!) and run

Code:
apt update && apt dist-upgrade
once again
write down the list of packages removed by

Code:
apt dist-upgrade
which start with

Code:
mobian-
as those will have to be reinstalled later on to restore full functionality of your device; please note that some packages have been renamed/replaced in Trixie, so it can be expected to see e.g.

Code:
phog
or

Code:
pinephonepro-tweaks
in the list of removed packages
reinstall all

Code:
mobian-*
packages removed in the previous step; this will remove

Code:
pulseaudio
from the system, which is to be expected as Mobian now relies on (and mandates the use of) PipeWire
run

Code:
apt autoremove
to clean up unneeded packages

________________________________________________

Does this look correct? it seems that an apt update && apt upgrade will update the signing crypto keys so we dont need to dl that.