Okay, now that github has started working again, let's have a look here...

Uh, I think there's still some work to be done on that dependency list:
You mean Armory doesn't require Qt4 any more?

Also, your .desktop files are invalid. "Categories=GNOME;Applications;Internet;" should be changed to "Categories=Qt;Network;", since "GNOME" is not a main category (and Armory is based on Qt, not GNOME) and neither "Applications" nor "Internet" are valid categories at all. Since there is no valid main category specified, KDE just dumps the menu entries in "Lost & Found". For reference, a list of valid menu categories can be found here.

Other than those major flaws it's all good.

It seems that when compiling from source, it uses whatever version of libpython you happen to have, but the binary in the Debian package is dynamically linked to libpython2.6. I don't see a solution as long as Armory needs to be dynamically linked to libpython.

I'm pretty sure python programs don't need executable permissions. At least they don't in python 2.6...

That's because you can't have python 2.6 and 2.7 both installed on the same system, so any given distro will only have one or the other. Sucks. (You can downgrade from 2.7 to 2.6 if you change your distro settings, but installing packages from a different distro almost always ends in tears. I do not recommend you attempt this.)

Great!

Could you propose your package to Debian, to be included in the official repositories?


Ciao!

Agreed.  It will be a while before this even becomes a candidate for an official package.  There's a lot of work to do.

Speaking of which, I'm obviously quite disappointed with the lack of success of these packages.  It sounds like I'd have to compile a different version for python 2.5, 2.6 and 2.7, and amd64 and i386.  That's at least 6 packages (and 6 configurations I need)    For now, I actually can support amd64-python2.6 and amd64-python2.7.  And probably the equiv for i386.

Is there a way to set up the package for install and make-install instead of dumping the binaries in the package instead?  I mean, I know someone can just download the source and do that, but obviously I want to find a way to make this easily supported.  

In the end, were all problems related to the python issue?  

Foxpup,

Thanks for that link.  I tried lots of different things in the "Categories" field and nothing worked.  I eventually found a website that said "You have to use GNOME;Applications:...;", so that's what I did, even though it didn't improve the situation.  

Clearly something was wrong with the dependencies, but it still worked on my system, so I thought I'd throw it out there to find out that no one else could use it, anyway.  I'll try to get that all straightened out today.  If you used the package and you were successful, please let me know!  All I've heard is unsuccess!

-Alan

Actually, I meant that my .deb file produced on 10.04 with python2.6 worked on Ubuntu 11.10 which uses python 2.7 and it worked when I manually installed the dependencies.  Which is why I posted the apt-get installer line in my original .deb posting.

As for dependencies, I noticed that I had all my dependencies on the "Build-Depends" line, and no "Depends" line.   I'm trying to get dependencies worked out, but every time I compile the .deb, it overwrites my depends line and puts it's own in there.  Definitely needs some improvement.

Btw, your suggestion for Categories seems to have worked... almost.  I now have 2 of the 3 icons under my "Internet" tab, but the other one somehow ends up in "Other" anyway.  I think I may have messed up my menu

Working on the dependencies thing now...

Okay!  I think I got it!  

Please execute "sudo dpkg -r armory" before attempting to install this package.  Since the version number didn't increment, your system may be confused by this...

If you had problems before, please try it again by downloading the appropriate version from the downloads page.

• It looks like dependencies worked this time.  I used the short list produced by Foxpup.  I tested it on a mostly-fresh system and got the appropriate errors.  Double-clicking and letting the Ubuntu package manager deal with it did result in those dependencies being installed.
• Menu options now show up in the "Internet" menu on my computer.  Thanks again to Foxpup for that.
• There is now a separate version for python2.6 and python2.7.   For me, the python2.6 version worked on my 11.10 system with python2.7, but clearly others were having problems.  So I compiled it again on the 11.10 system and posted the .deb file as well.  The packages are marked with arch and python version.

As for the menu options:  it is just my main system where the menu got screwed up.  When I install the package on a [mostly-]fresh new system, the menu options appear as expected.  Please let me know...

P.S. -- Foxpup, I installed nothing extra in the Ubuntu 11.10 system.  "python --version" replies with "Python 2.7.2+".  And when I run the .deb package everything goes smoothly and it works.  It does look like I have python2.6 libraries on that system... that would explain it...  (libpython2.6.so.1.0)

Gah!  I added python to the version number, but forgot to automate the depends line.  This really is a PITA!  I just replaced that version on the downloads page.  It should be correct.

At least I'm getting these stupid little things out the way before I declare a real release...

Hey, wait a minute, if that's all it was, then it shouldn't have worked at all, because I don't have python 2.7, so the python version obviously doesn't make any difference at all. Where exactly did psy's error come from? You know what, just remove libpython from the dependency list, put up one version per architecture, and see if that works on both my and psy's system. If it does, problem solved. Except for the problem of why it didn't work on psy's system originally after he hacked the dependencies, that trick should have worked...

Also, I've discovered a bug in the handling of white-on-black color schemes, and it's a big one. When printing a paper wallet, it turns out that white text does not actually make it easier to read.

Strictly speaking, it requires any localhost version of bitcoin to be running.  It can be bitcoin-qt or bitcoind.  As long as there is a localhost node to do blockchain validation and networking fanciness (peer-finding, blacklisting, address collection, etc).

So some form of bitcoin is technically required, but I can't put it in the depends list for fear that a distribution will not have it whatsoever, and then the package will be essentially uninstallable.

However, with packages out of the way, I can get on with doing my dev plans to get to Beta, which then will lead me to dealing with networking-independence (which will prob be the first priority after Beta).  Such update will also likely to lead to me removing some of my blockchain code and using the underlying library (libcoin, libbitcoin?) which will then allow it to work on all architectures smoothly:  Win32 included.

I believe I can stop thinking about debian packages for now.  If you are using Ubuntu, you can use the packages (which seem to work with mixed python no problem), and otherwise you can build from source.  You should be able to "make install" now, and then "chmod 755 dpkgfiles/postinst; dpkgfiles/postinst configure" in order to install the menu entries.   I haven't tested this, but if you're in a non-standard distribution, you are probably capable of handling the subtleties (please email me to work it out if there are problems).

Yeah, I was hoping that my dependencies hack would work. After all it asks for libpython2.6 or superior, doesn't it?
Isn't that what >=2.6 means? Equal or superior?

I will try it again and post results in a while.