Arch Linux User Repository

Is this still maintained package? If not, I would like to take over.

@Maximka I jumped ship to ansible, time for someone new to step up and maintain this.

Until its officially out on the webpage I don't update guys. https://downloads.chef.io/chefdk 1.22 is still the latest one listed as released.

I just changed this on PKGBUILD ``` pkgver=1.3.10 pkgrel=1 source=("https://packages.chef.io/files/current/chefdk/1.3.10/ubuntu/12.04/chefdk_${pkgver}-${pkgrel}_amd64.deb") sha256sums=('14c030e5456c79318515f0debf4893a435ffcb56f18a5425f3d8b576dee91a20') ```

v1.2.1 is out :) Well, on github releases yes, but far behind here hmm https://downloads.chef.io/chefdk/stable/1.1.16.

Here is a diff for upgrading to 1.1.16 that I used recently, it also addresses (hopefully correctly) the issue with broken symlinks. YMMV, correct as necessary... N.B. I used the deb from 14.04 from the chef downloads site as I was about to create an ubuntu vagrant image using 14.04... otherwise I have no reason to use that particular deb. I assume they are the same, but maybe they aren't, I didn't look. HTH Jeff ---- Diff Below ---- 4c4 < pkgver=1.0.3 --- > pkgver=1.1.16 6c6 < _ubuntuver=raring --- > _ubuntuver=trusty 14,15c14,15 < source=("https://packages.chef.io/stable/ubuntu/12.04/chefdk_${pkgver}-1_amd64.deb") < sha512sums=('ca3734ac4af5a6d92585d290d6fd0d50d974d5afc4701290afb0c28b38c623014a700658f0b0cb6941c4d99caad10e3a652917101ddec708a879098b9f66239c') --- > source=("https://packages.chef.io/files/stable/chefdk/1.1.16/ubuntu/14.04/chefdk_${pkgver}-1_amd64.deb") > sha256sums=('7a1bed7f6eae3ae26694f9d3f47ce76d5e0cbbaba72dafcbc175e89ba0ac6dd9') 25c25 < binaries="berks chef chef-apply chef-shell chef-solo chef-zero delivery fauxhai foodcritic kitchen knife ohai push-apply pushy-client pushy-service-manager rubocop cookstyle chef-client" --- > binaries="berks chef chef-apply chef-shell chef-solo delivery foodcritic kitchen knife ohai push-apply pushy-client pushy-service-manager rubocop cookstyle chef-client" 31a32,39 > > # some binaries do not get linked from the /opt/chefdk/bin directory above > # as they exist in the embedded/bin directory instead, link from there. > embedded="chef-zero fauxhai" > for binary in $embedded; do > ln -s /opt/chefdk/embedded/bin/$binary $pkgdir/usr/bin || error_exit "Canot link $binary to /usr/bin" > done >

@czk quick look, looks like this is a upstream issue. If anyone has a quick fix thhough I'll gladly make the change.

I noticed 2 broken symlinks - /usr/bin/chef-zero and /usr/bin/fauxhai. Can you fix that?: # ls -l /usr/bin/chef-zero lrwxrwxrwx 1 root root 25 Dec 9 18:16 /usr/bin/chef-zero -> /opt/chefdk/bin/chef-zero # ls -l /opt/chefdk/bin/chef-zero ls: cannot access '/opt/chefdk/bin/chef-zero': No such file or directory # ls -l /usr/bin/fauxhai lrwxrwxrwx 1 root root 23 Dec 9 18:16 /usr/bin/fauxhai -> /opt/chefdk/bin/fauxhai # ls -l /opt/chefdk/bin/fauxhai ls: cannot access '/opt/chefdk/bin/fauxhai': No such file or directory Is that a packaging error or rather an upstream issue?

@automaticgiant It seems that stripping just takes a very very long time. I'm not sure why (too many files causing some unexpected quadratic behavior?), but a lot of time is spent in the `while read -r filename; do ... done < <(find "$pkgdir" -type f -perm -u+x)` loop in makepkg. I waited a while and it eventually did finish.

@Maximka I'll happily take it over.