-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
modules/portage: fix usage with withbdeps: false #6456
Conversation
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.
Thanks for your contribution! I've added a first comment.
Using ``withbdeps: false`` was causing the underlying emerge command to fail due to not passing an argument to the ``--with-bdeps`` flag. Fix by updating the logic for generating the emerge command arguments to ensure that ``withbdeps: false`` results in a passing an ``n`` argument with the ``--with-bdeps`` emerge flag.
LGTM |
Backport to stable-6: 💚 backport PR created✅ Backport PR branch: Backported as #6480 🤖 @patchback |
Using ``withbdeps: false`` was causing the underlying emerge command to fail due to not passing an argument to the ``--with-bdeps`` flag. Fix by updating the logic for generating the emerge command arguments to ensure that ``withbdeps: false`` results in a passing an ``n`` argument with the ``--with-bdeps`` emerge flag. (cherry picked from commit fab717b)
@living180 thanks for your contribution! |
…h withbdeps: false (#6480) modules/portage: fix usage with withbdeps: false (#6456) Using ``withbdeps: false`` was causing the underlying emerge command to fail due to not passing an argument to the ``--with-bdeps`` flag. Fix by updating the logic for generating the emerge command arguments to ensure that ``withbdeps: false`` results in a passing an ``n`` argument with the ``--with-bdeps`` emerge flag. (cherry picked from commit fab717b) Co-authored-by: Daniel Harding <[email protected]>
SUMMARY
Using
withbdeps: false
was causing the underlying emerge command to fail due to not passing an argument to the--with-bdeps
flag. Fix by updating the logic for generating the emerge command arguments to ensure thatwithbdeps: false
results in a passing ann
argument with the--with-bdeps
emerge flag.Fixes #6451.
ISSUE TYPE
COMPONENT NAME
portage