From: Martin via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 47092@debbugs.gnu.org
Subject: bug#47092: Icecat sandbox causes issues with fonts in --pure env
Date: Fri, 12 Mar 2021 10:15:25 +0000 [thread overview]
Message-ID: <07e5c494-0bc7-47fd-ab0a-8884b88f7275@disroot.org> (raw)
In-Reply-To: <86sg50itq6.fsf@gmail.com>
Hi Simon,
no it doesn't help in this case and in general eolie package seems to be
broken because it doesn't work even with the simple 'guix environment
--ad-hoc eolie -- eolie':
Traceback (most recent call last):
File
"/gnu/store/w47sa5q3vki5siwk5lb62ld4ksxa5gcn-eolie-0.9.101/bin/.eolie-real",
line 20, in <module>
from eolie.application import Application
File
"/gnu/store/w47sa5q3vki5siwk5lb62ld4ksxa5gcn-eolie-0.9.101/lib/python3.8/site-packages/eolie/application.py",
line 19, in <module>
gi.require_version("Handy", "1")
File
"/gnu/store/597f7p79vyxjhwsv2qqnn76hx107xgj1-python-pygobject-3.34.0/lib/python3.8/site-packages/gi/__init__.py",
line 129, in require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Handy not available
Kind regards!
Martin
On 3/12/21 9:53 AM, zimoun wrote:
> Hi,
>
> The example about ’eolie’ adapted to your usecase, does it not work?
>
> See:
> <https://guix.gnu.org/manual/devel/en/guix.html#Invoking-guix-environment>
>
>
> All the best,
> simon
next prev parent reply other threads:[~2021-03-12 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 9:03 bug#47092: Icecat sandbox causes issues with fonts in --pure env Martin via Bug reports for GNU Guix
2021-03-12 9:53 ` zimoun
2021-03-12 10:15 ` Martin via Bug reports for GNU Guix [this message]
2021-03-12 10:51 ` zimoun
2021-03-12 11:09 ` Martin via Bug reports for GNU Guix
[not found] ` <d45ebb57-fed2-e77a-804e-73d8cbcf4d76@disroot.org>
2021-03-12 10:21 ` zimoun
2021-10-28 11:15 ` Martin via Bug reports for GNU Guix
2021-10-28 18:49 ` Mark H Weaver
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=07e5c494-0bc7-47fd-ab0a-8884b88f7275@disroot.org \
--to=bug-guix@gnu.org \
--cc=47092@debbugs.gnu.org \
--cc=smartin@disroot.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).