Bug#884417: python-trezor v0.9.0 tagged - next steps?

[Tristan Seligmann]

I have a fixed version prepared in git now, but it looks like we need to
wait for Electrum 3.1.0 to be released as 3.0.6 is not compatible with
python-trezor 0.9.0

On Tue, 27 Feb 2018 at 06:55 Jonathan Cross  wrote:

> >  I'll try to take care of it this week.
>
> Fantastic, thanks Tristan!
>

Bug#884417: python-trezor v0.9.0 tagged - next steps?

[Jonathan Cross]

>  I'll try to take care of it this week.

Fantastic, thanks Tristan!

Bug#884417: python-trezor v0.9.0 tagged - next steps?

[Tristan Seligmann]

On Mon, 26 Feb 2018 at 21:20 Andreas Beckmann  wrote:

> This is what I understood from reading debian/{changelog,control} and
> the upload notifications on the qa page [1]: the package was split with
> the 0.7.16-1 upload, but lacks proper Breaks+Replaces for the files
> being moved around.
>

Yes, this is a relatively straightforward fix, sorry for the delay in
implementing it! I'll try to take care of it this week. It's just an issue
with the Debian packaging, not the upstream portion.

Bug#884417: python-trezor v0.9.0 tagged - next steps?

[Andreas Beckmann]

[ adding the bug back into the loop, please keep it Cc:ed ]

On 2018-02-26 19:23, Jonathan Cross wrote:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884417
> 
> What would be the next steps in getting past this?
> 
> How can we indicate that '/usr/bin/trezorctl' should be replaced?

In debian/control, in the 'Package: trezor' stanza, add

Breaks: python-trezor (<< 0.7.16)
Replaces: python-trezor (<< 0.7.16)

Disclaimer: completely untested!

This is what I understood from reading debian/{changelog,control} and
the upload notifications on the qa page [1]: the package was split with
the 0.7.16-1 upload, but lacks proper Breaks+Replaces for the files
being moved around.

[1] https://packages.qa.debian.org/p/python-trezor.html


Andreas