Performed an update this morning and I’m getting this:
E: Release file for https://repo.pureos.net/pureos/dists/byzantium/InRelease is expired (invalid since 4h 46min 49s). Updates for this repository will not be applied.
7 Likes
It was also reported in: Repos for PureOS Crimson and PureOS Byzantium unavailable. My Librem 5 is affected too.
2 Likes
I found same thing here in California, USA.
2 Likes
Same thing here. Get message: release file is expired. Updates for this repository will not be applied.
2 Likes
In case they’re not actively reading this forum, what would be the proper channel to reach out to PureOS repository maintainers?
Update: Filed OS-issues!355 with a link to this thread to increase our chances that a PureOS package maintainer notices.
4 Likes
Matrix:
1 Like
@JCS ?
My guess is that it expired over the weekend (in whatever timezone is applicable) and noone has got to it yet.
If this were me, I would be doing at least the bare minimum … a cron job that emails someone a warning a few working days in advance of expiry.
4 Likes
I got this 
$ apt update
Get:1 http://repo.pureos.net/pureos byzantium InRelease [9,641 B]
Get:2 http://repo.pureos.net/pureos byzantium-security InRelease [9,650 B]
Get:3 http://repo.pureos.net/pureos byzantium-updates InRelease [9,649 B]
Reading package lists... Done
E: Release file for http://repo.pureos.net/pureos/dists/byzantium/InRelease is expired (invalid since 2d 21h 11min 36s). Updates for this repository will not be applied.
2 Likes
Yeah, that’s why I started this thread. It is kinda worrisome.
3 Likes
This happens fairly regularly in April/October going back to at least 2016.
They’ll get to it eventually and it’ll happen again until they decide that making this not happen is a priority.
And that would be an improvement.
6 Likes
It strikes me that they must be using PureOS themselves, so they must be affected by this as much as us.
2 Likes
Best way to insure a good product is to daily-drive that product in work and home life. If you want a product to do amazing, use it, care about it, then take your own gripes and problems as a personal drive to fix the product… I assume as well that they are using the product that they’ve been developing.
3 Likes
@irvinewade Do we have update yet? Also, I’ve noticed that the Admins group cannot be tagged for visibility…
1 Like
Not everyone checks for updates regularly and/or in a way that will be visible/affected by this.
1 Like
The store depends on apt, so you get the same message there. I just confirmed it.
2 Likes
Sorry, I am just a humble moderator of the forum. I don’t have any administrative access of any type to any Purism system.
I did tag @JCS in the hope that he can actually get the right system administrator on the case.
Otherwise known, rather unappetisingly, as “eating your own dog food” (aka “dogfooding”).
6 Likes
The team knows about this and is working toward a solution. Correct, many (most?) people at Purism do run PureOS. I, for example, use a L5 & LMv2 as my daily-drivers.
10 Likes
Can you maybe release the needed parameters to use the L5 as daily driver?
1 Like