[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#57345] [PATCH] Add gnupg to propagated-inputs of trezor-agent
From: |
Marek Paśnikowski |
Subject: |
[bug#57345] [PATCH] Add gnupg to propagated-inputs of trezor-agent |
Date: |
Fri, 09 Sep 2022 19:55:17 +0000 |
I give up.
So far, the cleanest workaround is to explicitly declare `gnupg` installation.
I decided to use that going forward.
```
(inputs (list gnupg guile-2.0 python-3 python-trezor python-trezor-agent))
(add-before 'check 'wrap-more
(lambda* (#:key inputs outputs #:allow-other-keys)
(wrap-script (string-append #$output "/bin/trezor_agent.py")
'("PATH" ":" prefix
'("/gnu/store/3bpq5knfvzhxhqfwzqm9br917nz7r0yp-gnupg-2.2.32/bin")))))
```
This is as far as I was able to go while maintaining any sense of understanding
and control over the code.
All attempts to progress end with this failure:
```
Backtrace [...]
ERROR:
1. &wrap-error:
program:
"/gnu/store/rb3wzd5pi899mlvv4wj35afc4z8ys60m-trezor-agent-0.14.4/bin/trezor_agent.py"
type: no-interpreter-found
```
Clearly, the wrapping documentation assumes something and fails to mention it -
and now a programming noob like me is totally lost.
My conclusions:
1. Current state of `trezor-agent` - broken critical functionality by default.
2. Presence of `gnupg` in profile fixes the above.
3. `propagated-inputs` also fixes 1., but is not acceptable.
4. In theory, it should be possible to expose a PATH to `gnupg` in `inputs`;
but after days of working towards it, I am still not capable of reaching this
solution.