Gitea: Problems with the new release 1.11.7

[somera]

• Gitea version (or commit ref): commit 7937f1463a9be43574460b14fe7a509ca62ecd6d (HEAD -> release/v1.11, tag: v1.11.7, origin/release/v1.11)
• Git version: 1.11.7
• Operating system: Linux pi-manager 4.19.118-v7l+ #1311 SMP Mon Apr 27 14:26:42 BST 2020 armv7l GNU/Linux
• Database (use [x]):
  
  
  
  • [ ] PostgreSQL
  
  
  • [ ] MySQL
  
  
  • [ ] MSSQL
  
  
  • [x] SQLite
  
  
• Can you reproduce the bug at https://try.gitea.io:
  
  
  
  • [ ] Yes (provide example URL)
  
  
  • [ ] No
  
  
  • [x] Not relevant
  
  
• Log gist:

Description

I updated my local git clone and compiled the new release. like I do it every time. No compile errors. But the look&feel looks strange. Same problems in Chrome and FF. Actual versions. HTTP shows some 404 errors.

I switched back to 1.11.6. which works fine.

Screenshots

[lafriks]

Did you build also styles?

[6543]

and sometimes you have to clear the browser cache ...

[somera]

and sometimes you have to clear the browser cache ...

Yes. I cleared the browser cache.

[techknowlogick]

We've just released 1.12.0 please update to that version.

[somera]

Did you build also styles?

I do this:

TAGS="bindata sqlite sqlite_unlock_notify" make generate build

after every release

[somera]

We've just released 1.12.0 please update to that version.

O.k. I can try this. Its possible to go back to 1.11.6 when I have some problems?

[somera]

I'm usind Nginx as proxy for my local gitea instance

[somera]

We've just released 1.12.0 please update to that version.

I can't build 1.12.0 on my Raspi. Cause I nee the newest go version. I try to build 1.11.7 again.

build flag -mod=vendor only valid when using modules
CC= GOOS= GOARCH= go generate -mod=vendor -tags 'bindata sqlite sqlite_unlock_notify'
Gitea requires Go 1.12 or greater to build. You can get it at https://golang.org/dl/
make: *** [Makefile:177: go-check] Fehler 1

[somera]

I downloaded now the official release

gitea-1.12.0-linux-arm-6

cause I can't compile it on my system.

[somera]

We've just released 1.12.0 please update to that version.

With gitea-1.12.0-linux-arm-6 I see in the gitea.log

ORM engine initialization attempt #1/10...

if this reach #10/10 than the process is finished?

[silverwind]

Changing make generate build to just make build should fix this.

[somera]

Changing make generate build to just make build should fix this.

Thx for the info. But now I switched to the official gitea-1.12.0-linux-arm-6. And as I can see in the gitea.log the DB will be migrated. I think, I can't switch back to 1.11.

[silverwind]

No problem, you might want to close this then. Issue is the extra generate causes bindata to build too early and without webpack files resulting in a broken binary. Just remove it and it will build in the right order.

[somera]

I will close my problem now, cause I switched to the official

gitea-1.12.0-linux-arm-6

release. Thx for the feedback & help!