Flatpak Update Error: Key expired

[Itay080]

Current Behavior

Hi!
Looks like the key for the flatpak has expired so it can't be installed

Expected Behavior

Keys should be renewed so the flatpak can be installed

Desktop

GNOME Shell

Other Desktop

No response

Operating System

Debian 12

Installed from

Nightly Flatpak

Version

nightly

Devices

No response

Plugins

No response

Logs

F: Loading https://valent.andyholmes.ca/repo/summaries/69eb8f9e3b62263580f3ad0a506896a991323e181684c436a6e3cc8cc7f75ebe.idx.sig using curl
F: Received 142 bytes
F: Failed to download optional summary index: Signature made Mon 14 Oct 2024 03:58:53 using EdDSA key ID C1C2E37EA92DAB83
BAD signature from " <[email protected]>"
Key expired Thu 17 Oct 2024 06:33:41

Screenshots

No response

[andyholmes]

Thanks for reporting, I guess I forgot the passkey which is kind of a bummer. I'll see if I can extend the expiry, but otherwise...well I've never done this before with a Flatpak repo :)

[andyholmes]

Hi, the repository should be fixed now, however you may need to remove/add it again:

flatpak remote-delete valent-origin
flatpak install https://valent.andyholmes.ca/valent.flatpakref

(or just click https://valent.andyholmes.ca/valent.flatpakref after removing the remote)

[Lehmanator]

Looks like aarch64 builds are failing after a deps update. libical failed to build.

https://github.com/andyholmes/valent/actions/runs/12959880143/job/36154266825

Trying to install yields the error:

$ flatpak remote-delete valent-origin
$ flatpak install https://valent.andyholmes.ca/valent.flatpakref
error: No such ref 'app/ca.andyholmes.Valent/aarch64/master' in remote valent-origin

Since you also author the GitHub Action for building and deploying flatpaks, figured I'd let you know in case this is a bug where failed builds (or builds failing for one arch but succeeding for another) causes the latest artifacts to be replaced for all architectures when a build only succeeds for one arch.

[andyholmes]

Huh, yeah that is not...intended. I noticed the aarch64 job failed, so I gave it a bump it looks like a compiler segfault on aarch64 (yay 😉).

That's definitely unfortunate that the aarch64 build disappears in that case, I've opened andyholmes/flatter#124 to track it. Thanks for the heads up, I haven't been updating Valent on my phone so I wouldn't have noticed!