<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><link rel="alternate" type="text/html" href="https://status.openpak.org/"/><title>Main Repository Server on Openpak Status</title><link>https://status.openpak.org/affected/main-repository-server/</link><description>Incident history</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2026-03-25T00:58:00+00:00</lastBuildDate><updated>2026-03-25T00:58:00+00:00</updated><atom:link href="https://status.openpak.org/affected/main-repository-server/index.xml" rel="self" type="application/rss+xml"/><item><title>[Resolved] Publishing delay due to delta regeneration</title><link>https://status.openpak.org/issues/2026-03-25-publish/</link><pubDate>Wed, 25 Mar 2026 00:58:00 +0000</pubDate><guid>https://status.openpak.org/issues/2026-03-25-publish/</guid><category>2026-03-25 04:26:13</category><description>&lt;p>We are in the process of regenerating deltas for the current apps. The process
takes an exclusive lock of the underlying ostree repository, preventing new
builds from being published. If you have an urgent update to release, please
contact us on our Matrix channel.
&lt;span class="faded">(02:14 UTC — Mar 25)&lt;/span>
&lt;/p></description><content type="html">&lt;p>We are in the process of regenerating deltas for the current apps. The process
takes an exclusive lock of the underlying ostree repository, preventing new
builds from being published. If you have an urgent update to release, please
contact us on our Matrix channel.
&lt;span class="faded">(02:14 UTC — Mar 25)&lt;/span>
&lt;/p></content></item><item><title>[Resolved] Signing outage</title><link>https://status.openpak.org/issues/2026-02-17-publish/</link><pubDate>Tue, 17 Feb 2026 13:56:00 +0000</pubDate><guid>https://status.openpak.org/issues/2026-02-17-publish/</guid><category>2026-02-23 18:50:00</category><description>&lt;p>An issue with hardware security key is currently preventing builds from
being signed with our GPG key. This affects both direct uploads and
builds performed on Flathub infra. Since no builds can be signed thus
published, the build service including test builds are also
disrupted.
&lt;span class="faded">(13:56 UTC — Feb 17)&lt;/span>
&lt;/p>
&lt;p>We are in contact with the data center staff to investigate the
issue physically.
&lt;span class="faded">(17:49 UTC — Feb 19)&lt;/span>
&lt;/p>
&lt;p>Data centre staff attempted reseating the signing key across available
USB ports without success. We are now arranging delivery and
installation of a replacement key.
&lt;span class="faded">(16:46 UTC — Feb 20)&lt;/span>
&lt;/p></description><content type="html">&lt;p>An issue with hardware security key is currently preventing builds from
being signed with our GPG key. This affects both direct uploads and
builds performed on Flathub infra. Since no builds can be signed thus
published, the build service including test builds are also
disrupted.
&lt;span class="faded">(13:56 UTC — Feb 17)&lt;/span>
&lt;/p>
&lt;p>We are in contact with the data center staff to investigate the
issue physically.
&lt;span class="faded">(17:49 UTC — Feb 19)&lt;/span>
&lt;/p>
&lt;p>Data centre staff attempted reseating the signing key across available
USB ports without success. We are now arranging delivery and
installation of a replacement key.
&lt;span class="faded">(16:46 UTC — Feb 20)&lt;/span>
&lt;/p>
&lt;p>We successfully managed to install the new Yubikey.
&lt;span class="faded">(14:04 UTC — Feb 23)&lt;/span>
&lt;/p>
&lt;p>&lt;strong>Information&lt;/strong>&lt;/p>
&lt;p>We will soon restart all affected official builds in batches and they
should be published within a couple of hours. Affected direct uploaders
will be informed to restart builds from their end. Once this process
is complete, some services which were disabled (to reduce impact)
will be re-enabled one by one.&lt;/p>
&lt;p>Once the test build service is available, any affected test builds on
pull requests will need to be manually restarted by commenting
&amp;ldquo;bot, build&amp;rdquo; by the respective maintainer or contributor.&lt;/p>
&lt;p>Please allow us some time to finish the entire process outlined above.
Publishing may take longer than usual due the large number of builds
in the queue. Please open an issue on &lt;a href="https://github.com/flathub/flathub/issues">GitHub&lt;/a>
for any further query about missing or unpublished builds. Further
updates will be posted in the statuspage.&lt;/p>
&lt;p>All affected builds were successfully restarted and they finished building.
&lt;span class="faded">(16:40 UTC — Feb 23)&lt;/span>
&lt;/p>
&lt;p>The repository server is still experiencing some issues.
&lt;span class="faded">(17:30 UTC — Feb 23)&lt;/span>
&lt;/p>
&lt;p>The incident should be resolved now and services are being restarted.
&lt;span class="faded">(18:50 UTC — Feb 23)&lt;/span>
&lt;/p></content></item><item><title>[Resolved] Publish outage</title><link>https://status.openpak.org/issues/2025-05-28-publish-broken/</link><pubDate>Tue, 27 May 2025 11:47:00 +0000</pubDate><guid>https://status.openpak.org/issues/2025-05-28-publish-broken/</guid><category>2025-05-28 10:04:00</category><description>&lt;p>An ongoing outage is currently preventing builds from being published
and is causing test build links to return 404 errors. This issue
affects both direct uploads and all builds performed on Flathub infra.&lt;/p>
&lt;p>We are trying to resolve it.
&lt;span class="faded">(11:47 UTC — May 27)&lt;/span>
&lt;/p>
&lt;p>This is resolved now.
&lt;span class="faded">(10:04 UTC — May 28)&lt;/span>
&lt;/p></description><content type="html">&lt;p>An ongoing outage is currently preventing builds from being published
and is causing test build links to return 404 errors. This issue
affects both direct uploads and all builds performed on Flathub infra.&lt;/p>
&lt;p>We are trying to resolve it.
&lt;span class="faded">(11:47 UTC — May 27)&lt;/span>
&lt;/p>
&lt;p>This is resolved now.
&lt;span class="faded">(10:04 UTC — May 28)&lt;/span>
&lt;/p></content></item><item><title>[Resolved] Build service outage</title><link>https://status.openpak.org/issues/2024-11-03-repo-exp/</link><pubDate>Sun, 03 Nov 2024 19:05:00 +0000</pubDate><guid>https://status.openpak.org/issues/2024-11-03-repo-exp/</guid><category>2024-11-04 19:39:00</category><description>&lt;p>There is an ongoing outage that is causing builds to fail at the commit
stage. This affects all builds done through Flathub buildbot and may
affect direct uploads as well.&lt;/p>
&lt;p>We are trying to resolve it.
&lt;span class="faded">(19:05 UTC — Nov 3)&lt;/span>
&lt;/p>
&lt;p>&lt;strong>Resolved:&lt;/strong> This should be resolved now
&lt;span class="faded">(19:39 UTC — Nov 4)&lt;/span>
&lt;/p></description><content type="html">&lt;p>There is an ongoing outage that is causing builds to fail at the commit
stage. This affects all builds done through Flathub buildbot and may
affect direct uploads as well.&lt;/p>
&lt;p>We are trying to resolve it.
&lt;span class="faded">(19:05 UTC — Nov 3)&lt;/span>
&lt;/p>
&lt;p>&lt;strong>Resolved:&lt;/strong> This should be resolved now
&lt;span class="faded">(19:39 UTC — Nov 4)&lt;/span>
&lt;/p></content></item><item><title>[Resolved] Blocked publishing due to ongoing repository pruning</title><link>https://status.openpak.org/issues/2024-05-14-repo-prune/</link><pubDate>Tue, 14 May 2024 10:00:00 +0000</pubDate><guid>https://status.openpak.org/issues/2024-05-14-repo-prune/</guid><category>2024-05-15 17:50:00</category><description>&lt;p>&lt;strong>Resolved&lt;/strong>: The pruning has completed, freeing almost 7TB of disk space. Affected builds have been restarted in Buildbot.
&lt;span class="faded">(17:50 UTC — May 15)&lt;/span>
&lt;/p>
&lt;p>The pruning process is still ongoing. It may take about 12 hours more.
&lt;span class="faded">(05:30 UTC — May 14)&lt;/span>
&lt;/p>
&lt;p>We are in the process of pruning the ostree repository from old builds. The
process requires an exclusive lock of the repository, meaning that publishing
is not going to be possible until it finishes. We will manually publish the
outstanding builds afterwards.
&lt;span class="faded">(19:00 UTC — May 14)&lt;/span>
&lt;/p></description><content type="html">&lt;p>&lt;strong>Resolved&lt;/strong>: The pruning has completed, freeing almost 7TB of disk space. Affected builds have been restarted in Buildbot.
&lt;span class="faded">(17:50 UTC — May 15)&lt;/span>
&lt;/p>
&lt;p>The pruning process is still ongoing. It may take about 12 hours more.
&lt;span class="faded">(05:30 UTC — May 14)&lt;/span>
&lt;/p>
&lt;p>We are in the process of pruning the ostree repository from old builds. The
process requires an exclusive lock of the repository, meaning that publishing
is not going to be possible until it finishes. We will manually publish the
outstanding builds afterwards.
&lt;span class="faded">(19:00 UTC — May 14)&lt;/span>
&lt;/p></content></item></channel></rss>