-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Closed
Labels
issue/workaroundit is or has a workaroundit is or has a workaroundpr/breakingMerging this PR means builds will break. Needs a description what exactly breaks, and how to fix it!Merging this PR means builds will break. Needs a description what exactly breaks, and how to fix it!topic/buildPR changes how Gitea is built, i.e. regarding Docker or the MakefilePR changes how Gitea is built, i.e. regarding Docker or the Makefiletype/bug
Description
Description
I can no longer build the stable branch 1.16 on my Fedora 35 system.
go mod tidy fails, see below.
+ make 'TAGS=bindata sqlite sqlite_unlock_notify pam' 'LDFLAGS=-X "code.gitea.io/gitea/modules/setting.AppWorkPath=/var/lib/gitea" -X "code.gitea.io/gitea/modules/setting.CustomPath=/var/lib/gitea/custom" -X "code.gitea.io/gitea/modules/setting.PIDFile=/run/gitea/gitea.pid" -X "code.gitea.io/gitea/modules/setting.CustomConf=/etc/gitea/app.ini"' vendor build
go mod tidy && go mod vendor
go mod tidy: go.mod file indicates go 1.17, but maximum supported version is 1.16
make: *** [Makefile:374: vendor] Error 1
IMHO The stable branch should not break existing working setups.
Gitea Version
1.16
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
Operating System
Fedora 35 x64
How are you running Gitea?
not relevant
Database
PostgreSQL
Metadata
Metadata
Assignees
Labels
issue/workaroundit is or has a workaroundit is or has a workaroundpr/breakingMerging this PR means builds will break. Needs a description what exactly breaks, and how to fix it!Merging this PR means builds will break. Needs a description what exactly breaks, and how to fix it!topic/buildPR changes how Gitea is built, i.e. regarding Docker or the MakefilePR changes how Gitea is built, i.e. regarding Docker or the Makefiletype/bug