Package Details: kubernetes-helm 3.1.0-2

Git Clone URL: (read-only, click to copy)
Package Base: kubernetes-helm
Description: A tool to manage Kubernetes charts
Upstream URL:
Keywords: helm k8s kubernetes
Licenses: Apache
Conflicts: kubernetes-helm, kubernetes-helm-bin, kubernetes-helm-git
Provides: kubernetes-helm
Submitter: tongpu
Maintainer: tongpu (eyenx)
Last Packager: eyenx
Votes: 39
Popularity: 2.15
First Submitted: 2017-01-04 10:36
Last Updated: 2020-02-14 08:59

Dependencies (5)

Required by (0)

Sources (1)

Latest Comments

1 2 3 4 Next › Last »

xuanwo commented on 2019-10-30 08:52

@tongpu: I use extra-x86_64-build to build it.

It looks like makepkg can't find the tag, I'll check it later.

tongpu commented on 2019-10-24 06:31

xuanwo: How are you building the package? The v2.15.1 tag is clearly there at GitHub:

xuanwo commented on 2019-10-23 10:55

v2.15.1 built failed for:

(1/4) Creating system user accounts...
Creating group git with gid 977.
Creating user git (git daemon user) with uid 977 and gid 977.
(2/4) Reloading system manager configuration...
  Skipped: Current root is not booted.
(3/4) Arming ConditionNeedsUpdate...
(4/4) Warn about old perl modules
 [1m [32m==> (B [m [1m Retrieving sources... (B [m
 [1m [33m==> WARNING: (B [m [1m Skipping all source file integrity checks. (B [m
 [1m [32m==> (B [m [1m Extracting sources... (B [m
 [1m [34m  -> (B [m [1m Creating working copy of helm git repo... (B [m
Cloning into 'helm'...
fatal: 'v2.15.1' is not a commit and a branch 'makepkg' cannot be created from it
 [1m [31m==> ERROR: (B [m [1m Failure while creating working copy of helm git repo (B [m
 [1m    Aborting... (B [m
 [1m [31m==> ERROR: (B [m [1m Build failed, check /var/lib/archbuild/extra-x86_64/lilydjwg/build (B [m

carbolymer commented on 2019-06-25 14:34

Doesn't build:

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

Looks like:

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 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:

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.