Problems with the new release 1.11.7 #5577

@somera commented on GitHub (Jun 18, 2020):

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

Yes. I cleared the browser cache.

@somera commented on GitHub (Jun 18, 2020): > and sometimes you have to clear the browser cache ... Yes. I cleared the browser cache.

GiteaMirror commented

@techknowlogick commented on GitHub (Jun 18, 2020):

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

@techknowlogick commented on GitHub (Jun 18, 2020): We've just released 1.12.0 please update to that version.

GiteaMirror commented

@somera commented on GitHub (Jun 18, 2020):

Did you build also styles?

I do this:

TAGS="bindata sqlite sqlite_unlock_notify" make generate build

after every release

@somera commented on GitHub (Jun 18, 2020): > Did you build also styles? I do this: `TAGS="bindata sqlite sqlite_unlock_notify" make generate build` after every release

GiteaMirror commented

@somera commented on GitHub (Jun 18, 2020):

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 commented on GitHub (Jun 18, 2020): > 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?

GiteaMirror commented

@somera commented on GitHub (Jun 18, 2020):

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

@somera commented on GitHub (Jun 18, 2020): I'm usind Nginx as proxy for my local gitea instance ![image](https://user-images.githubusercontent.com/8334250/85059193-86f1ca80-b1a3-11ea-8c4d-f42543513337.png)

GiteaMirror commented

@somera commented on GitHub (Jun 18, 2020):

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 commented on GitHub (Jun 18, 2020): > 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 ```

GiteaMirror commented

@somera commented on GitHub (Jun 18, 2020):

I downloaded now the official release

gitea-1.12.0-linux-arm-6

cause I can't compile it on my system.

@somera commented on GitHub (Jun 18, 2020): I downloaded now the official release `gitea-1.12.0-linux-arm-6` cause I can't compile it on my system.

GiteaMirror commented

@somera commented on GitHub (Jun 18, 2020):

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?

@somera commented on GitHub (Jun 18, 2020): > 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?

GiteaMirror commented

@silverwind commented on GitHub (Jun 18, 2020):

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

@silverwind commented on GitHub (Jun 18, 2020): Changing `make generate build` to just `make build` should fix this.

GiteaMirror commented

@somera commented on GitHub (Jun 18, 2020):

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.

@somera commented on GitHub (Jun 18, 2020): > 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.

GiteaMirror commented

@silverwind commented on GitHub (Jun 18, 2020):

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.

@silverwind commented on GitHub (Jun 18, 2020): 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.

GiteaMirror commented