From: zimoun <zimon.toutoune@gmail.com>
To: 47097@debbugs.gnu.org
Subject: bug#47097: eolie broken => unworking example from manual
Date: Fri, 12 Mar 2021 11:56:31 +0100 [thread overview]
Message-ID: <86ft10iqsg.fsf@gmail.com> (raw)
Hi,
The manual says:
guix environment --preserve='^DISPLAY$' --container --network \
--expose=/etc/machine-id \
--expose=/etc/ssl/certs/ \
--share=$HOME/.local/share/eolie/=$HOME/.local/share/eolie/ \
--ad-hoc eolie nss-certs dbus -- eolie
from
<https://guix.gnu.org/manual/devel/en/guix.html#Invoking-guix-environment>.
The result is:
--8<---------------cut here---------------start------------->8---
Traceback (most recent call last):
File "/gnu/store/vd3j73jl7prq92w1343k9miiyzbiw2qz-eolie-0.9.101/bin/.eolie-real", line 20, in <module>
from eolie.application import Application
File "/gnu/store/vd3j73jl7prq92w1343k9miiyzbiw2qz-eolie-0.9.101/lib/python3.8/site-packages/eolie/application.py", line 19, in <module>
gi.require_version("Handy", "1")
File "/gnu/store/w2vbhjfbhiszlrjilnxniqrmkdpy0kr9-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
--8<---------------cut here---------------end--------------->8---
All the best,
simon
next reply other threads:[~2021-03-12 11:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 10:56 zimoun [this message]
2021-03-12 11:44 ` bug#47097: eolie broken => unworking example from manual Martin via Bug reports for GNU Guix
2021-03-12 17:55 ` bug#47097: [PATCH] gnu: eolie: Add missing inputs Leo Prikler
2021-03-18 20:44 ` bug#47097: eolie broken => unworking example from manual Ludovic Courtès
2021-03-24 3:14 ` zimoun
2021-03-24 8:07 ` Leo Prikler
2021-03-24 16:17 ` Ludovic Courtès
2021-03-26 12:32 ` Leo Prikler
2021-04-10 18:40 ` Leo Famulari
2021-04-10 20:24 ` Leo Prikler
2021-04-10 20:31 ` Leo Famulari
2021-04-14 20:03 ` Leo Famulari
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=86ft10iqsg.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=47097@debbugs.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).