-
Notifications
You must be signed in to change notification settings - Fork 87
Fix: Add missing build dependencies #1035
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
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Snapshot WarningsEnsure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice. Scanned FilesNone |
Scanning the following files:
Scan: '.github/build-dependencies.list'Nothing detected in .github/build-dependencies.list Scan: '.github/runtime-dependencies.oldstable.list'Nothing detected in .github/runtime-dependencies.oldstable.list Scan: '.github/runtime-dependencies.stable.list'Nothing detected in .github/runtime-dependencies.stable.list Scan: '.github/runtime-dependencies.testing.list'Nothing detected in .github/runtime-dependencies.testing.list |
bjoernricks
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets just get the debian testing container image build running again
Use exact package name for `libgcrypt-dev` package which is `libgcrypt20-dev`. `libgcrypt20-dev` just *Provides* `libgcrypt-dev`. Also require libcrypt1 because we link against it. By default it is already installed because `passwd` depends on it. But we should ensure that it is still installed if something in Debian will change in future.
What
libcrypt-dev is added to the list of build dependencies.
Why
libcrypt-dev is required to build gvm-libs.