github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-09 12:46:42 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

After update to version 1.20.0 Gitea refused to start #11283

New Issue
Closed
opened 2025-11-02 09:33:19 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2025-11-02 09:33:19 -06:00
Owner
Copy Link

Originally created by @veita on GitHub (Jul 19, 2023).

Description

  • Update from Gitea 1.19.4 to 1.20.0
  • Gitea deployed as a Systemd service on Debian 12

Start with systemctl start gitea fails.

The log configured in app.ini does not give any hint about the cause of the error (neither did journalctl).

Starting Gitea interactively from the terminal revealed the cause:

$ GITEA_WORK_DIR=/var/lib/gitea/ /usr/local/bin/gitea web -c /etc/gitea/app.ini
2023/07/19 19:48:36 ...g/config_provider.go:327:deprecatedSettingFatal() [F] Deprecated fallback `[server]` `LFS_CONTENT_PATH` present. Use `[lfs]` `PATH` instead. This fallback will be/has been removed in v1.19.0

This information should probably also be written to configured log file. Also "v1.19.0" in the error message does not seem to be correct. And it may be added to the list of breaking changes (https://github.com/go-gitea/gitea/releases/tag/v1.20.0).

Gitea Version

1.20.0

Can you reproduce the bug on the Gitea demo site?

No

How are you running Gitea?

Download from GitHub; run as a Systemd service.

Database

PostgreSQL

Originally created by @veita on GitHub (Jul 19, 2023). ### Description * Update from Gitea 1.19.4 to 1.20.0 * Gitea deployed as a Systemd service on Debian 12 Start with `systemctl start gitea` fails. The log configured in `app.ini` does not give any hint about the cause of the error (neither did `journalctl`). Starting Gitea interactively from the terminal revealed the cause: ``` $ GITEA_WORK_DIR=/var/lib/gitea/ /usr/local/bin/gitea web -c /etc/gitea/app.ini 2023/07/19 19:48:36 ...g/config_provider.go:327:deprecatedSettingFatal() [F] Deprecated fallback `[server]` `LFS_CONTENT_PATH` present. Use `[lfs]` `PATH` instead. This fallback will be/has been removed in v1.19.0 ``` This information should probably also be written to configured log file. Also "v1.19.0" in the error message does not seem to be correct. And it may be added to the list of breaking changes (https://github.com/go-gitea/gitea/releases/tag/v1.20.0). ### Gitea Version 1.20.0 ### Can you reproduce the bug on the Gitea demo site? No ### How are you running Gitea? Download from GitHub; run as a Systemd service. ### Database PostgreSQL
GiteaMirror added the issue/not-a-bug label 2025-11-02 09:33:19 -06:00
GiteaMirror commented 2025-11-02 09:33:19 -06:00
Author
Owner
Copy Link

@why0why0why commented on GitHub (Jul 20, 2023):

Try to modify app.ini from

[server]
LFS_CONTENT_PATH=xxxxx

to

[lfs]
PATH=xxxxx
@why0why0why commented on GitHub (Jul 20, 2023): Try to modify app.ini from ``` [server] LFS_CONTENT_PATH=xxxxx ``` to ``` [lfs] PATH=xxxxx ```
GiteaMirror commented 2025-11-02 09:33:20 -06:00
Author
Owner
Copy Link

@veita commented on GitHub (Jul 20, 2023):

@Lunny This bug report is about missing log entries, incorrect information and the incomplete change log, which may prevent people from finding the configuration error easily.

This information should probably also be written to configured log file. Also "v1.19.0" in the error message does not seem to be correct. And it may be added to the list of breaking changes (https://github.com/go-gitea/gitea/releases/tag/v1.20.0).

@veita commented on GitHub (Jul 20, 2023): @Lunny This bug report is about missing log entries, incorrect information and the incomplete change log, which may prevent people from finding the configuration error easily. > This information should probably also be written to configured log file. Also "v1.19.0" in the error message does not seem to be correct. And it may be added to the list of breaking changes (https://github.com/go-gitea/gitea/releases/tag/v1.20.0).
GiteaMirror commented 2025-11-02 09:33:20 -06:00
Author
Owner
Copy Link

@veita commented on GitHub (Jul 20, 2023):

@why0why0why See https://docs.gitea.com/administration/git-lfs-setup

@veita commented on GitHub (Jul 20, 2023): @why0why0why See https://docs.gitea.com/administration/git-lfs-setup
GiteaMirror commented 2025-11-02 09:33:20 -06:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 20, 2023):

Be aware that you have to remove or comment (using ;) the old setting.
Even when the new setting is in place, Gitea will not start if the old setting is still there.
(which is a defect IMHO as it should ignore not used settings in all cases).

@ghost commented on GitHub (Jul 20, 2023): Be aware that you have to remove or comment (using ;) the old setting. Even when the new setting is in place, Gitea will not start if the old setting is still there. (which is a defect IMHO as it should ignore not used settings in all cases).
GiteaMirror commented 2025-11-02 09:33:20 -06:00
Author
Owner
Copy Link

@Johnson90512 commented on GitHub (Aug 10, 2023):

Can this also be added to the upgrade documentation? I just ran into this issue while upgrading and took a lot of searching to find this post.

@Johnson90512 commented on GitHub (Aug 10, 2023): Can this also be added to the upgrade documentation? I just ran into this issue while upgrading and took a lot of searching to find this post.
GiteaMirror commented 2025-11-02 09:33:21 -06:00
Author
Owner
Copy Link

@jme147 commented on GitHub (Aug 10, 2023):

upgrade-from-gitea.en-us.md

@jme147 commented on GitHub (Aug 10, 2023): [upgrade-from-gitea.en-us.md](https://github.com/go-gitea/gitea/files/12315415/upgrade-from-gitea.en-us.md)
GiteaMirror commented 2025-11-02 09:33:21 -06:00
Author
Owner
Copy Link

@jme147 commented on GitHub (Aug 10, 2023):

I tried to create a pull request to update the installation/upgrade instructions, but couldn't create a request due to not being a collaborator. Can someone add the above file to a pull request?

@jme147 commented on GitHub (Aug 10, 2023): I tried to create a pull request to update the installation/upgrade instructions, but couldn't create a request due to not being a collaborator. Can someone add the above file to a pull request?
GiteaMirror commented 2025-11-02 09:33:21 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 11, 2023):

Can this also be added to the upgrade documentation? I just ran into this issue while upgrading and took a lot of searching to find this post.

Reasonable. I think we can add a step for upgrade which is check your admin panel top bar. Some deprecated configurations will be displayed there, if you couldn't resolve them, Gitea may cannot started after upgrade. I will create a PR for that.

@lunny commented on GitHub (Aug 11, 2023): > Can this also be added to the upgrade documentation? I just ran into this issue while upgrading and took a lot of searching to find this post. Reasonable. I think we can add a step for upgrade which is check your admin panel top bar. Some deprecated configurations will be displayed there, if you couldn't resolve them, Gitea may cannot started after upgrade. I will create a PR for that.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/not-a-bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#11283
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?