sudo apt update && sudo apt upgrade -y
Reading package lists... Done
E: Release file for https://repo.pureos.net/pureos/dists/crimson/InRelease is expired (invalid since 8h 22min 15s). Updates for this repository will not be applied.
E: Release file for https://repo.pureos.net/pureos/dists/crimson-security/InRelease is expired (invalid since 8h 27min 42s). Updates for this repository will not be applied.
E: Release file for https://repo.pureos.net/pureos/dists/crimson-updates/InRelease is expired (invalid since 8h 27min 42s). Updates for this repository will not be applied.
Hi everyone! The repository was not updating for a few days because a SSL certificate expired on a server that the system has to query while building the repository metadata. For some reason, our monitoring did not pick that up (we will find out why), and Laniakea is logging the error but does not send a very visible notification - yet. I will change that now, to ping us on Matrix if that ever happens again.
I also reconfigured certbot again, this time automatic renewal should not fail.
We are very sorry for the inconvenience, and the metadata should be fully up to date again in a few minutes.
Best,
Matthias
Hi, I updated this morning and it came down a new kernel. On rebooting it, I got nearly a heart break when I saw the message “crypsetup…” for minutes until the boot continued with success. Don’t know what the L5 was doing.
installed a new kernel so you just wait and it should boot up, might require two reboots I noticed. It froze on the second reboot for me at login screen. Third did the charm.
Myself, after this morning’s update I find the touchscreen unresponsive at “Enter disk decryption passphrase” screen, same as described in this post from 2 years ago: Anyone experience an issue with the latest update?
Would anyone know if the same solution from that thread works again now? I’m pretty close to giving up on telephony in general!
That’s no fun. There’s no reason I can see that it wouldn’t work, but there may be an easier way. My problem came about in a weird way, because the drive wasn’t partitioned right, so the fix necessary was probably more complicated than a normal corrupted file or something. It might be good to see if your problem came about for the same reason. Have you installed uuu and connected via jumpdrive before? There’s a way to replace some of your boot files that way:
I’d try fixing by replacing those files first. In any case, I’d check for freespace on your partitions to make sure it doesn’t happen again. I understand they implemented a fix to prevent the issue from happening due to a filled up boot drive, but it didn’t stop mine due to a filled up root drive. Fixing the partition prevented it from reoccurring.
Oddly enough, my phone puked (i.e. didn’t respond to touch at encryption log-in) after a recent update too, so I went through the easier process through jumpdrive again. However, I did notice the files were a bit different than they used to be. Now every file, new and old, has its version number. e.g., there’s no vmlinuz nor vmlinuz.bak. There are however four files in the fashion, vmlinuz-6.6.0-1-librem5 and vmlinuz-6.5.0-1-librem5. I couldn’t find a quick way to have the boot sequence point to the older version, so I just copied the four 6.5.0-1’s over the 6.6.0-1’s, and it seemed to do the trick. Maybe someone has a more clever way of just pointing to the vintage file?
Sad side note - when I ran the update again (after I copied over and got it to boot fully), the reboot did the same thing - no touch response at the encryption login screen. But the copy-over worked just fine again. Guess I’ll just wait awhile before I update the phone again, and hope an updated update comes out that doesn’t have the same issue on my phone.
It’s different from most big computers that I have seen where those names will exist without version numbers as symbolic links to the names with the chosen version number (so theoretically it could be easy to revert) - although the previous version may be .old rather than .bak.
Strangely though I am running 6.6.0-1 and I am not experiencing the problem entering the encryption passphrase.
I did delete most of them, but I still had the same issue on the upgrade reattempt. Now I figure I’ll just wait until there’s two versions up, and hopefully jumping the current one will work?
Having this same issue with Crimson for a few days now.
Reading package lists... Done
E: Release file for http://repo.pureos.net/pureos/dists/crimson/InRelease is expired (invalid since 3d 19h 28min 57s). Updates for this repository will not be applied.
E: Release file for http://repo.pureos.net/pureos/dists/crimson-security/InRelease is expired (invalid since 3h 33min 57s). Updates for this repository will not be applied.
E: Release file for http://repo.pureos.net/pureos/dists/crimson-updates/InRelease is expired (invalid since 3h 33min 49s). Updates for this repository will not be applied.
)
