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

apt repository does not have a Release file for Ubuntu 24.04 LTS #7364

Open
maxkratz opened this issue May 18, 2024 · 2 comments
Open

apt repository does not have a Release file for Ubuntu 24.04 LTS #7364

maxkratz opened this issue May 18, 2024 · 2 comments

Comments

@maxkratz
Copy link

Currently, the apt repository does not contain a Release file for Ubuntu 24.04 LTS (which is the current LTS version). Therefore, EdgeDB can not be installed on Ubuntu 24.04 LTS using apt despite the documentation on

explicitly mention "Ubuntu LTS".


  • EdgeDB Version: ?
  • EdgeDB CLI Version: ?
  • OS Version: Ubuntu 24.04 LTS (Noble)

Steps to Reproduce:

  1. Follow the installation steps on the doc pages given above.
  2. Try to apt-get update
  3. See error:
[...]
root@c6c59e84df24:/# apt update
Hit:1 http://security.ubuntu.com/ubuntu noble-security InRelease
Hit:2 http://archive.ubuntu.com/ubuntu noble InRelease
Hit:3 http://archive.ubuntu.com/ubuntu noble-updates InRelease
Ign:4 https://packages.edgedb.com/apt noble InRelease
Hit:5 http://archive.ubuntu.com/ubuntu noble-backports InRelease
Err:6 https://packages.edgedb.com/apt noble Release
  404  Not Found [IP: 18.66.102.5 443]
Reading package lists... Done
E: The repository 'https://packages.edgedb.com/apt noble 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.
@KaelWD
Copy link

KaelWD commented May 20, 2024

Workaround:

maxkratz added a commit to maxkratz/edgedb-vm that referenced this issue May 20, 2024
@maxkratz
Copy link
Author

Workaround:

Thank you, this workaround worked for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants