$ sudo python3 setup_federated_node.py
[sudo] password for xcp:
It appears this setup has been run already. ®ebuild node, or just (U)pdate from git? (r/U): r
Enter the number for the role you want to build:
1: Counterwallet server
2: Vending machine
3: Blockexplorer server
4: counterpartyd-only
5: BTCPay Escrow Server
Your choice: 1
Building a Counterwallet server
Build from branch (M)aster or (d)evelop? (M/d): M
Working with branch: master
Run as (t)estnet node, (m)ainnet node, or (B)oth? (t/m/B): B
Setting up to run on testnet and mainnet
Blockchain services, use (B)lockr.io (remote) or (i)nsight (local)? (B/i): B
Using blockr.io
Email address where support cases should go (blank to disable):
Set up security hardening? (Y/n): n
I get this:
Traceback (most recent call last):
File "setup_federated_node.py", line 885, in
main()
File "setup_federated_node.py", line 860, in main
do_counterparty_setup(role, run_as_user, answered_questions['branch'], base_path, dist_path, answered_questions['run_mode'],
NameError: name 'role' is not defined
It's Ubuntu 14.04 x64.
I got the rebuild prompt the first time I ran the script (which is wrong), too.
Are you building from the develop branch?
[quote author=weex link=topic=505.msg3131#msg3131 date=1408753164]
Are you building from the develop branch?
[/quote]
From my post:
> Build from branch (M)aster or (d)evelop? (M/d): M Working with branch: master
I was using Master.
Late yesterday xnova said Master was screwed up and he fixed it, I will retry to see whether I still run into this.
So far it's been running longer (I think) so I believe updates he made Friday afternoon/evening fixed the problem, so I will post here again only if the problem has not been resolved. Thanks!
P.S. Rich formatting in this forum s/w isn't very useful…
It makes better progress, but it still cannot complete…
2014-08-23 15:36:31,831|DEBUG: RUNNING COMMAND: dpkg -i /tmp/armory.deb
(Reading database … 87537 files and directories currently installed.)
Preparing to unpack /tmp/armory.deb …
Unpacking armory (0.92.1-1) over (0.92.1-1) …
xdg-icon-resource: No writable system icon directory found.
dpkg: warning: subprocess old post-removal script returned error exit status 3
dpkg: trying script from the new package instead …
xdg-icon-resource: No writable system icon directory found.
dpkg: error processing archive /tmp/armory.deb (–install):
subprocess new post-removal script returned error exit status 3
xdg-icon-resource: No writable system icon directory found.
dpkg: error while cleaning up:
subprocess new post-removal script returned error exit status 3
Processing triggers for mime-support (3.54ubuntu1) …
Errors were encountered while processing:
/tmp/armory.deb
2014-08-23 15:36:33,532|ERROR: Command failed: 'dpkg -i /tmp/armory.deb'
It seems a temp workaround is to use "develop" instead of "master".
Next I'll build from develop.