This is how I managed to upgrade to Crimson on my Librem 5:
I first tried to use the graphical installer but the battery never reached the 90% requirement; it seemed stuck at 88%. I tried to remove the battery to see if it would trick the system to upgrade anyway but that didn’t work. (Purism doesn’t ship replacement batteries outside the US so I think this battery charge requirement is going to be an obstacle for quite a few users.)
I then went for the manual upgrade method, replacing byzantium → crimson in /etc/apt/sources.list and running sudo apt update && sudo apt full-upgrade. I allowed the system to automatically restart services during the install and initially watched the installation proceed. I then had to go away for a little while. When I returned the screen lock had triggered and when I tried to input the password, all numbers had been replaced by comma, apostrophe and other such characters and since my password contained one or more numbers I was unable to unlock. It made no difference trying to switch to a different language or keyboard layout. After waiting a few minutes I decided to power off the device.
After booting the device the keyboard looked alright again and I was able to input the password. It was clear however that the system wasn’t exactly in good order. Several applications had wrong icons and some of them failed to load, including the terminal! Now what to do here? Then I realize that I’ve got emacs installed, both the graphical and the terminal version. From the latter, I was able to start up eshell – not sure why I didn’t go for the regular shell – and fix the broken install by first running sudo dpkg --configure -a and then sudo apt upgrade. Everything was good after rebooting the device again.
Success! Now I get to figure out how to get the eMMC boot to use the profile on my Crimson uSD and failover to the eMMC profile if the uSD is absent.
Edit: OK, not quite.I get lots of failed to fetch errors on sudo apt update. Did an upgrade anyway, and upgraded 16 packages. Still the error on update, though.
Looks like the repo might have been being updated about an hour ago. Are you still getting errors?
I just did apt update on my phone (in-place upgraded to crimson back in March, so not identical to your scenario) and did not receive any error messages.
Obvious question: Do you have any non-standard repos in sources.list ?
/etc/apt# grep -v ^# sources.list
deb https://repo.pureos.net/pureos crimson main
deb https://repo.pureos.net/pureos crimson-updates main
deb https://repo.pureos.net/pureos crimson-security main
And what are the error messages? The error messages should be slightly easier to work with if coming directly from apt as compared with from inside a Python program.
Booted the L5 from SD card and got no errors on update. Booted from eMMC and got “Temporary failure resolving ‘repo.pureos.net’” for each of the three repositories (main, updates main and security main). No illegal aliens in sources.list.
When I ping the repo, I get “repo.pureos.net: Temporary failure in name resolution”
OK… Wi-Fi had dropped off. Cycled HKS a couple of times and we are good!
I still have the old card in there. When I moved about a year ago, I misplaced the SparkLAN I bought from Purism. If I don’t find it, I’ll just buy new one – it not as if I was buying RAM, after all.
im on pure oS gnome version 3.30 2 but was looking for a new upgrade os like crimson but here is what your command gave
sudo apt full-upgrade
[sudo] password for me
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Wi-Fi had dropped off. Cycled HKS a couple of times and we are good!