No updates on `latest` since 20250629.1

Bluefin
1

Hi there,

updates have been rolling in like clockwork ever since I rebased to the latest bluefin. That has stopped on Sunday:

Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest
                   Digest: sha256:e2deb514661d1abf08f7f0acc502b4b7a2dba5af167044bb6f3de8d8144e2613
                  Version: latest-42.20250629.1 (2025-06-29T17:25:46Z)

Is the latest – and already a downgrade which I did as I thought maybe I backed myself into a dead end there.

Did I do something wrong to end up in a bad state with my update? As I said: You guys do an amazing job rolling out regular updates, so it probably is something I did.

Best Regards,
Tobias

2

We have had some building issues , as you can see from GitHub

3

Oh, cool, so things will sort themselves out in time. Thanks for the incredible work, it is an amazing distribution that just works for me.

Where can I see that? Github is a pretty big place nowadays :slight_smile:

4

For bluefin its GitHub - ublue-os/bluefin: The next generation Linux workstation, designed for reliability, performance, and sustainability. and then go to the Actions tab where you can see the builds happening

1 Like
5

We’re pausing while Fedora’s datacenter moves happens, we’ll turn everything back on tomorrow probably.

2 Likes
6

A status page for possible service problems on build and updates would be immensely helpful, to be honest. Nothing automatic, just something that says No known service problems or Builds on Bluefin paused for the following reason, plus the date that it was posted. Again, it does not need to be fancy at all, but it’s much better than a user posting here or receiving the answer check the actions on GitHub, when most users have no idea what GitHub even is. Something simple based on Kuma, like this example status.plex.tv, is more than sufficient in my opinion.

7

The build failures are transparent to you, it doesn’t matter to you unless it’s a long time. If we had to do an update every time a build failed we would spend all of our time posting updates.

If you care about build failures then learn to use Github, that’s what I do. :smiley:

2 Likes
8

Sorry I wasn’t clear at all in my request. My fault. Obviously, a build failure does not warrant a status page. What I meant in my recommendation was simply a page that states whether there is a service problem or not. The page would typically show a “systems fully operational” message in green 99.99% of the time, but in the rare instance of a widespread issue, for example, with the update service, such a page would provide a simple and clear message to users that the error they are seeing in their terminal when they are running the system update shortcut is expected and that they simply need to be patient until the service error is resolved.

Anyway, just an idea. Most likely bad :sweat_smile:

9

https://www.githubstatus.com is the closest we have lol!!!

EDIT: More seriously the datacenter move is an outlier of a circumstance, they’re physically moving Fedora infra from one datacenter to another, it’s a multi day effort.

2 Likes