From: Attila Lendvai <attila@lendvai.name>
To: Sarah Morgensen <iskarian@mgsn.dev>
Cc: 50751@debbugs.gnu.org
Subject: [bug#50751] [PATCH] gnu: update Trezor support
Date: Fri, 24 Sep 2021 11:05:00 +0000 [thread overview]
Message-ID: <DzDi6h_5spuoHXP0bdLYQbS6NY2DetR_lBnnR18-u0RUj_EQPWkzp8x6ZXxMIQYqNQBIA4ukzQXGeUtKDYBRHInV83zrfiZzd_W3xTfc3u8=@lendvai.name> (raw)
In-Reply-To: <86mto3kumt.fsf@mgsn.dev>
> > Fetch everything from their git repos, instead of pypi.
>
> Given the resulting version mismatch, and having to pick apart the
> sources, is there a compelling reason for this? It looks like the same
> files are included.
an objective reason: one of these versions were not in pipy at the
time i was working on this.
a subjective reason: one less organization to rely on. if anything
would happen to pipy, e.g. some random API change, then that wouldn't
affect us anymore. if github went down or went hostile, then we could
just change the git URL and continue with a minor glitch.
> > - gnu/packages/finance.scm (python-trezor-agent): Update to 0.14.2.
> >
> > (python-trezor): Update to 0.12.3.
> > (trezor-agent): Update to 0.11.0.
> > (trezord): Update to 2.0.31.
> > - gnu/packages/patches/trezor-agent-fix-argv0.patch: New file.
>
> When at all possible, version updates should be separate commits from changes.
ok, makes sense, because now that i think about it, it was broken with
the prior version, too. i'll resend it in two patches once i have tested them.
> > ;; overwrite the wrapper with the real thing.
> > (install-file "./trezor_agent.py"
> > - (string-append out "/bin"))
> > - #t))))))
> > - (string-append out "/bin")))
> > - #t)))))
>
> This wasn't added by your patch, but it's odd that the reason for
> overriding the wrapper wasn't documented....
i have added a comment explaining the situation.
thank you for the feedback! the updated patches will be coming a bit
later.
- attila
PGP: 5D5F 45C7 DFCD 0A39
next prev parent reply other threads:[~2021-09-24 11:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 8:30 [bug#50751] [PATCH] gnu: update Trezor support Attila Lendvai
2021-09-23 18:35 ` Sarah Morgensen
2021-09-24 11:05 ` Attila Lendvai [this message]
2021-09-24 11:05 ` [bug#50751] [PATCH 1/2] gnu: python-trezor-agent: Fix key generation with trezor-gpg init Attila Lendvai
2021-09-24 11:05 ` [bug#50751] [PATCH 2/2] gnu: update Trezor support Attila Lendvai
2021-11-28 20:35 ` bug#50751: " Nicolas Goaziou
2021-11-28 20:34 ` [bug#50751] [PATCH 1/2] gnu: python-trezor-agent: Fix key generation with trezor-gpg init Nicolas Goaziou
2021-11-30 20:51 ` Attila Lendvai
2021-12-01 15:34 ` Nicolas Goaziou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='DzDi6h_5spuoHXP0bdLYQbS6NY2DetR_lBnnR18-u0RUj_EQPWkzp8x6ZXxMIQYqNQBIA4ukzQXGeUtKDYBRHInV83zrfiZzd_W3xTfc3u8=@lendvai.name' \
--to=attila@lendvai.name \
--cc=50751@debbugs.gnu.org \
--cc=iskarian@mgsn.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).