Age | Commit message (Collapse) | Author |
|
After bisecting `nixpkgs-master` I realized that the usage of
`-trimpath`[0] by default for Go modules[1] is responsible for breaking UI
delivery of `gotify-server`[2].
This behavior can only be turned off by setting `allowGoReference` to
`true`.
We may want to find a better long-term fix, but given that this only
affects a leaf-package and actually fixes the problem, this is good
enough for now.
Fixes #105472
[0] https://golang.org/doc/go1.13#go-command
[1] 4e9f7bbf8573d07f7b0c87d97c026cd4aad5a758
[2] https://hydra.nixos.org/build/131660876
|
|
https://github.com/gotify/server/releases/tag/v2.0.19
https://github.com/gotify/server/releases/tag/v2.0.20
|
|
Use new line in printf calls of update.sh, so editor config CI check
won't fail.
|
|
In version 2.0.15 `gotify` switched to `packr` at 2.x which is why the
UI can't be served properly via HTTP and causes an empty 500 response and
the following errors in `journald`:
```
2020/09/12 19:18:33 [Recovery] 2020/09/12 - 19:18:33 panic recovered:
GET / HTTP/1.1
Host: localhost:8080
Accept: */*
User-Agent: curl/7.72.0
stat /home/ma27/Projects/ui/build/index.html: no such file or directory
```
This wasn't caught by the VM-test as it only tested the REST and push
APIs. Using their internal `packr.go` script in our build as it's the
case in the upstream build-system[1] fixes the issue.
[1] https://github.com/gotify/server/pull/277/files#diff-b67911656ef5d18c4ae36cb6741b7965R48
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Improved update script / procedure by getting all versions and shas
needed to build it.
|
|
This reverts commit 4e6bf03504c9e09f067cc6dee6b5aeec43a1405c, reversing
changes made to afd997aab6e9b7a322198092c7828d6c560ac06f.
Instead we propagate those frameworks from the compiler again
|
|
|
|
|
|
https://github.com/gotify/server/releases/tag/v2.0.13
|
|
|
|
|
|
|