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

Fix issue with docker-rootless shimming script (#18690) #18699

Merged
merged 1 commit into from
Feb 10, 2022

Conversation

zeripath
Copy link
Contributor

Backport #18690

There is a problem with the current shimming script in that it will double quote the
provided GITEA_APP_INI due to a mistake in the bash. Here we change this to use a bash array.

Fix https://gitea.com/gitea/helm-chart/issues/287

Signed-off-by: Andrew Thornton art27@cantab.net

Backport go-gitea#18690

There is a problem with the current shimming script in that it will double quote the
provided GITEA_APP_INI due to a mistake in the bash. Here we change this to use a bash array.

Fix https://gitea.com/gitea/helm-chart/issues/287

Signed-off-by: Andrew Thornton <art27@cantab.net>
@zeripath zeripath added this to the 1.16.2 milestone Feb 10, 2022
@GiteaBot GiteaBot added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Feb 10, 2022
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Feb 10, 2022
@lunny lunny merged commit ce69882 into go-gitea:release/v1.16 Feb 10, 2022
@zeripath zeripath deleted the backport-18690-v1.16 branch February 10, 2022 18:39
@PrivatePuffin
Copy link

@lunny Can you please tag the 1.16.2 release.

@lunny
Copy link
Member

lunny commented Feb 11, 2022

@lunny Can you please tag the 1.16.2 release.

There are still some other bugs need to be merged into 1.16.2. I think it could be expected in next week. You can also switch to 1.16-dev to follow the 1.16 branch if you don't want to wait.

@PrivatePuffin
Copy link

@lunny Can you please tag the 1.16.2 release.

There are still some other bugs need to be merged into 1.16.2. I think it could be expected in next week. You can also switch to 1.16-dev to follow the 1.16 branch if you don't want to wait.

As a downstream the number of bugs in 1.16 are kinda a problem.
And no, we cannot decide for our users to use dev builds.

@go-gitea go-gitea locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants