Package Details: kubernetes-helm 2.14.2-1

Git Clone URL: https://aur.archlinux.org/kubernetes-helm.git (read-only)
Package Base: kubernetes-helm
Description: A tool to manage Kubernetes charts
Upstream URL: https://github.com/helm/helm
Keywords: helm k8s kubernetes
Licenses: Apache
Conflicts: kubernetes-helm-bin
Submitter: tongpu
Maintainer: tongpu
Last Packager: tongpu
Votes: 31
Popularity: 1.641636
First Submitted: 2017-01-04 10:36
Last Updated: 2019-07-11 22:21

Dependencies (6)

Required by (0)

Sources (1)

Pinned Comments

tongpu commented on 2019-06-12 07:27

I've faced some issues during the update to v2.14.1 with building the package, because glide was behaving strangely. I had to run "glide cache-clear" to fix the issues. This just as an information if someone is facing the same issues.

Latest Comments

1 2 3 4 Next › Last »

carbolymer commented on 2019-06-25 14:34

Doesn't build:

[INFO]  --> Fetching vbom.ml/util
[WARN]  Unable to checkout vbom.ml/util
[ERROR] Update failed for vbom.ml/util: Cannot detect VCS
[ERROR] Failed to install: Cannot detect VCS
make: *** [Makefile:171: bootstrap] Error 1

Looks like: https://github.com/helm/helm/issues/2466#issuecomment-395164749

tongpu commented on 2019-06-12 07:27

I've faced some issues during the update to v2.14.1 with building the package, because glide was behaving strangely. I had to run "glide cache-clear" to fix the issues. This just as an information if someone is facing the same issues.

tongpu commented on 2019-05-31 10:47

@alwyn There's a reason we're using a git checkout and not the "release" tarball and that is that the version in the tarball you get from GitHub is wrong:

Client: &version.Version{SemVer:"v2.14+unreleased", GitCommit:"f73cdefc6b98", GitTreeState:"dirty"}

This is probably caused by something in versioning.mk and because of that this package is being built directly from the git sources. Additionally be aware that the tarball you can download from GitHub is created by GitHub and does not represent an official release tarball, because e.g. not checksums are being published for it.

alwyn commented on 2019-05-29 09:38

As the versions used in this PKGBUILD points to the appropriate release, I think it would be better to use the release tarball instead and check its hash.

Simple patch: https://gist.github.com/Alveel/0fc483814db000ac68a64ab2034d0564

tongpu commented on 2019-05-07 20:02

@maximbaz You're correct and I'm going to fix it right now. I've mixed it up with the all wildcard that is present in Debian.

maximbaz commented on 2019-05-07 19:58

Strictly speaking, AFAIK "any" has a slightly different meaning of "once compiled on any platform, the binary will run on any other platform" which is true for things like python scripts, but not for this app.

tongpu commented on 2019-05-07 19:54

@eminguez I've switched to arch=('any'), that should also solve your issue.

eminguez commented on 2019-05-07 12:57

It would be nice to enable this PKGBUILD to be used in 'aarch64' architectures (helm supports it). I've tested it locally and it works.

michelesr commented on 2019-02-14 10:46

Could you please copy the tiller binary in addition to the helm one? That is very useful when you run tiller locally (that seems to be a common pattern for increased security in a k8s cluster)

install -Dm755 "$srcdir/src/k8s.io/helm/bin/tiller" -t "$pkgdir/usr/bin"

maximbaz commented on 2019-01-23 14:02

tongpu, if you don't increase pkgver and pkgrel, people won't get an update notification ;)