Update to upgrade-from-binary steps #156
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The scripts/init/debian/gogs file wasn't executable, which caused some confusion when my init.d script stopped working (it symlinks to this bundled script). Might as well make sure all the shebang files are, in fact, executable.
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During a recent upgrade (https://dl.gogs.io/0.10.18/linux_amd64.tar.gz), my init.d script stopped working because the bundled script didn't have the execute bit set.
I suppose this might be better fixed in the packaging scripts in the main gogs repo, but I didn't feel comfortable editing that. Docs are just docs, right? 😁
I also condensed the three
cp -R ...commands into a single command using brace expansion, which is a standard bash thing.