{"is":"issue","title":"Signing outage","body":"\u003cp\u003eAn issue with hardware security key is currently preventing builds from\nbeing signed with our GPG key. This affects both direct uploads and\nbuilds performed on Flathub infra. Since no builds can be signed thus\npublished, the build service including test builds are also\ndisrupted. \n  \u003cspan class=\"faded\"\u003e(13:56 UTC — Feb 17)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003eWe are in contact with the data center staff to investigate the\nissue physically. \n  \u003cspan class=\"faded\"\u003e(17:49 UTC — Feb 19)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003eData centre staff attempted reseating the signing key across available\nUSB ports without success. We are now arranging delivery and\ninstallation of a replacement key. \n  \u003cspan class=\"faded\"\u003e(16:46 UTC — Feb 20)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003eWe successfully managed to install the new Yubikey. \n  \u003cspan class=\"faded\"\u003e(14:04 UTC — Feb 23)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eInformation\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eWe will soon restart all affected official builds in batches and they\nshould be published within a couple of hours. Affected direct uploaders\nwill be informed to restart builds from their end. Once this process\nis complete, some services which were disabled (to reduce impact)\nwill be re-enabled one by one.\u003c/p\u003e\n\u003cp\u003eOnce the test build service is available, any affected test builds on\npull requests will need to be manually restarted by commenting\n\u0026ldquo;bot, build\u0026rdquo; by the respective maintainer or contributor.\u003c/p\u003e\n\u003cp\u003ePlease allow us some time to finish the entire process outlined above.\nPublishing may take longer than usual due the large number of builds\nin the queue. Please open an issue on \u003ca href=\"https://github.com/flathub/flathub/issues\"\u003eGitHub\u003c/a\u003e\nfor any further query about missing or unpublished builds. Further\nupdates will be posted in the statuspage.\u003c/p\u003e\n\u003cp\u003eAll affected builds were successfully restarted and they finished building. \n  \u003cspan class=\"faded\"\u003e(16:40 UTC — Feb 23)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003eThe repository server is still experiencing some issues. \n  \u003cspan class=\"faded\"\u003e(17:30 UTC — Feb 23)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003eThe incident should be resolved now and services are being restarted. \n  \u003cspan class=\"faded\"\u003e(18:50 UTC — Feb 23)\u003c/span\u003e\n\n\u003c/p\u003e\n","createdAt":"2026-02-17 13:56:00 +0000 UTC","lastMod":"2026-02-24 00:35:36 +0530 +0530","permalink":"https://status.openpak.org/issues/2026-02-17-publish/","severity":"disrupted","resolved":true,"informational":false,"resolvedAt":"2026-02-23 18:50:00","affected":["Build service","Main repository server"],"filename":"2026-02-17-publish.md"}