-
Notifications
You must be signed in to change notification settings - Fork 461
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
W: --force-yes is deprecated, use one of the options starting with --allow instead. #1130
Comments
The only place I see
I think you want to file this bug against puppet itself, not this apt module: https://github.com/search?q=repo%3Apuppetlabs%2Fpuppet%20--force-yes&type=code |
Ok, thank you. Unfortunately, I cannot file an issue there as Issues are disabled for that GitHub repo and all links to the Jira Issue tracker are dead too... |
Thanks @XSpielinbox for raising and sorry for inconvenience, looks the README.md file still points to the old JIRA URL. I have created tracker ticket internally to update to new JIRA ticket. Also will review the module where ever there is |
Closing this as we have fixed in repo, the same will review for other modules and do needful, Thanks Team!! |
Thank you @Ramesh7! |
Describe the Bug
Puppet calls
apt-get
with the--force-yes
option. This option has been deprecated and replaced by--allow-unauthenticated
,--allow-downgrades
,--allow-remove-essential
and--allow-change-held-packages
in apt 1.1 in 2015.Expected Behavior
The Puppet apt module does not use
--force-yes
.Steps to Reproduce
Steps to reproduce the behavior:
puppet agent -t
on a node that then has to downgrade a package.Environment
Additional Context
For enhanced backwards compatibility one might have an option that users that really need it, can explicitly enable to use the old
--force-yes
option.The text was updated successfully, but these errors were encountered: