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.

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

avoid force-yes with newer version of apt-get #51

Merged
merged 1 commit into from
Sep 6, 2019

Conversation

imirkin
Copy link
Contributor

@imirkin imirkin commented Aug 31, 2019

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.

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.
@imirkin
Copy link
Contributor Author

imirkin commented Aug 31, 2019

Or maybe it's OK to just always use the new options since Heroku currently supports just the 16.04 and 18.04-based releases, which have apt 1.2 and 1.6 respectively. Happy to redo it the simpler way too.

(Actually nevermind - Cedar-14 is EOL but still buildable, and that has 1.0.)

Copy link
Member

@edmorley edmorley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me - thank you for the PR!

@edmorley edmorley merged commit cae2549 into heroku:master Sep 6, 2019
@edmorley
Copy link
Member

edmorley commented Sep 9, 2019

And published to the buildpack registry:

$ h buildpacks:versions heroku-community/apt
Version  Released At               Status
───────  ────────────────────────  ─────────
3        2019-09-09T07:26:55.242Z  published

EtienneM pushed a commit to Scalingo/apt-buildpack that referenced this pull request Dec 16, 2022
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.
taschik pushed a commit to obefitness/heroku-buildpack-apt that referenced this pull request Oct 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants