use force when fixing broken deb packages

[reubenmiller]

Signed-off-by: Reuben Miller reuben.miller@softwareag.com

Proposed changes

Use assume yes when fixing debian broken packages (apt-get install -f -y). The build was previously prompting for confirmation which resulted in the CI workflow which prevented the action from executing successfully.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
• Documentation Update (if none of the other choices apply)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist

• I have read the CONTRIBUTING doc
• I have signed the CLA (in all commits with git commit -s)
• I ran cargo fmt as mentioned in CODING_GUIDELINES
• I used cargo clippy as mentioned in CODING_GUIDELINES
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

I tested the command command locally on the device to confirm the functionality.

[rina23q]

Approved