Bitcoin Forum

Bugfix version 0.88.1, now available
(Windows users, please fully reinstall again... this reinstallation stuff will hopefully be going away, soon)

Well, I found three hardcore bugs in v0.88.  Not security-related bugs, but the kind of bugs that prevent users from using the software.  At all.   These should've been caught during testing!  Please help test.  Especially in Linux, if you are running from the git repo, just keep yourself on the testing branch and pull occasionally.  I promise only to update the testing branch after a lot of internal testing.

Fixes:

• Unicode issues in settings window:  I missed a unicode fix which prevented some users from opening the settings dialog at all.  This meant that you couldn't set Bitcoin-Qt installation or home directories
• "rpcport" in bitcoin.conf:  Users who specified any rpcport argument in their bitcoin.conf file, would result in failed loading with auto-bitcoind.  There really was no workaround for this
• Importing addresses:  Another major Armory feature that was botched with a recent upgrade.  You simply could not import addresses into an encrypted wallet.  At all.  Unencrypted wallets imported fine.
• Clean shutdown on Linux:  It turns out I accidentally used functions in the python-psutil module that do not exist natively in older versions.  This caused the auto-bitcoind management to leave bitcoind open even after Armory was closed, in older Linux versions.   Granted, that might be good for some users... but it's not intended behavior (this is part of my goal to keep Armory dependency-version-less: making it easy to compile on just about any system)

So, I spent a couple hours creating scripts to streamline the release process, and it definitely made it a lot easier.  The offline computer now signs the .debs, and also repackages the offline bundle, and automatically produces the *.sha256sum.asc file and signs it (after I manually verify hashes between all my computers/VMs).   So, this process hopefully won't be so painful in the future, and the offline bundle will be reproduced automatically on every release.  But it's still not pleasant.

So, I just posted the updated installers to the Download (https://bitcoinarmory.com/get-armory/) page.  I re-linked them at the bottom of this post, because my script automatically emits the BBCode for me, and so it just one copy&paste.

---

All the signed installers:

Version 0.88.1-beta for Ubuntu/Debian 64-bit (https://bitcoinarmory.googlecode.com/files/armory_0.88.1-beta_amd64.deb)
Version 0.88.1-beta for Ubuntu/Debian 32-bit (https://bitcoinarmory.googlecode.com/files/armory_0.88.1-beta_i386.deb)
Version 0.88.1-beta for Windows 64-bit (https://bitcoinarmory.googlecode.com/files/armory_0.88.1-beta_win64.msi)
Version 0.88.1-beta for Windows 32- and 64-bit (https://bitcoinarmory.googlecode.com/files/armory_0.88.1-beta_win32.msi)
Version 0.88.1-beta for Mac/OSX 10.8 (https://bitcoinarmory.googlecode.com/files/armory_0.88.1-beta_OSX.dmg)
Version 0.88.1-beta SHA256 hashes of installers (https://bitcoinarmory.googlecode.com/files/armory_0.88.1-beta_sha256sum.txt.asc)
Version 0.88.1-beta Offline Bundle for Ubuntu 10.04-32bit (https://bitcoinarmory.googlecode.com/files/armory_0.88.1-beta_OfflineBundle_Ubuntu-10.04-32bit.tar.gz)
Version 0.88.1-beta Offline Bundle for Ubuntu 10.04-64bit (https://bitcoinarmory.googlecode.com/files/armory_0.88.1-beta_OfflineBundle_Ubuntu-10.04-64bit.tar.gz)

Is this the "offical" 0.88 version?

The "official" one was yesterday.  But I missed these show-stopper bugs, so I decided to go through the whole thing again today.  It was annoying, but I really couldn't leave it in an usuable state for so many.

I updated the webpage, but didn't re-trigger notifications.  I didn't want to spam people who already upgraded.  They'll probably find the upgrade themselves if they were affected by any of those bugs.