Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ubuntu Jammy Updation Giving Error #6174

Closed
siddhpurakaran opened this issue Sep 2, 2022 · 6 comments
Closed

Ubuntu Jammy Updation Giving Error #6174

siddhpurakaran opened this issue Sep 2, 2022 · 6 comments
Labels
bug Something isn't working needs-triage needs to be reviewed

Comments

@siddhpurakaran
Copy link

sudo apt-get update
Ign:5 https://cli.github.com/packages jammy InRelease
Hit:6 http://in.archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:7 https://cli.github.com/packages stable InRelease
Hit:8 http://in.archive.ubuntu.com/ubuntu jammy-security InRelease
Err:9 https://cli.github.com/packages jammy Release
404 Not Found [IP: 185.199.109.153 443]
Reading package lists... Done
E: The repository 'https://cli.github.com/packages jammy 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.

@siddhpurakaran siddhpurakaran added the bug Something isn't working label Sep 2, 2022
@cliAutomation cliAutomation added the needs-triage needs to be reviewed label Sep 2, 2022
@hmahmood24
Copy link

sudo apt update fails on Ubuntu 20.04 LTS (Focal Fossa) as well.

image

Seems like the GPG key used to sign in to this repo has expired as of today (2nd September).

image

Any workaround to this would be highly appreciated.

@hmahmood24
Copy link

sudo apt update fails on Ubuntu 20.04 LTS (Focal Fossa) as well.

image

Seems like the GPG key used to sign in to this repo has expired as of today (2nd September).

image

Any workaround to this would be highly appreciated.

For now, the only workaround I can think of is commenting out the problematic repo in the /etc/apt/sources.list:

image

and the /etc/apt/sources.list.d/github-cli.list files respectively:

image

This should allow the apt to update without any issues.

image

@thomasmerz
Copy link

Seems to be related to #6175 🤔

@rmw
Copy link
Contributor

rmw commented Sep 3, 2022

Please follow along with updates here: #6175 (comment)

@mislav
Copy link
Contributor

mislav commented Sep 4, 2022

Thanks for the reports everyone; closing in favor of the more aptly-titled #6174. 🙇

@mislav mislav closed this as completed Sep 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage needs to be reviewed
Projects
None yet
Development

No branches or pull requests

7 participants
@mislav @rmw @thomasmerz @siddhpurakaran @hmahmood24 @cliAutomation and others