~kaey

Recent activity

Re: [PATCH] community/alertmanager: fix LDFLAGS issues 16 days ago

From Konstantin Kulikov to ~sircmpwn/alpine-aports

On 1/9/20 10:10 PM, Drew DeVault wrote:
> This should(?) fix the build on aarch64.
> ---
>   community/alertmanager/APKBUILD | 31 ++++++++++++++-----------------
>   1 file changed, 14 insertions(+), 17 deletions(-)
> 
> diff --git a/community/alertmanager/APKBUILD b/community/alertmanager/APKBUILD
> index e61bbb2526..c585d43871 100644
> --- a/community/alertmanager/APKBUILD
> +++ b/community/alertmanager/APKBUILD
> @@ -1,7 +1,7 @@
>   # Maintainer: Drew DeVault <sir@cmpwn.com>
>   pkgname=alertmanager
>   pkgver=0.20.0

Re: [PATCH v2] community/alertmanager: new aport 19 days ago

From Konstantin Kulikov to ~sircmpwn/alpine-aports

On 1/6/20 8:18 PM, Drew DeVault wrote:
> This package is running in production at SourceHut.
> ---
> Apologies for the noise, the previous patch was pre-rebase.
> 
>   community/alertmanager/APKBUILD               | 60 +++++++++++++++++++
>   community/alertmanager/alertmanager.confd     |  6 ++
>   community/alertmanager/alertmanager.initd     | 18 ++++++
>   .../alertmanager/alertmanager.pre-install     |  4 ++
>   4 files changed, 88 insertions(+)
>   create mode 100644 community/alertmanager/APKBUILD
>   create mode 100644 community/alertmanager/alertmanager.confd
>   create mode 100644 community/alertmanager/alertmanager.initd
>   create mode 100644 community/alertmanager/alertmanager.pre-install

Re: [PATCH] community/prometheus: add reload to init.d 19 days ago

From Konstantin Kulikov to ~sircmpwn/alpine-aports

On 1/6/20 8:19 PM, Drew DeVault wrote:
> ---
>   community/prometheus/APKBUILD         | 4 ++--
>   community/prometheus/prometheus.initd | 8 ++++++++
>   2 files changed, 10 insertions(+), 2 deletions(-)
> 
> diff --git a/community/prometheus/APKBUILD b/community/prometheus/APKBUILD
> index e5594d6942..1e46bc83dc 100644
> --- a/community/prometheus/APKBUILD
> +++ b/community/prometheus/APKBUILD
> @@ -1,7 +1,7 @@
>   # Maintainer: Drew DeVault <sir@cmpwn.com>
>   pkgname=prometheus
>   pkgver=2.15.1

Re: [PATCH v2] testing/telegraf: fix package setup 20 days ago

From Konstantin Kulikov to ~sircmpwn/alpine-aports

On 1/5/20 8:47 PM, Galen Abell wrote:
> Telegraf's conf.d command line uses the additional config directory
> `telegraf.d`, but the package installs the directory `telegraf.conf.d`.
> ---
> Bumped pkgrel (oops), switched -config-directory to /etc/telegraf.conf.d
> rather than changing created directory.
> 
>   testing/telegraf/APKBUILD       | 2 +-
>   testing/telegraf/telegraf.confd | 2 +-
>   2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/testing/telegraf/APKBUILD b/testing/telegraf/APKBUILD
> index 7ede05c220..cb0cb4c1a0 100644
> --- a/testing/telegraf/APKBUILD

Re: [PATCH] testing/telegraf: fix package setup 21 days ago

From Konstantin Kulikov to ~sircmpwn/alpine-aports

On 1/4/20 10:33 PM, Galen Abell wrote:
> Telegraf's conf.d command line uses the additional config directory
> `telegraf.d` (which is default for telegraf), but the package installs
> the directory `telegraf.conf.d`.
> ---
>   testing/telegraf/APKBUILD | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/testing/telegraf/APKBUILD b/testing/telegraf/APKBUILD
> index 7ede05c220..fdfa9e87ff 100644
> --- a/testing/telegraf/APKBUILD
> +++ b/testing/telegraf/APKBUILD
> @@ -44,7 +44,7 @@ package() {
>   	install -Dm644 "$srcdir/$pkgname.confd" "$pkgdir/etc/conf.d/$pkgname"

Re: [PATCH v3] community/prometheus: new APKBUILD a month ago

From Konstantin Kulikov to ~sircmpwn/alpine-aports

On 12/4/19 6:42 PM, Drew DeVault wrote:
> ---
> v3 drops the checkpath line for the config file, which was wrong and
> didn't really need to be there anyway.
> 
>   community/prometheus/APKBUILD               | 53 +++++++++++++++++++++
>   community/prometheus/prometheus.confd       |  5 ++
>   community/prometheus/prometheus.initd       | 16 +++++++
>   community/prometheus/prometheus.pre-install |  4 ++
>   4 files changed, 78 insertions(+)
>   create mode 100644 community/prometheus/APKBUILD
>   create mode 100644 community/prometheus/prometheus.confd
>   create mode 100644 community/prometheus/prometheus.initd
>   create mode 100644 community/prometheus/prometheus.pre-install

Re: community/go and buildmode pie a month ago

From Konstantin Kulikov to ~sircmpwn/alpine-devel

This warning is harmless https://github.com/golang/go/issues/31544.
Will probably be fixed with linker updates in go1.15.
If you don't want to build pie binary use -buildmode=exe.

On Sat, Nov 30, 2019 at 1:13 AM Wolf <wolf@wolfsden.cz> wrote:
>
> Hello,
> when trying to complie something using the community/go package I'm
> always getting this warning:
>
>         # foo
>         loadinternal: cannot find runtime/cgo
>
> go package in community uses buildmode pie by default due to this patch:

Re: [PATCH 1/2] community/prometheus: new APKBUILD a month ago

From Konstantin Kulikov to ~sircmpwn/alpine-aports

>+               -gcflags "all=-trimpath=$PWD" \
>+               -asmflags "all=-trimpath=$PWD" \

You can use simpler go build -trimpath here.
Also add -mod=vendor to avoid downloading modules during build (will
become the default in go1.14).

>+config_file=/etc/prometheus/prometheus.yml
>+storage_path=/var/lib/prometheus/data

Usual convention is to prefix variable name with service name (eg
prometheus_config_file) to avoid potential conflicts with other openrc
defined variables.

Re: [PATCH] testing/grafana: upgrade to 6.5.0 a month ago

From Konstantin Kulikov to ~sircmpwn/alpine-aports

1. Grafana ships significant bugs with every minor release, always
wait for patch release before updating (6.5.1 was coincidentally
released a few minutes ago)
2. you have to run go get
github.com/grafana/grafana/pkg/cmd/grafana-server@COMMITHASH && go mod
tidy because I packaged it that way. I think it is fine to revert it
to simpler go build -mod=vendor for now because x/errors update no
longer needed, they have wrong go.mod file and they vendor their deps
anyway, but in the long run I'd like every go binary to have proper
version information recorded in them (queryable with go version -m
/path/to/binary or via https://godoc.org/runtime/debug#ReadBuildInfo)

>Upstream will be given tests when they learn how to use them responsibly

[PATCH v2] app/internal/window: map window after defining WM protocols 2 months ago

From Konstantin Kulikov to ~eliasnaur/gio-patches

ICCCM 4.1.2 says WMs will examine client properties every time
window is mapped. Because SetWMProtocols is called before MapWindow
some WMs (specifically taowm) never see them.

In other WMs this works because they check for WM_DELETE_WINDOW
when user tries to close window, not when window is mapped.

Signed-off-by: Konstantin Kulikov <k.kulikov2@gmail.com>
---
 app/internal/window/os_x11.go | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/app/internal/window/os_x11.go b/app/internal/window/os_x11.go
index 7f69b36..d4d6987 100644
[message trimmed]