Repositories expired?

Software PureOS
21

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.

3 Likes
22

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.

1 Like
23

I have the following files in /boot:

purism@pureos:/boot$ ls -ltr vm* Sys* init*
-rw-r--r-- 1 root root 26593288 Dec  8 05:26 vmlinuz-6.5.0-1-librem5
-rw-r--r-- 1 root root  4136206 Dec  8 05:26 System.map-6.5.0-1-librem5
-rw-r--r-- 1 root root 66055077 Dec 22 22:19 initrd.img-6.5.0-1-librem5
-rw-r--r-- 1 root root 26806280 Mar 17 14:42 vmlinuz-6.6.0-1-librem5
-rw-r--r-- 1 root root  4176893 Mar 17 14:42 System.map-6.6.0-1-librem5
-rw-r--r-- 1 root root 66096486 Apr  3 05:55 initrd.img-6.6.0-1-librem5

# cat /var/log/apt/history.log

Start-Date: 2024-04-03  05:55:07
Commandline: apt full-upgrade
Requested-By: purism (1000)
Upgrade: linux-image-6.6.0-1-librem5:arm64 (6.6.6pureos2~byz1, 6.6.22pureos1~byz1), linux-image-librem5:arm64 (6.6.6pureos2~byz1, 6.6.22pureos1~byz1)
End-Date: 2024-04-03  05:56:05
...

and the update on April 3 went fine for me too.

Maybe your /boot partition run out of space during the update? Don’t know why the updateer scripts can not check this before.

2 Likes
24

So, the space issue crossed my mind too, because I had the following versions of each file (not just the initrd):

image
image903×102 14.3 KB

And I also had even more versions of dtbs:
image

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?

1 Like
25

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.
3 Likes
26

Here is what they say.

3 Likes
27

Is it fixed yet?

1 Like
28

The repositories have been working for a while now, but no one has updated this specific topic.

2 Likes