An error occurred fetching the project authors.
- 24 Apr, 2020 1 commit
-
-
Julien Muchembled authored
-
- 02 Feb, 2020 1 commit
-
-
Jérome Perrin authored
It seems some programs can only be built by the same gcc than the one used to build golang itself. For example, when system gcc is gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516, grafana-server fail to build with: /data/slappart11_testnode/cqg/inst/test0-0/tmp/shared/golang1.12/fbee59cfb3c995382cf70d409615aa54/pkg/tool/linux_amd64/link: running gcc failed: exit status 1 /usr/bin/ld: /tmp/go-link-305363633/000000.o: unable to initialize decompress status for section .debug_info /usr/bin/ld: /tmp/go-link-305363633/000000.o: unable to initialize decompress status for section .debug_info /usr/bin/ld: /tmp/go-link-305363633/000000.o: unable to initialize decompress status for section .debug_info /usr/bin/ld: /tmp/go-link-305363633/000000.o: unable to initialize decompress status for section .debug_info /tmp/go-link-305363633/000000.o: file not recognized: File format not recognized collect2: error: ld returned 1 exit status Also generally, if we don't trust system gcc to build golang, we cannot trust it to build golang programs. The downside is that if components or software want to use a specifig golang version they have to set both golang= and the corresponding gcc-bin-directory= in their [gowork]
-
- 30 Aug, 2019 1 commit
-
-
Łukasz Nowak authored
-
- 24 Jul, 2019 1 commit
-
-
Łukasz Nowak authored
Notice that project changed from github.com/mholt to github.com/caddyserver
-
- 26 Jun, 2019 1 commit
-
-
Łukasz Nowak authored
This also means that caddy source is fetched directly from upstream, as all required fixes has been incorporated into the upstream. Drop direct usage of gowork for now, in order to have caddy built using go module, support for gowork with go modules might come later. Follow new way of certificate managament in Caddy 1 as noted https://github.com/mholt/caddy/issues/2588#issuecomment-505367152
-
- 26 Apr, 2019 1 commit
-
-
Łukasz Nowak authored
This reverts commit 6d2019b965f4a3521b651f2cb9ef241dce29af55, as new caddy has issues with tls certificate configuration: https://github.com/mholt/caddy/issues/2588 About nxd-v0.11.5-4-g9d3151db: * not released yet functionality for regular expression cookie rewriting is available: https://github.com/mholt/caddy/pull/2144 * not released yet functionality for ca_certifices in proxy: https://github.com/mholt/caddy/pull/2380 * support for builtin log rotation disabling
-
- 23 Apr, 2019 1 commit
-
-
Łukasz Nowak authored
caddyserver/builds repository is obsoleted and this commit avoids fetching it.
-
- 18 Apr, 2019 1 commit
-
-
Łukasz Nowak authored
QUIC implementation module is fixed.
-
- 16 Apr, 2019 1 commit
-
-
Łukasz Nowak authored
This also means that caddy source is fetched directly from upstream, as all required fixes has been incorporated into the upstream. Since https://github.com/mholt/caddy/releases/tag/v0.11.4 TLS-SNI challenge is replaced by ACME TLS-ALPN challenge, so switch has changed. Drop direct usage of gowork for now, in order to have caddy built using go module, support for gowork with go modules might come later. /reviewed-on nexedi/slapos!544
-
- 14 Mar, 2019 1 commit
-
-
Łukasz Nowak authored
-
- 28 Jun, 2018 1 commit
-
-
Łukasz Nowak authored
In order to follow proper way, move caddy to the component and reuse it.
-
- 24 Oct, 2017 2 commits
- 23 Oct, 2017 2 commits
-
-
Gabriel Monnerat authored
-
Rafael Monnerat authored
This reverts merge request !243
-
- 20 Oct, 2017 1 commit
-
-
Gabriel Monnerat authored
-