-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
first-time install of build-essential returns non-zero exit status #7
Comments
|
This may be related to this issue: |
When trussing the pkgin install, we found that the following is written out to /var/db/pkgin/sql.log:
|
Note: This only appears to happen with pkgsrc 0.6.4 (smartos-base64 13.2.0, for example). |
We get a nonzero exit status when installing scmgit on its own, so the problem may lie there. |
It's a known issue - pkgin will return non-zero if one of the packages it installs already exists on the system. It's due to the core pkg_add, which behaves the same if '-f' forced (as pkgin executes it), whereas it should really just no-op "nothing to do". |
I've built an updated pkg_install to fix this for 2013Q1 and 2013Q2. In order to upgrade, you must run
Subsequent
This is merely cosmetic, and will be fixed in subsequent releases. |
@jperkin I have included your workaround in my version of the joyent-smartmachine.erb bootstrap file for Chef. |
This occurs after a successful install of build-essential and its dependencies. This causes big problems for tools like chef, which want to exit/bail when this happens.
/cc @sax @bixu
The text was updated successfully, but these errors were encountered: