From: Ricardo Wurmus <rekado@elephly.net>
To: Adonay Felipe Nogueira <adfeno@openmailbox.org>
Cc: 25035@debbugs.gnu.org
Subject: bug#25035: scribus: No module named _sysconfigdata_nd
Date: Mon, 28 Nov 2016 09:13:16 +0100 [thread overview]
Message-ID: <877f7o2fab.fsf@elephly.net> (raw)
In-Reply-To: <87zikmwku1.fsf@openmailbox.org>
Adonay Felipe Nogueira <adfeno@openmailbox.org> writes:
> # Steps to reproduce
>
> Simply try running Scribus. It closes immediatelly.
I cannot reproduce this. I just upgraded Scribus; I’m using
/gnu/store/5h44li2ansg4mb5kqck44wdzkka3isih-scribus-1.5.2/bin/scribus
> # Notes
>
> * I have attached the raw output of `strace scribus`.
> * It seems that, from the strace, one sees that something (Scribus?)
> attempts to use things from the host's root ("/"), not from the
> derivative's root ("$out/"), although, if comparing the existance of
> some files between the two path trees, some of them don't exist in
> the derivative's path tree (e.g.: No "$out/lib/python2.7/site.py", or
> no "$profile/lib/python2.7/site.py", in the case of the current user's
> ".guix-profile" directory).
Are you running Scribus on GuixSD or on a foreign distro? The strace
shows that your Scribus opens /usr/lib/python2.7/sysconfig.py, which
doesn’t exist on GuixSD. Mixing Python from Guix with a system Python
installation is bound to lead to problems.
What is your PYTHONPATH variable set to?
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
http://elephly.net
next prev parent reply other threads:[~2016-11-28 8:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-26 11:18 bug#25035: scribus: No module named _sysconfigdata_nd Adonay Felipe Nogueira
2016-11-28 8:13 ` Ricardo Wurmus [this message]
2016-11-28 9:54 ` Adonay Felipe Nogueira
2016-11-28 13:54 ` Ludovic Courtès
2016-11-28 15:42 ` Ricardo Wurmus
2016-12-09 8:59 ` Adonay Felipe Nogueira
2017-05-03 19:05 ` Adonay Felipe Nogueira
2017-12-01 14:41 ` Ludovic Courtès
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=877f7o2fab.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=25035@debbugs.gnu.org \
--cc=adfeno@openmailbox.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).