From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 29292-done@debbugs.gnu.org
Subject: bug#29292: [PATCH] Scribus: Fix No module named _sysconfigdata_nd
Date: Mon, 20 Nov 2017 18:26:14 +0100 [thread overview]
Message-ID: <87r2ssn9op.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87bmk2ilza.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 16 Nov 2017 10:58:17 +0100")
Hello,
ludo@gnu.org (Ludovic Courtès) writes:
> Please make it “Fixes <https://bugs.gnu.org/25035>.” so we can more
> easily grep the git log.
Fixed.
>> + (modify-phases %standard-phases
>> + (add-after 'install 'wrap-program
>> + (lambda* (#:key inputs outputs #:allow-other-keys)
>> + ;; Fix "ImportError: No module named _sysconfigdata_nd" where
>> + ;; Scribus checks PATH and eventually runs system's Python
>> + ;; instead of package's.
>> + (let* ((out (assoc-ref outputs "out"))
>> + (py2 (assoc-ref inputs "python")))
>> + (wrap-program (string-append out "/bin/scribus")
>> + `("PATH" ":" prefix (,(string-append py2 "/bin")))))
>
> Did you identify the part of the code that invokes “python”? If so,
> instead of adding a wrapper, we could patch that file to use the
> absolute file name of “python”, which would be even better.
I know, but I couldn't find the culprit, unfortunately. It may be easier
for someone more knowledgeable in the Python world.
> Anyway, congrats on finding out what was wrong!
To be fair, the IRC crew did all the work.
I applied the patch. Thank you.
Regards,
--
Nicolas Goaziou 0x80A93738
prev parent reply other threads:[~2017-11-20 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 23:44 [bug#29292] [PATCH] Scribus: Fix No module named _sysconfigdata_nd Nicolas Goaziou
2017-11-14 0:07 ` Adonay Felipe Nogueira
2017-11-16 9:58 ` Ludovic Courtès
2017-11-20 17:26 ` Nicolas Goaziou [this message]
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=87r2ssn9op.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=29292-done@debbugs.gnu.org \
--cc=ludo@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.
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).