Repository navigation
fix(deb): depend on runtime libgcrypt20 instead of libgcrypt20-dev - #127
Merged
Merged
Conversation
The .deb control declared libgcrypt20-dev, a build-time package, as a runtime dependency. Hosts without the -dev package could not install the .deb (dpkg -i fails on the unmet dependency). The binary only needs the runtime library libgcrypt20. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The .deb control file declares
libgcrypt20-devas a runtime dependency. That is a build-time package: thescanossbinary only needs the runtime librarylibgcrypt20at run time.On hosts without
libgcrypt20-dev,dpkg -iof the package fails on the unmet dependency, even though the binary would run fine.Change
scripts/debpkg/DEBIAN/control:Same fix already applied on the
crc64line (engine 6.0.1-crc64). The RPM spec declares noRequires, so nothing to change there.Intended to land before tagging
v5.4.28.🤖 Generated with Claude Code