unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 27237-done@debbugs.gnu.org, ng0 <ng0@pragmatique.xyz>
Subject: bug#27237: wicd-curses: `urwid' is not available
Date: Fri, 18 Dec 2020 23:41:41 +0100	[thread overview]
Message-ID: <87k0ten3dm.fsf@elephly.net> (raw)
In-Reply-To: <86bleqvpun.fsf@gmail.com>


zimoun <zimon.toutoune@gmail.com> writes:

> Hi,
>
> On Sun, 04 Jun 2017 at 17:27, ng0 <ng0@pragmatique.xyz> wrote:
>> On a minimal, Xless system when you install wicd through your
>> system configuration and try to start wicd-curses,
>> you get a traceback:
>>
>> File "/gnu/store/aaaaaaaa-wicd-1.7.4/share/wicd/curses/wicd-curses.py", line 44, in <module> import urwid
>> ImportError: No mouled named urwid
>>
>> Which is strange since it is in the inputs, so I'm thinking
>> maybe it needs to be wrapped? I haven't put much though to
>> a solution yet.
>
> Is it still relevant?  If yes, someone could provide moreinfo?
>
> <http://issues.guix.gnu.org/issue/27237>

I cannot reproduce this:

--8<---------------cut here---------------start------------->8---
$ guix environment --ad-hoc --pure wicd -- wicd-curses
/gnu/store/68pb6kcqfc38xk8rn7whmplfq77viwva-wicd-1.7.4/bin/.wicd-curses-real: line 3: mkdir: command not found
Can't connect to the daemon, trying to start it automatically...
Can't automatically start the daemon, this error is fatal...
Error connecting to wicd via D-Bus. Please make sure the wicd service is running.
--8<---------------cut here---------------end--------------->8---

While wicd-curses fails for unrelated reasons, it does *not* fail to
load urwid.

I’m closing this issue.

-- 
Ricardo




      reply	other threads:[~2020-12-18 22:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-04 17:27 bug#27237: wicd-curses: `urwid' is not available ng0
2020-12-18 20:09 ` zimoun
2020-12-18 22:41   ` Ricardo Wurmus [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=87k0ten3dm.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=27237-done@debbugs.gnu.org \
    --cc=ng0@pragmatique.xyz \
    --cc=zimon.toutoune@gmail.com \
    /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).