Bug#824766: armory: New home for armory and new upstream release

2017-03-29 Thread Marco Balmer
The issue [1] on github seems to be closed and armory has signed git
tags now [1].

[1] https://github.com/goatpig/BitcoinArmory/issues/40
[2] 
https://github.com/goatpig/BitcoinArmory/releases/download/v0.95.1/sha256sum.asc

I think you could go on here - Correct?

Marco


signature.asc
Description: Digital signature


Bug#824766: armory: New home for armory and new upstream release

2016-05-19 Thread Joseph Bisch
On Thu, May 19, 2016 at 09:33:17AM -0600, Joseph Bisch wrote:
> On Thu, May 19, 2016 at 04:15:02PM +0200, Diederik de Haas wrote:
> > As can be read in the links from this issue
> > https://github.com/etotheipi/BitcoinArmory/issues/325 Armory
> > Technologies has stopped working on armory, at least for the time being.
> > As can be read in the linked threads, there is now a fork which seemed
> > to be (somewhat) official, namely
> > https://github.com/goatpig/BitcoinArmory and there have been several
> > releases there, the latest being 0.94.1.
> > 
> > Maybe it's a good idea to switch the Debian package to the fork?
> 
> Yes, I would say that Goatpig's fork is the most official version of
> Armory in development currently. He was the defacto maintainer of the
> open source version of Armory at Armory Technologies up until the
> company stopped development.
> 
> I won't be able to get to this myself before the weekend at the
> earliest (just moved and going to be starting a new job). Patches to
> package 0.94.1 are welcome from anyone. Just be sure to base the
> packaging off of the pkg-bitcoin repo[0].

I actually got to take a look at this. I decided not to package new
versions of Armory until the git tags are signed to verify the integrity
of the source code (e.g. so GitHub or someone with access to GitHub's
servers cannot modify the code). I have filed a bug[0] upstream asking
for Goatpig to sign tags. I hope to be able to package 0.94.1 and future
versions of Armory soon, but without signed tags, I think it would be
irresponsible of me to package financial software. I just filed the bug
upstream, so it might be a while before I hear back from Goatpig.

[0] - https://github.com/goatpig/BitcoinArmory/issues/40

Joseph



Bug#824766: armory: New home for armory and new upstream release

2016-05-19 Thread Joseph Bisch
On Thu, May 19, 2016 at 04:15:02PM +0200, Diederik de Haas wrote:
> As can be read in the links from this issue
> https://github.com/etotheipi/BitcoinArmory/issues/325 Armory
> Technologies has stopped working on armory, at least for the time being.
> As can be read in the linked threads, there is now a fork which seemed
> to be (somewhat) official, namely
> https://github.com/goatpig/BitcoinArmory and there have been several
> releases there, the latest being 0.94.1.
> 
> Maybe it's a good idea to switch the Debian package to the fork?

Yes, I would say that Goatpig's fork is the most official version of
Armory in development currently. He was the defacto maintainer of the
open source version of Armory at Armory Technologies up until the
company stopped development.

I won't be able to get to this myself before the weekend at the
earliest (just moved and going to be starting a new job). Patches to
package 0.94.1 are welcome from anyone. Just be sure to base the
packaging off of the pkg-bitcoin repo[0].

[0] - https://anonscm.debian.org/cgit/pkg-bitcoin/armory.git/

Cheers,
Joseph



Bug#824766: armory: New home for armory and new upstream release

2016-05-19 Thread Diederik de Haas
Package: armory
Version: 0.92.3-1+b2
Severity: normal

As can be read in the links from this issue
https://github.com/etotheipi/BitcoinArmory/issues/325 Armory
Technologies has stopped working on armory, at least for the time being.
As can be read in the linked threads, there is now a fork which seemed
to be (somewhat) official, namely
https://github.com/goatpig/BitcoinArmory and there have been several
releases there, the latest being 0.94.1.

Maybe it's a good idea to switch the Debian package to the fork?

Cheers,
  Diederik


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(101, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages armory depends on:
ii  bittornado 0.3.18-10.2
ii  libc6  2.22-9
ii  libcrypto++6   5.6.3-6
ii  libgcc11:6.1.1-3
ii  libleveldb1v5  1.18-5
ii  libstdc++6 6.1.1-3
ii  python-psutil  4.1.0-1
ii  python-qt4 4.11.4+dfsg-1+b3
ii  python-qt4reactor  1.0-1
ii  python-twisted 16.1.1-1
ii  python2.7  2.7.11-9
pn  python:any 
ii  xdg-utils  1.1.1-1

Versions of packages armory recommends:
ii  bitcoind  0.11.2-1

armory suggests no packages.

-- no debconf information