[Pkg-bitcoin-devel] Armory - Looking for Sponsor

[Tristan Seligmann]

On 8 October 2014 16:49, Joseph Bisch <joseph.bisch at gmail.com> wrote:
>> 2) The git repository referenced in debian/control does not have your
>> latest changes. I think if you join pkg-bitcoin on Alioth, we could
>> move this into a repository under pkg-bitcoin.
>
> I requested to join pkg-bitcoin on Alioth. The reason the git
> repository currently in debian/control is out of date is that I was
> having some problems with git-buildpackage. When I would make changes
> and try to reimport the dsc I ended up with multiple commits saying
> that I imported the version. I would git reset hard, but gbp would
> somehow retain the history and restore it when I import the dsc again.
> So my solution is to wait until I finish working on a version and then
> import the dsc just once. I guess I can import the upstream source and
> do development in the git repo instead of importing the dsc.

I'm not that familiar with using import-dsc on an existing repository.
I expect there's some way to make it work, but I don't think it's too
important preserving this initial history, so a single import once the
package is initially uploaded should be fine.

> I was able to fix this by adding a patch that changes the line to
> "upnp_type = 0" (which I got from the bittornado source in Debian). I
> was able to download the torrent up to 10% (then I stopped it). So I
> assume the issue is fixed.

Yes, it seems to be working here too.

> I reuploaded Armory to mentors[0] with all the changes you mentioned
> in your email.

I'm doing some final checking on the package, but so far everything
looks good, so I will probably upload it later today if I don't find
any other issues. In the meantime I created a git repository under
pkg-bitcoin on Alioth; I will try to pull the upstream git repository
in for the upstream branch rather than using gbp import-orig as this
way the upstream tag signatures can be verified more easily.
-- 
mithrandi, i Ainil en-Balandor, a faer Ambar