unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Jacob MacDonald <jaccarmac@gmail.com>
To: "Daniel Meißner" <daniel.meissner-i4k@ruhr-uni-bochum.de>
Cc: help-guix@gnu.org
Subject: Re: trash-cli commands fail after upgrade to 0.21.10.24
Date: Sun, 13 Feb 2022 19:42:28 -0600	[thread overview]
Message-ID: <CACy6W0Ctv9q70sKNOmg6JJsDrQOVftvZo5T4q9N+OGX4DiS3Dg@mail.gmail.com> (raw)
In-Reply-To: <87fsomx3wi.fsf@ruhr-uni-bochum.de>

On Sun, Feb 13, 2022 at 8:00 AM Daniel Meißner
<daniel.meissner-i4k@ruhr-uni-bochum.de> wrote:
> after setting GUIX_PYTHONPATH I was able to get the cli working

Thanks for investigating. I had missed that environment variable, and
it looks like python-wrapper adds it to Guix's .profile. With the
proper environment variable and no python-wrapper, the program works
fine.

> This means the package needs a fix.  We could either patch the scripts
> ...
> or maybe we could use the wrap-program procedure to wrap it with GUIX_PYTHONPATH set correctly.

I took a look at the changes in
39510d5a5e4e0e38cd3d3bc944d5bf6d96242493, wrap-python3 in (gnu
packages python.scm), and the Python build system. There may be other
source code which answers my question, but: Did that version-bumping
commit break trash-cli with the version upgrade or with the new phase?
Does wrap-python3 write environment variables to my Guix profile
somehow, or does it just update what the wrapped package outputs?


  reply	other threads:[~2022-02-14  1:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-05  4:39 trash-cli commands fail after upgrade to 0.21.10.24 Jacob MacDonald
2022-02-10 13:51 ` Daniel Meißner
2022-02-10 20:53   ` Simon Streit
2022-02-11  2:59   ` Jacob MacDonald
2022-02-13 14:00   ` Daniel Meißner
2022-02-14  1:42     ` Jacob MacDonald [this message]
2022-02-16 16:11     ` Daniel Meißner

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=CACy6W0Ctv9q70sKNOmg6JJsDrQOVftvZo5T4q9N+OGX4DiS3Dg@mail.gmail.com \
    --to=jaccarmac@gmail.com \
    --cc=daniel.meissner-i4k@ruhr-uni-bochum.de \
    --cc=help-guix@gnu.org \
    /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. 
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).