Skip to content
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.

Sign up for GitHub

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

Jump to bottom

--force-yes is deprecated #16

Closed
csuhta opened this issue May 24, 2017 · 3 comments
Closed

--force-yes is deprecated #16

csuhta opened this issue May 24, 2017 · 3 comments

Comments

@csuhta
Copy link

csuhta commented May 24, 2017

Getting this warning lately when deploying with this buildpack. Ex:

-----> Fetching .debs for libjpeg-progs
       Reading package lists...
       Building dependency tree...
       [… snip …]
       Download complete and in download only mode
W: --force-yes is deprecated, use one of the options starting with --allow instead.
@zunda
Copy link
Member

zunda commented May 27, 2017

I've just tested and found that the --allow-* options are not available on cedar-14 stack. We have to wait for end of life of cedar-14 before we can replace --force-yes with --allow-* options.

@sobrinho
Copy link
Contributor

Why are we using --force-yes? Can't it be replaced by --assume-yes?

Ref: https://forums.solydxk.com/viewtopic.php?t=6148

@surfaceowl
Copy link

@zunda --the cedar-14 stack will EOL in April 2019

.... are the ``--allow-*options available on thecedar-16 stack`?

@duanehutchins duanehutchins mentioned this issue Oct 10, 2018
Open
@amiel amiel mentioned this issue Oct 26, 2018
Open
@edmorley edmorley mentioned this issue Jun 10, 2019
Merged
EtienneM pushed a commit to Scalingo/apt-buildpack that referenced this issue Dec 16, 2022
@imirkin @EtienneM
avoid force-yes with newer version of apt-get (heroku#51)
ad5df5a 
force-yes was deprecated with 1.1, and split up into three new options.
Keep the same behavior by enabling all 3 options when a newer version is
detected.

This should fix errors at install time, which are tripping up the
current tests.

Fixes heroku#16.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@sobrinho @zunda @csuhta @surfaceowl