Skip to content

Instantly share code, notes, and snippets.

Application Link: The admin link to the user, looks something like https://apply.boundless.com/active_admin/applications/12345

Where: Describe where you are seeing this issue. Easy way to do this, copy paste the URL.

Context: Describe your context with a few sentences. Are you going through as a beneficiary or sponsor? Did you answer the questions in a certain way that leads you to this issue?

Repro:

  • Step-by-step describe the actions you take to get into this situation.
  • Do this to the best of your understanding of the app.

Keybase proof

I hereby claim:

  • I am sersut on github.
  • I am serdarsutay (https://keybase.io/serdarsutay) on keybase.
  • I have a public key ASDfO7_b2KhUEUpGBN_B4S841v-oLCVeWWN-gVHK71S2Ego

To claim this, I am signing this object:

Opscode::Version
  resolving with input :latest
    behaves like correct version resolution
      with 12.1.2 & 12.1.2+20150906090309
        selects 12.1.2 (FAILED - 1)
      with 12.1.2 & 12.1.2+20150906090309-1
        selects 12.1.2 (FAILED - 2)
      with 12.1.2-1 & 12.1.2+20150906090309
        selects 12.1.2-1 (FAILED - 3)
Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e; 2014-06-17T13:51:42+00:00)
Maven home: /opt/opscode-analytics/embedded/service/maven
Java version: 1.7.0_25, vendor: Oracle Corporation
Java home: /opt/opscode-analytics/embedded/jre/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.11.0-15-generic", arch: "amd64", family: "unix"
[INFO] Error stacktraces are turned on.
[DEBUG] Reading global settings from /opt/opscode-analytics/embedded/service/maven/conf/settings.xml
[DEBUG] Reading user settings from /root/.m2/settings.xml
[DEBUG] Using local repository at /root/.m2/repository

Ohai chefs,

We are super excited to announce the availability of the first Chef Client 12.0.0 Release Candidate that accompanies the recently released Chef Server 12 Release Candidate.

In this major version release, we have all the features we've decided to complete as a community, around 70 contributions from Chef community and lots of minor features / bug fixes. You can see the full list of changes in our change log and more information in our release notes.

Backwards Compatibility

The biggest highlight of the Chef Client 12 release is the backward compatibility. Chef Client 12 is fully backwards compatible with Chef 11. You can use Chef Client 12 against Enterprise Chef, Open Source Chef, Hosted Chef and Chef Server 12 with your exis

Chef Native Gem Installation Issues with Xcode CLI Tools 5.1

Summary

In recently released Xcode CLI tools 5.1, Apple has changed clang not to accept unknown CLI options. This causes gem installation failures for gems with C extensions when using Chef Client Mac OSX Omnibus Packages.

The reason of this issue is that during the build process, ruby is configured with compiler options that are incompatible with the latest version of clang. When installing rubygems with C extensions this leads to errors like:

clang: error: unknown argument: '-R/opt/chef/embedded/lib' [-Wunused-command-line-argument-hard-error-in-future]