-
Notifications
You must be signed in to change notification settings - Fork 2k
Replace obsolete ENV VAR VALUE with ENV VAR=VALUE #2254
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
base: main
Are you sure you want to change the base?
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.
Need to fix update.sh & functions.sh
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
Why should this one depend on #2258?
|
Because they touch the same line in update.sh. |
That's something should be prevented. I don't want to mix different topic in the same pull request.
|
I agree. So which one of them do you want to accept first? You can either merge the other one and then I'll rebase this one, or I can swap them. |
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.
Please remove unrelated commit changes that are not relevant to the topic.
Maybe this one as it was sent earlier. |
Done |
Rebased. Please review. |
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.
Needs another rebase, but LGTM 👍
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.
As @tianon mentions in #2252 (comment), this advice might not actually be great
Fixes these warnings: - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
Rebased. As for the warnings, whether we like them or not - they currently appear on every build, and it is annoying. It doesn't look like it's going to change anytime soon. So we can either ignore them and hope that upstream docker will remove them, or change to the new syntax. |
Description
Fixes these warnings:
Testing Details
Build passed.
Types of changes
Checklist