When there'll be next release? What is the status of `testing` branch?

[dpc]

Hi,

Sorry for using github issues, but there are very little updates on the project in last few months.

I can see that testing is busy, but I'm just wondering are there any estimates when Armory will receive next (even beta) release? Is testing even usable ATM, or is it going to munch private keys, corrupt wallets and blow computer screens? ;)

Best Regards, Dawid

[etotheipi]

The "testing" branch is very usable. In fact, I request that you use it -- I've been using it exclusively for over a month and been doing tons of transactions on it. So far we have seen no issues with it in any dimension except usability (surprise!). The DB gets corrupted sometimes, requiring a rebuild, and occasionally a zero-conf tx disappears and doesn't recover even after a block (requires a rescan). Both of these are tough to track down and I'm doing my best to get 'em fixed. But beyond that, there hasn't even been a hint of a problem with the functionality once it's working properly.

[dpc]

OK. Thanks. Will try this.

[dpc]

I was able to compile on Fedora 19 and seems now running and syncing. Thanks.

[FluxSine]

Hey There, I'm trying to install on fedora 19 just wondering if you can walk me through it. What other libraries do i need to install before I run make inside BitcoinArmory?

[dpc]

Just try building and install things that are missing. The python settings file had to be created from the scratch, IIRC. But I don't have an access to desktop ATM. I'll paste it latter.

[FluxSine]

Hmm well the issue I'm having is i run make and i get a blinking square so I can't see whats not working.

[FluxSine]

I take that back i do make and i get cd cppForSwig; make swig followed by a blinking cursor. any thoughts ?

[goatpig]

You need to install the Fedora packages that are equivalent to the Debian packages listed.

On 12/5/2013 12:55 AM, FluxSine wrote:

I take that back i do make and i get cd cppForSwig; make swig followed by a blinking cursor. any thoughts ?

— Reply to this email directly or view it on GitHub https://github.com/etotheipi/BitcoinArmory/issues/119#issuecomment-29858786.

[dpc]

% git diff
diff --git a/cppForSwig/Makefile b/cppForSwig/Makefile
index ba6cc45..f5c96d3 100755
--- a/cppForSwig/Makefile
+++ b/cppForSwig/Makefile
@@ -17,7 +17,7 @@ OBJS = UniversalTimer.o BinaryData.o leveldb_wrapper.o StoredBlockObj.o BtcUtils
 # pypaths.txt to define those three variables, and then comment out 
 # DO_EXEC_WHEREISPY line (to prevent the script from attempting to run
 # and overwriting the manual values).
-DO_EXEC_WHEREISPY := $(shell ./whereispy.sh)
+#DO_EXEC_WHEREISPY := $(shell ./whereispy.sh)

 include ./pypaths.txt

% cat cppForSwig/pypaths.txt 
PYTHON_INCLUDE += /usr/include/python2.7/
PYTHON_LIB += -lpython2.7
PYVER += python2.7

That's all what is needed to build on F19 (+ packages of course)