<<  >> (p.32)
    Author Topic: Armory - Discussion Thread  (Read 522407 times)
    etotheipi (OP)
    Legendary
    *
    Offline Offline

    Activity: 1428
    Merit: 1110


    Core Armory Developer


    View Profile WWW
    April 20, 2012, 04:09:27 PM
     #621

    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...

    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.

    Well, the dependency in that case was wrong.  It needs to be =2.6, because the library was compiled with libpython2.6, which causes fatal problems with the program if the user only has python2.7. 

    Make sure you "dpkg -r armory" before trying.  I just want to make sure you don't add complications by having mixed version of the package.  I haven't figured out how to get dpkg-builder to increment the debian build numeber (i.e. increase it from "armory_0.74-1" to "armory_0.74-2").  One more thing to work on...

    Founder and CEO of Armory Technologies, Inc.
    Armory Bitcoin Wallet: Bringing cold storage to the average user!
    Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

    Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
Page 31
Viewing Page: 32