Armory Installation on Linux Mint version 22.2

[matrix01]

I am building a new Armory Cold storage environment from scratch so I can relearn how to operate the software in a sandbox setup. My Online Broadcasting laptop runs on Cinnamon Linux Mint version 22.2 OS and I had no problem installing Bitcoin Knots and syncing it 100% to the blockchain. I have not yet setup my Air-Gapped laptop but when I do it will also be running Linux Mint version 22.2 OS with the same armory_0.96.5_amd64_gcc7.2.deb file installed.

Nevertheless, I have encountered a problem with Armory version 0.96.5 installation. I downloaded the armory_0.96.5_amd64_gcc7.2.deb file from the link below:

https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.5

And when I tried installing the deb file by right mouse clicking on it and selecting "Open with Package Installer" a window appears showing the message shown below: 

Error: Dependency is not satisfiable: python (>=2.6).

My Linux Mint OS already has python v3.12.3 installed and if v3 is greater than v2 why does this python dependency error appear? 

In short, I hope somebody in this forum community can advise me on what is the correct way to install the armory_0.96.5_amd64_gcc7.2.deb file so I can work around this python dependency problem within the Linux Mint v22.2 OS environment.  Thank you for your time.

[ABCbits]

And when I tried installing the deb file by right mouse clicking on it and selecting "Open with Package Installer" a window appears showing the message shown below:  

Error: Dependency is not satisfiable: python (>=2.6).

My Linux Mint OS already has python v3.12.3 installed and if v3 is greater than v2 why does this python dependency error appear?  

Most linux distro doesn't ship Python 2 on their repository these days. You'll need to find different way to install Armory. In addition,
1. Program written on Python 2 sometimes does not run on Python 3.
2. Most (or maybe all) linux distro use different package name for Python 2 and Python 3. Here's example from Debian,
https://packages.debian.org/bullseye/python2
https://packages.debian.org/stable/python3

[matrix01]

Thank you for your post ABCbits, and from what I gather the last version when Linux Mint OS supported Python 2.6 was Linux Mint Version 17.x. And this fact prompts me to kindly request the following questions be addressed:

As of today, is Armory still considered a fully operational cold storage solution where one can still securely broadcast any BTC transaction utilizing both the Air-Gapped Armory PC and the Online Armory PC?

I ask this question because Python version 2.6 is obsolete and this makes me wonder if Armory is still a secure and/or an operational cold storage solution being that it still relies on an obsolete, no longer supported Linux Mint v17.x OS / Python v2.6 version to work. In short, is Armory now too risky to use for what it was originally designed to do?

Please bear with me, but I am trying to get up to speed with Armory because the last time I used Armory was when Python 2.6 was the default install used in Linux Mint OS. Therefore, it is not clear to me if GoatPig has any plans to update Armory so it runs on Python v3.12.3. Or what currently are the best workarounds one can implement today to get Armory to work correctly?

Lastly, is anybody out there running Linux Mint OS with Python v3.12.3 and Python v2.6 concurrently in the same Linux Mint OS?  Will such a Linux Mint setup work and allow me to operate Armory for relearning purposes in a test environment? Any advice welcome and thank you for your time.

[matrix01]

I have spent a considerable amount of time researching this matter since my last post and I now have some followup questions I hope somebody in this community can answer:

First, I looked at installing PYENV Python version management software onto my LM v22.2 OS and from what I gather this will not fix the Armory installation Python v2.6 dependency error because this dependency error comes from the Debian packaging system (dpkg/apt), which only recognizes system packages, and not pyenv-managed Pythons. So, I think this option is a dead end unless somebody in this forum can tell me otherwise.

Second, I looked into installing Armory into a docker container that also has an old Linux Mint OS version 17.x with Python version 2.6 installed in the container as well.  Is this the correct approach to use for installing Armory in 2025?  The problem I see is I have Bitcoin Knots running within the Linux Mint 22.2 OS and I don't see how Armory is going to communicate with Bitcoin Knots considering Armory is operating from within a docker container. 

In closing, I will be very grateful if an Armory super user in this forum can provide advice to me that is specific to what is the correct approach to use for installing Armory version 0.96.5 onto a Linux Min v22.2 Operating System. Thank you for your time.

[nc50lc]

As of today, is Armory still considered a fully operational cold storage solution where one can still securely broadcast any BTC transaction utilizing both the Air-Gapped Armory PC and the Online Armory PC?

It's still can, but its latest release is quite dated.

On a side note, its requirement Bitcoin Knots/Core can now do that with its watch-only descriptor wallet and an offline descriptor wallet.
Signed/Unsigned transactions are transferred in PSBT format.
You may consider it if you're having trouble setting up Armory.

[ABCbits]

I am building a new Armory Cold storage environment from scratch so I can relearn how to operate the software in a sandbox setup.

If you don't insist using Armory, consider using different wallet that have feature needed for cold/airgapped wallet such as Electrum. It's actively developed and more popular.

Please bear with me, but I am trying to get up to speed with Armory because the last time I used Armory was when Python 2.6 was the default install used in Linux Mint OS. Therefore, it is not clear to me if GoatPig has any plans to update Armory so it runs on Python v3.12.3. Or what currently are the best workarounds one can implement today to get Armory to work correctly?

Looking at https://bitcointalk.org/index.php?topic=5544491.msg65420662#msg65420662, it seems he's working for Python 3 support. You could try build and install Armory from source code from latest commit, but no guarantee it'll make Armory work correctly/properly.

First, I looked at installing PYENV Python version management software onto my LM v22.2 OS and from what I gather this will not fix the Armory installation Python v2.6 dependency error because this dependency error comes from the Debian packaging system (dpkg/apt), which only recognizes system packages, and not pyenv-managed Pythons. So, I think this option is a dead end unless somebody in this forum can tell me otherwise.

I DO NOT recommend it, but i managed to install Armory on my Debian 12 device using this step. Obviously armory won't run, since some dependency are missing.

Code:

$ sudo dpkg -i armory_0.96.5_amd64_gcc7.2.deb Selecting previously unselected package armory.
(Reading database ... 377302 files and directories currently installed.)
Preparing to unpack armory_0.96.5_amd64_gcc7.2.deb ...
Unpacking armory (0.96.5-1) ...
dpkg: dependency problems prevent configuration of armory:
 armory depends on python (>= 2.6); however:
  Package python is not installed.
 armory depends on python-qt4; however:
  Package python-qt4 is not installed.
 armory depends on python-psutil; however:
  Package python-psutil is not installed.

dpkg: error processing package armory (--install):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.36-9+deb12u10) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Errors were encountered while processing:
 armory
$ armory
/usr/bin/armory: line 5: exec: python2: not found

[goatpig]

I have spent a considerable amount of time researching this matter since my last post and I now have some followup questions I hope somebody in this community can answer:

First, I looked at installing PYENV Python version management software onto my LM v22.2 OS and from what I gather this will not fix the Armory installation Python v2.6 dependency error because this dependency error comes from the Debian packaging system (dpkg/apt), which only recognizes system packages, and not pyenv-managed Pythons. So, I think this option is a dead end unless somebody in this forum can tell me otherwise.

Second, I looked into installing Armory into a docker container that also has an old Linux Mint OS version 17.x with Python version 2.6 installed in the container as well.  Is this the correct approach to use for installing Armory in 2025?  The problem I see is I have Bitcoin Knots running within the Linux Mint 22.2 OS and I don't see how Armory is going to communicate with Bitcoin Knots considering Armory is operating from within a docker container. 

In closing, I will be very grateful if an Armory super user in this forum can provide advice to me that is specific to what is the correct approach to use for installing Armory version 0.96.5 onto a Linux Min v22.2 Operating System. Thank you for your time.

pyenv wont save you, you still need to install pyqt4, and that is unlikely to work with modern compositors. It surely will choke with wayland, and it's debatable whether it can survive x-wayland. Arguably, I haven't tried this solution directly, but I have my doubts.

It would take less effort to build from the dev branch and run the modern version of Armory. If you insist on running 0.96.5, you're better off dockerizing it, and serviing it a X server socket for the GUI.

Sorry for the succinct reply, I am traveling for the another 3 weeks.

[matrix01]

Thank you to all for your posts. Considering Goatpig is traveling for the next 3 weeks can somebody be so kind to clarify what he means by “modern version of Armory”.  Isn’t the most modern Armory version available for download located at the link below? Or is there some other Armory version out there online that is more modern that supports Python 3.12? If yes I would like to know where online could I find it?

https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.5

Please bear with me, my air-gapped Armory PC has Armory v0.92.3 installed and runs on an Ubuntu v12.04 LTS Operating System. If I decide to migrate my private keys out of this air-gapped PC and over to an air-gapped Coldcard-Q hardware wallet should I consider upgrading my air-gapped Armory PC from Armory v0.92.3 to Armory v0.96.5? In other words, does such an upgrade offer any newer software features that makes a possible private key migration more directly compatible with the BIP39 private key format Coldcard utilizes?  Or is remaining on Armory v0.92.3 adequate enough to perform an entire private key migration over to a ColdCard-Q as smoothly as it would get done using the newer Armory v0.96.5?

Any opinions welcome.

[nc50lc]

Thank you to all for your posts. Considering Goatpig is traveling for the next 3 weeks can somebody be so kind to clarify what he means by “modern version of Armory”.  Isn’t the most modern Armory version available for download located at the link below? Or is there some other Armory version out there online that is more modern that supports Python 3.12? If yes I would like to know where online could I find it?

Oh, what he meant by "Dev Branch" is the code containing the latest changes.
It should be selected by default if you go to Armory's GitHub repository, double-check if "dev" is selected in the drop-down menu on the left.
To manually download, click "Code->Download Zip" (source code only)

Any opinions welcome.

For the private keys, there's no difference between v0.92.3 and v0.96.5.
Both use uncompressed WIF private key.

[matrix01]

Thank you for your post Nc50lc.

I performed and “Export Key Lists” operation in my air-gapped Armory PC environment to see for myself what a WIF looks like.  The exported key list text file shows data labeled as: PrivBase58, PrivHexBE, PublicX, and a PublicY. But it does not show any key labeled “WIF” but after some research I learned a PrivBase58 is the same thing as a WIF. However, I am not clear what is the purpose of the PrivHexBE as it relates to migrating my PrivBase58 key into Sparrow wallet so it can eventually end up in an air-gapped ColdCard-Q.   Does any Armory super user in this forum know whether or not a PrivHexBE key in any way plays a role in migrating my PrivBase58 key over to ColdCard-Q hardware wallet? Or can the PrivHexBE key, PublicX key, and the PublicY key be ignored as it relates to migrating a PrivBase58 key over to a ColdCard-Q?

Lastly, does any Armory Super User know of the existence of an online tutorial (video or written) that shows the process of migrating Armory PrivBase58 and/or PrivHexBE keys to a Sparrow Wallet and then from here migrate it over to a ColdCard-Q hardware wallet?  If I could get my hands on such a tutorial my stress level while performing such a migration process will decrease by a factor of 100.    Thank you for your time any opinions welcome.

[nc50lc]

I performed and “Export Key Lists” operation in my air-gapped Armory PC environment to see for myself what a WIF looks like.

You don't have to use those "PrivHexBE" since it's in a raw format that wallets don't usually support.
WIF (Wallet Import Format) is the one you need which is equivalent to those "PrivBase58" in your export list (omit the spaces).

As for my note about uncompressed, wallets are specific on which public key format to use to derive your addresses.
Since armory is using uncompressed WIF, it doesn't contain a "compressed flag" which tells the wallet to derive the uncompressed public key from that private key.
So, use those WIF prvKeys in their presented format to automatically match the correct addresses upon import.
(excluding P2SH-P2PK that most wallets do not support, Bitcoin Core can though via "importdescriptors")

Lastly, I can't help much about ColdCardQ since I don't have it,
But for Sparrow, it's not possible to import loose private keys to that wallet, it needs to be HD (via seed phrase, descriptor or master private key)
One of your cold-storage option that supports individual prvKey import would be Electrum (e.g.;cold-storage method), then send the bitcoins to your ColdCard.