We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
An InRelease file is just a Release file that's signed inline. If a repo has a Release and Release.gpg file, you can just ignore the InRelease file.
InRelease
Release
Release.gpg
I've found that apt-s3 fails when the InRelease file is missing: zendesk/apt-s3#17
apt-s3
I could imagine that other apt related tools fail without the InRelease file... The old repositories.timber.io repo included this InRelease file.
In the meantime, I'm going to try to fix apt-s3 to not fail when the InRelease file is missing.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
An
InRelease
file is just aRelease
file that's signed inline. If a repo has aRelease
andRelease.gpg
file, you can just ignore theInRelease
file.I've found that
apt-s3
fails when theInRelease
file is missing: zendesk/apt-s3#17I could imagine that other apt related tools fail without the
InRelease
file... The old repositories.timber.io repo included thisInRelease
file.In the meantime, I'm going to try to fix
apt-s3
to not fail when theInRelease
file is missing.The text was updated successfully, but these errors were encountered: