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

推荐订阅源

奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
大猫的无限游戏
大猫的无限游戏
博客园 - 聂微东
Jina AI
Jina AI
The Cloudflare Blog
V
Visual Studio Blog
博客园_首页
量子位
酷 壳 – CoolShell
酷 壳 – CoolShell
博客园 - 【当耐特】
爱范儿
爱范儿
博客园 - 三生石上(FineUI控件)
小众软件
小众软件
博客园 - 司徒正美
阮一峰的网络日志
阮一峰的网络日志
Last Week in AI
Last Week in AI
V
V2EX
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - 叶小钗
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
WordPress大学
WordPress大学
宝玉的分享
宝玉的分享
T
Tailwind CSS Blog
博客园 - Franky

Flathub Status

GitHub is experiencing issues | 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)