search

warpdotdev / Warp

Warp is a modern, Rust-based terminal with AI built in so you and your team can build great software, faster.
https://warp.dev
Other
21.24k stars 367 forks source link

Unable to update to the latest version on Linux due to NO_PUBKEY #5384

Open danorr opened 3 days ago

danorr commented 3 days ago

Dupe Check

Describe the bug

When I open the app I'm told to update immediately. When I do that, the update fails

To reproduce

  1. sudo apt update && sudo apt install warp-terminal && warp_finish_update vcZv02n
  2. await response

Expected behavior

Expected the app to updated.

Screenshots

Output from above command

Hit:1 http://nz.archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://nz.archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://nz.archive.ubuntu.com/ubuntu focal-backports InRelease
Get:6 https://cli.github.com/packages focal InRelease [3,915 B]
Hit:7 https://packages.microsoft.com/repos/edge stable InRelease
Hit:8 https://packages.microsoft.com/ubuntu/20.04/prod focal InRelease
Get:9 https://cli.github.com/packages stable InRelease [3,917 B]
Ign:4 https://repo.vivaldi.com/stable/deb stable InRelease
Get:11 http://dl.google.com/linux/chrome/deb stable InRelease [1,825 B]
Hit:10 https://repo.vivaldi.com/stable/deb stable Release
Ign:12 https://releases.warp.dev/linux/deb stable InRelease
Hit:13 http://security.ubuntu.com/ubuntu focal-security InRelease
Hit:15 http://archive.canonical.com/ubuntu focal InRelease
Ign:16 http://ppa.launchpad.net/docky-core/stable/ubuntu focal InRelease
Err:6 https://cli.github.com/packages focal InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059
Hit:17 https://releases.warp.dev/linux/deb stable Release
Ign:18 https://repo.fortinet.com/repo/6.4/ubuntu stable InRelease
Hit:19 http://ppa.launchpad.net/ricotz/docky/ubuntu focal InRelease
Err:20 https://repo.fortinet.com/repo/6.4/ubuntu stable Release
  404  Not Found [IP: 208.91.114.61 443]
Hit:21 https://packages.microsoft.com/repos/ms-teams stable InRelease
Hit:22 https://esm.ubuntu.com/apps/ubuntu focal-apps-security InRelease
Err:23 http://ppa.launchpad.net/docky-core/stable/ubuntu focal Release
  404  Not Found [IP: 185.125.190.80 80]
Hit:5 https://packages.microsoft.com/repos/code stable InRelease
Err:9 https://cli.github.com/packages stable InRelease
  The following signatures were invalid: EXPKEYSIG 23F3D4EA75716059 GitHub CLI <opensource+cli@github.com>
Hit:14 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease
Hit:24 https://esm.ubuntu.com/apps/ubuntu focal-apps-updates InRelease
Err:11 http://dl.google.com/linux/chrome/deb stable InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E88979FB9B30ACF2
Hit:26 https://esm.ubuntu.com/infra/ubuntu focal-infra-security InRelease
Hit:28 https://esm.ubuntu.com/infra/ubuntu focal-infra-updates InRelease
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://cli.github.com/packages focal InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059
E: The repository 'https://repo.fortinet.com/repo/6.4/ubuntu stable Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://ppa.launchpad.net/docky-core/stable/ubuntu focal Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://cli.github.com/packages stable InRelease: The following signatures were invalid: EXPKEYSIG 23F3D4EA75716059 GitHub CLI <opensource+cli@github.com>
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.google.com/linux/chrome/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E88979FB9B30ACF2

Operating system

MacOS

Operating system and version

Ubuntu 20.04.6 LTS

Shell Version

zsh 5.8 (x86_64-ubuntu-linux-gnu)

Current Warp version

v0.2024.08.13.08.02.stable_03

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

No

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

vorporeal commented 2 days ago

@danorr Looks like some of your other package repositories have configuration issues (cannot fetch the package signature verification key), meaning apt can't download an updated package list from the Warp package repository, so we can't actually fetch/install the latest version.

Unfortunately, apt doesn't provide any way for us to download the updated package list for only the warp repository, so any configuration issues with other repositories will break the update flow for Warp (and, FWIW, prevent you from updating any other packages on your system).

I recommend you fix the configuration for the repositories that are producing NO_PUBKEY errors; that should fix Warp's update flow.