WyseNynja's Homebrew tap for all your OSX bitcoin needs

[Red Emerald]

I have made my own homebrew tap to make it easier to compile bitcoind, bitcoind-next-test, and armory-qt from source on Mac OSX. It's been up and working for me for a while, and I've posted about it elsewhere, but I figured it deserved it's own thread.

https://github.com/wysenynja/homebrew-bitcoin

If you don't yet have homebrew, it is incredibly easy to install.

Code:

ruby -e "$(curl -fsSkL raw.github.com/mxcl/homebrew/go)"

It's always a good idea to keep brew up to date and to check with the doctor to make sure everything is running smoothly.  If you just installed homebrew, you will more than likely need to also install Xcode (don't worry, it's free and easy to get from the App Store) and the Command Line Tools that come with Xcode.  The doctor should tell you how.

Code:

brew update
brew doctor

Now you are ready to get my formula!

Code:

brew tap WyseNynja/bitcoin

Now you can install things!  I used to have to prefix my install targets with "wysenynja/bitcoin/" but since the last time I updated, I haven't needed to.

Try one (or all) of these first.

Code:

brew install bitcoind
brew install bitcoind-next-test --HEAD
brew install armory-qt

And if those fail (let me know if they do), do it like this:

Code:

brew install wysenynja/bitcoin/bitcoind
brew install wysenynja/bitcoin/bitcoind-next-test --HEAD
brew install wysenynja/bitcoin/armory-qt

All of the source comes from their official repositories.  I'm just providing formula to make the install easy.

bitcoind is the v0.7.2 tag of https://github.com/bitcoin/bitcoin
bitcoind-next-test is the next-test branch of https://github.com/luke-jr/bitcoin
armory-qt is the v0.86.3-beta tag of https://github.com/etotheipi/BitcoinArmory

EDIT: When installing armory-qt, the git tag is verified against etotheipi's armory signing key. The git command will attempt to add the key to your keychain for you, but sometimes your default keyserver does not have the key (keyserver.pgp.com is missing armory's because keys have to manually added and verified there).

If armory fails to add the key for you, you can get it for sure from ubuntu.  This step will more than likely NOT need to be run, but if you get the error "gpg: Can't check signature: public key not found" then run this.

Code:

gpg --recv-keys --keyserver keyserver.ubuntu.com 98832223

[Red Emerald]

You can now easily install the testing branch of armory-qt

Code:

brew install armory-qt --devel

[picobit]

Dear Red Emerald,

Thanks a lot for making this tap.  It really makes it a lot easier - except that this time I run into a snag:

Code:

$ brew upgrade
==> Upgrading 3 outdated packages, with result:
armory-qt 0.86.3-beta, netpbm 10.60.05, sqlite 3.7.15
==> Upgrading armory-qt
==> Cloning https://github.com/etotheipi/BitcoinArmory.git
Updating /Library/Caches/Homebrew/armory-qt--git
==> Checking out tag v0.86.3-beta
==> Patching
patching file ArmoryQt.command
==> git verify-tag v0.86.3-beta
error: cannot run gpg: No such file or directory
error: could not run gpg.

READ THIS: https://github.com/mxcl/homebrew/wiki/troubleshooting

Note that I do have gpg installed, and can run it from the command line:

Code:

$ gpg --version
gpg (GnuPG/MacGPG2) 2.0.17
libgcrypt 1.4.6
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, 
        CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

[Red Emerald]

Dear Red Emerald,

Thanks a lot for making this tap.  It really makes it a lot easier - except that this time I run into a snag:

Code:

$ brew upgrade
==> Upgrading 3 outdated packages, with result:
armory-qt 0.86.3-beta, netpbm 10.60.05, sqlite 3.7.15
==> Upgrading armory-qt
==> Cloning https://github.com/etotheipi/BitcoinArmory.git
Updating /Library/Caches/Homebrew/armory-qt--git
==> Checking out tag v0.86.3-beta
==> Patching
patching file ArmoryQt.command
==> git verify-tag v0.86.3-beta
error: cannot run gpg: No such file or directory
error: could not run gpg.

READ THIS: https://github.com/mxcl/homebrew/wiki/troubleshooting

Note that I do have gpg installed, and can run it from the command line:

Code:

$ gpg --version
gpg (GnuPG/MacGPG2) 2.0.17
libgcrypt 1.4.6
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, 
        CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

When brew installs things, I think it uses a modified PATH.

Code:

which gpg
echo $PATH

Until we figure this out, you can install with the "--skip-verify" "--without-gpg" flag.

[Red Emerald]

Weird that it works for me.

It's not a "real problem" considering it is documented

Superenv removes /usr/local/bin from the PATH as well as all user-PATHs that are not determined to be essential to the build. It does this because other PATHs are full of stuff that breaks builds. We have 15,000 tickets to that testament.

I just made a change to the formula that will hopefully work for you guys.  Try it out.

Code:

brew update
brew upgrade

[Red Emerald]

Weird that it works for me.

It's not a "real problem" considering it is documented

Superenv removes /usr/local/bin from the PATH as well as all user-PATHs that are not determined to be essential to the build. It does this because other PATHs are full of stuff that breaks builds. We have 15,000 tickets to that testament.

I just made a change to the formula that will hopefully work for you guys.  Try it out.

Code:

brew update
brew upgrade

Gee so because you document your breakage it is not a problem that is what a ./configure check is for you know that part where it says "Checking whether build environment is sane" or words to that meaning along with checking the versions required for the programs/libs used in building.

There is no need to be hostile.  Did the update work for you or not?

[K1773R]

Dear Red Emerald,

Thanks a lot for making this tap.  It really makes it a lot easier - except that this time I run into a snag:

Code:

$ brew upgrade
==> Upgrading 3 outdated packages, with result:
armory-qt 0.86.3-beta, netpbm 10.60.05, sqlite 3.7.15
==> Upgrading armory-qt
==> Cloning https://github.com/etotheipi/BitcoinArmory.git
Updating /Library/Caches/Homebrew/armory-qt--git
==> Checking out tag v0.86.3-beta
==> Patching
patching file ArmoryQt.command
==> git verify-tag v0.86.3-beta
error: cannot run gpg: No such file or directory
error: could not run gpg.

READ THIS: https://github.com/mxcl/homebrew/wiki/troubleshooting

Note that I do have gpg installed, and can run it from the command line:

Code:

$ gpg --version
gpg (GnuPG/MacGPG2) 2.0.17
libgcrypt 1.4.6
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, 
        CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

When brew installs things, I think it uses a modified PATH.

Code:

which gpg
echo $PATH

Until we figure this out, you can install with the "--skip-verify" flag.

$ echo $PATH
/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin

$ which gpg
/usr/local/bin/gpg

That thing has real problems if it cannot find /usr/local/bin ...

try fixing it with this (as root or with sudo):

Code:

ln -s /usr/local/bin/gpg /usr/bin/gpg

i saw alot of scripts/binarys which call gpg directly with /usr/bin/gpg, so this may be the problem here

[Red Emerald]

Dear Red Emerald,

Thanks a lot for making this tap.  It really makes it a lot easier - except that this time I run into a snag:

Code:

$ brew upgrade
==> Upgrading 3 outdated packages, with result:
armory-qt 0.86.3-beta, netpbm 10.60.05, sqlite 3.7.15
==> Upgrading armory-qt
==> Cloning https://github.com/etotheipi/BitcoinArmory.git
Updating /Library/Caches/Homebrew/armory-qt--git
==> Checking out tag v0.86.3-beta
==> Patching
patching file ArmoryQt.command
==> git verify-tag v0.86.3-beta
error: cannot run gpg: No such file or directory
error: could not run gpg.

READ THIS: https://github.com/mxcl/homebrew/wiki/troubleshooting

Note that I do have gpg installed, and can run it from the command line:

Code:

$ gpg --version
gpg (GnuPG/MacGPG2) 2.0.17
libgcrypt 1.4.6
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, 
        CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

When brew installs things, I think it uses a modified PATH.

Code:

which gpg
echo $PATH

Until we figure this out, you can install with the "--skip-verify" flag.

$ echo $PATH
/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin

$ which gpg
/usr/local/bin/gpg

That thing has real problems if it cannot find /usr/local/bin ...

try fixing it with this (as root or with sudo):

Code:

ln -s /usr/local/bin/gpg /usr/bin/gpg

i saw alot of scripts/binarys which call gpg directly with /usr/bin/gpg, so this may be the problem here

Well that would probably do it.  First they should just try updating the tap though, because it should be fixed without manually linking things.

I am pretty sure git is not calling gpg with a fixed path.  I'm pretty sure it's just that brew's superenv uses a minimal path to avoid breaking things.

[picobit]

I tried the updated tap - sure enough, now it called gpg (but it also first replaced my ancient gpg installation with homebrews ...)
Now it gives a new error, perhaps my gpg is not set up optimally, I rarely use it.

Code:

$ brew upgrade
==> Upgrading armory-qt
==> Cloning https://github.com/etotheipi/BitcoinArmory.git
Updating /Library/Caches/Homebrew/armory-qt--git
==> Checking out tag v0.86.3-beta
==> Patching
patching file ArmoryQt.command
==> git verify-tag v0.86.3-beta
gpg: requesting key 98832223 from ldap server keyserver.pgp.com
gpgkeys: key 4AB16AEA98832223 not found on keyserver
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
gpg: Can't check signature: public key not found

READ THIS: https://github.com/mxcl/homebrew/wiki/troubleshooting

Now it is compiling with the --skip-verify flag, no problems so far.

[picobit]

Apparently they could not be bothered with putting the key needed on a key server that is what the error is telling you.

Red Emerald is actually making an unpaid effort to help us install Armory in an easier way.  You really are quite hostile to him!

Most likely my gpg setup is querying the wrong keyserver.  While it would be nice if things worked in the first try, sometimes it takes a few attempts before such a setup script works for everyone.

[gweedo]

I have no inclination to help any fool who cannot upload a gpg key and in case you did not notice asshole I have no access to that gpg to fix the problem anyways. And it is people like you that are the reason useless practices like this creep into a project always going on about how great it is that the useless practitioner is doing it for free don't point out any problems you uncouth swine how dare you... PLONK.

if your just going to criticize then don't even post in the thread, the dude made one mistake and you acted like an asshole instead of pointing it out, and it is just a script not a full program. Dude get over yourself if your such a great coder wheres your projects? I am not even going to answer anymore since I am not going to fill a good dudes thread up with stupidity from a 12yr kid which you are obviously.

[Red Emerald]

Apparently they could not be bothered with putting the key needed on a key server that is what the error is telling you.

Red Emerald is actually making an unpaid effort to help us install Armory in an easier way.  You really are quite hostile to him!

Most likely my gpg setup is querying the wrong keyserver.  While it would be nice if things worked in the first try, sometimes it takes a few attempts before such a setup script works for everyone.

So pointing out the useless way it is happening is hostile. I despise bad programming practices that make it harder to get actual work done from sloppy coders. If you had clue how key servers work then you might have point they work in round robin fashion ie. once you upload key to one key server all the severs in the group get updated once those scripts run that do the updating. In other words someone is playing at security when they have no clue how to do it that is dangerous in a project such as this where peoples money is at stake. And I am damn well going to point it out regardless of what anyone has to say about it.

It is unappreciated people like this, why don't you help him and look at the script instead of just sitting there and laughing like an asshole. People like this are detrimental to all projects.

I have no inclination to help any fool who cannot upload a gpg key and in case you did not notice asshole I have no access to that gpg to fix the problem anyways. And it is people like you that are the reason useless practices like this creep into a project always going on about how great it is that the useless practitioner is doing it for free don't point out any problems you uncouth swine how dare you... PLONK.

Now I see why your ignore link is starting to change color.  I'll help it along.

The key is on a keyserver.  It just isn't in his keychain or the keyserver he queried.  I don't automatically add etotheipi's key to your keychain because the git verify-tag command does it automatically.  I've queried a bunch of keyservers for this key and every one has worked but pgp.keyserver.com.  You have to manually upload and verify your key with them.

The key is definitely on keyserver.ubuntu.com

Code:

gpg --recv-keys --keyserver keyserver.ubuntu.com 98832223

[picobit]

Now I see why your ignore link is starting to change color.  I'll help it along.

I hope he is not behaving like this in real life, otherwise he will run into trouble quickly!

The key is on a keyserver.  It just isn't in his keychain or the keyserver he queried.  I don't automatically add etotheipi's key to your keychain because the git verify-tag command does it automatically.  I've queried a bunch of keyservers for this key and every one has worked but pgp.keyserver.com.  You have to manually upload and verify your key with them.

The key is definitely on keyserver.ubuntu.com

Looks like the keyserver that was the obvious one to use back when I configured my gpg installation (last century, probably!!) is no longer current.  Switching to Ububtu's fixed the problem.  Everything now works just fine.  Thanks again for the homebrew formula, Red Emerald!

[Red Emerald]

Armory version bumped to 0.87-beta!

[Red Emerald]

Bumped bitcoind to version 0.8.0.  --HEAD will install the latest master

[Red Emerald]

I've updated the tap to install bitcoind 0.8.5.  It only works on mavericks if you install with `brew install wysenynja/bitcoin/bitcoind --HEAD`

I expect 0.8.6 to work with Mavericks without issue.

[Red Emerald]

I've updated bitcoind (and bitcoin-cli) to version 0.9.0!  It builds on Mavericks easily.

I'm still working on the --with-coinpunk flag.

[jorijnsmit]

Cheers for this bro!

I initially found your tap on GitHub, where you stated you had a custom tap containing vanitygen (https://github.com/samr7/vanitygen/issues/45), which is maybe worth mentioning here as well.

The only concern I have is that of safety... How can I know there is no backdoor in the scripts, reporting back private keys to you?