-
Notifications
You must be signed in to change notification settings - Fork 143
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
[BUG] setup.sh: E: The repository ... does not have a Release file. #290
Comments
|
Thanks for looking into this! Can you explain how it works? I'm admittedly not well versed in the differences between apt-get and apt. My understanding is apt-get update will fetch all the most recent versions from the repositories. If that is removed, how does apt know that it is fetching the latest version? |
It doesn't, you're right. Actually I think the error handling might've been the true culprit here. ideally when running setup.sh it shouldn't exit out just because some unrelated package doesn't have a release file |
Error condition will output to console, but script will continue to install dependencies.
It is intentional that the script exits if apt-get update doesn't work. I think that if a user is using an invalid repository, the user should fix that issue. Otherwise, the setup script cannot guarantee that the packages it installs will be up to date and compatible. |
In my case the error actually has nothing to do with the other pikaraoke packages and continuing the setup leads to no problems. Perhaps it could be modified to check for specific error codes that would cause problems with the installation? |
No longer relevant, pikaraoke is installed via pip |
To Reproduce
Steps to reproduce the behavior:
-The user must have installed at least one package from a repository that does not have a release file (in this case cli.github.com/packages bookworm release)
-run setup.sh
Platform :
Error is the same whether you run it as user or root.
The text was updated successfully, but these errors were encountered: