Update Linux development dependencies#21672
Closed
Seekers2001 wants to merge 1 commit into
Closed
Conversation
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.
Description
Add
libffi-devandlibyaml-devto the Linux development dependency command. These packages are needed when building the Ruby dependencies used by a fresh Metasploit development environment.Related Issue: Fixes #21669
Breaking Changes
None
Verification Steps
docs/metasploit-framework.wiki/dev/Setting-Up-a-Metasploit-Development-Environment.md.libffi-devandlibyaml-devbefore the laterbundle installstep.Test Evidence
git diff --checkpasses.tools/dev/msftidy_docs.rbwas also run, but it is scoped to module documentation and rejects this pre-existing wiki guide as "Doc missing module"; its module-section warnings are not applicable to this file.Environment
AI Usage Disclosure
OpenAI Codex (GPT-5) was used to inspect the issue and repository guidance, make the one-line documentation edit, and run the checks listed above.
Pre-Submission Checklist
documentation/modules(new modules only)lib/changes)