Package Details: armory-git v0.96.5.r0.g1d02a664-1

Git Clone URL: https://aur.archlinux.org/armory-git.git (read-only, click to copy)
Package Base: armory-git
Description: Full-featured Bitcoin wallet management application
Upstream URL: https://github.com/goatpig/BitcoinArmory
Licenses: MIT, AGPL3
Conflicts: armory, armory-bin, armory-goatpig-git
Provides: armory
Submitter: jgottula
Maintainer: jon
Last Packager: jon
Votes: 17
Popularity: 0.000000
First Submitted: 2012-01-10 07:04 (UTC)
Last Updated: 2019-02-19 18:36 (UTC)

Latest Comments

1 2 3 4 5 6 Next › Last »

bobpaul commented on 2022-10-10 23:18 (UTC)

This package conflicts with fcgi.

zovo commented on 2018-12-27 21:28 (UTC)

I've got this error: checking for pythonVersione... no configure: error: Cannot find pythonVersione : 2.7 in your system path

What can I do for solve this problem?

uncle commented on 2017-11-14 21:55 (UTC)

Digger, this is probably happening because you have previously installed armory using a different package name (probably armory-bin, which I will add to the conflicting packages). Uninstall the old one first, then try installing this package again.

digger commented on 2017-11-10 02:54 (UTC)

It looks like there are packages that conflict: $ sudo pacman -U armory-goatpig-git-v0.96.3.r0.g2b65ac06-1-x86_64.pkg.tar.xz loading packages... resolving dependencies... looking for conflicting packages... Packages (1) armory-goatpig-git-v0.96.3.r0.g2b65ac06-1 Total Installed Size: 30.60 MiB :: Proceed with installation? [Y/n] (1/1) checking keys in keyring [######################] 100% (1/1) checking package integrity [######################] 100% (1/1) loading package files [######################] 100% (1/1) checking for file conflicts [######################] 100% error: failed to commit transaction (conflicting files) armory-goatpig-git: /usr/include/fastcgi.h exists in filesystem armory-goatpig-git: /usr/include/fcgi_config.h exists in filesystem armory-goatpig-git: /usr/include/fcgi_stdio.h exists in filesystem armory-goatpig-git: /usr/include/fcgiapp.h exists in filesystem armory-goatpig-git: /usr/include/fcgimisc.h exists in filesystem armory-goatpig-git: /usr/include/fcgio.h exists in filesystem armory-goatpig-git: /usr/include/fcgios.h exists in filesystem armory-goatpig-git: /usr/lib/libfcgi.so exists in filesystem armory-goatpig-git: /usr/lib/libfcgi.so.0 exists in filesystem armory-goatpig-git: /usr/lib/libfcgi.so.0.0.0 exists in filesystem Errors occurred, no packages were upgraded.

resetko commented on 2017-10-29 20:28 (UTC)

got this error during compilation CppBlockUtils_wrap.cxx: In function 'PyObject* _wrap_BtcUtils_hash256(PyObject*, PyObject*)': CppBlockUtils_wrap.cxx:28661:17: error: 'PyString_FromStringAndSize' was not declared in this scope resultobj = PyString_FromStringAndSize((char*)((&result)->getPtr()), (&result)->getSize()); ^~~~~~~~~~~~~~~~~~~~~~~~~~

jon commented on 2017-10-13 03:01 (UTC)

A changelog for 0.96.3.99 (0.96.4 RC1) is available here: https://bitcointalk.org/index.php?topic=2227856.0

jon commented on 2017-09-22 22:32 (UTC) (edited on 2017-10-13 03:00 (UTC) by jon)

@s1kx Thanks! I've released these changes. There was a build issue previously, so it took a while to get a functional release out.

uncle commented on 2017-08-31 07:25 (UTC)

Updated to 0.96.2. With this release, Armory allows the use of segwit addresses. NOTE: The "coin control" bug I was experiencing appears to have been one unique to my wallet, and one which I have since remedied.

uncle commented on 2017-08-26 01:42 (UTC) (edited on 2017-08-27 16:46 (UTC) by uncle)

EDIT: Latest testing version is still freezing, use the stable version. There is a bug in 0.96.1 and 0.96.2 RC2 which, after using the "coin control" menu once to create a transaction, will cause Armory to freeze if you try to use the "coin control" menu again. This bug is fixed in the latest version of the testing repo (not in the 0.96.2 RC2 binary). if you wish to install the testing version (do so at your own risk, of course) you may do so by editing the PKGBUILD before installation, and adding "#branch=testing" (without the quotes) at the end of the "source" address. continue building the package, and it will install the latest version from testing. Again, do so at your own risk ;-)

uncle commented on 2017-08-26 01:36 (UTC)

@mmanjos I updated the PKGBUILD to fix the problem you pointed out, thanks for the feedback. the makefile assumes that qt4 version of lrelease is named "lrelease" but since Arch tends to be bleeding edge, it assumes qt5 is the default version, and installs the qt5 version of lrelease (included in the "qt5-tools" package) as "lrelease" and the qt4 version as "lrelease-qt4". Now the PKGBUILD updates the command in the makefile so that it uses the correct qt4 version when the package is compiled.