惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

大猫的无限游戏
大猫的无限游戏
MyScale Blog
MyScale Blog
雷峰网
雷峰网
量子位
小众软件
小众软件
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 叶小钗
T
Tailwind CSS Blog
月光博客
月光博客
博客园 - 【当耐特】
博客园_首页
罗磊的独立博客
博客园 - 三生石上(FineUI控件)
IT之家
IT之家
爱范儿
爱范儿
阮一峰的网络日志
阮一峰的网络日志
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
WordPress大学
WordPress大学
The Cloudflare Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
S
SegmentFault 最新的问题
人人都是产品经理
人人都是产品经理
V
V2EX
酷 壳 – CoolShell
酷 壳 – CoolShell

Flathub Status

GitHub is experiencing issues | Flathub Status Website is down | Flathub Status Multiple services down | Flathub Status Infrastructure provider outage | Flathub Status Build status updates failing | Flathub Status Publishing delay due to delta regeneration Signing outage | Flathub Status CDN cache invalidation issue | Flathub Status CDN cache invalidation issue | Flathub Status Website facing intermittent disruptions | Flathub Status Publish outage | Flathub Status Build service outage | Flathub Status Hosting provider planned maintenance | Flathub Status Blocked publishing due to ongoing repository pruning Frontend service is down | Flathub Status
appstream2 branch referencing stale commit
2026-03-25 · via Flathub Status

March 24, 2026 at 23:55 UTC

CDN

Resolved after 2h 5m March 25, 2026 at 02:00 UTC


A mismatch between the appstream2 branch and delta indexes caused local Flatpak clients to fail to update appstream data. The issue is resolved now after regenerating both the branch and the indexes.

If you are still experiencing issues, please try the steps below to clear the local copy of the appstream2 branch. (01:33 UTC — Mar 25)

# For system-wide installation 
sudo ostree --repo=/var/lib/flatpak/repo refs --delete flathub:appstream2/x86_64

# For user installation
ostree --repo=$HOME/.local/share/flatpak/repo refs --delete flathub:appstream2/x86_64

# Update the appstream data
flatpak update --appstream

Additionally, some client experienced timeouts when fetching delta indexes that were removed from the server. This was caused by the CDN not caching 404 responses, resulting in requests queuing up behind nginx’s cache lock. A fix was deployed to cache 404 responses, allowing clients to gracefully fall back to full downloads. (02:08 UTC — Mar 25)