| Re: [proaudio] ImportError: No module named layman.config |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] ImportError: No module named layman.config
- From: "Arve Barsnes" <arve.barsnes@xxxxxxxxx>
- Date: Tue, 5 Aug 2008 06:27:06 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=TXqcFLDpiiYdzQYEXwoqXLaen3dTWM0ooyE4+uHc2bA=; b=j4JoAYTN0MWVQ4vrigz4NtnK9avN8q5H7tsINsRn8hSJs763Tv0HwW6XV6JaBOmvqi soC4wQ+RrDd8hvU6N9lLxlOTLfiUzgh1RoPVi+mjLy81PCa4kW6XtlsYpuLioesoKXUy 9cS41MVIGuTdIk47J7xKLWh2veu4fJkxVb1EI=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=desSfG5K3xP7tYaZBWxlYkSCTij74+Jx5X/YDARl2T4I/z17kG9VK7nmHg3n5H7PZ9 PU8fxaQEBOQ5M0eRDr9TrKc+hiRJrwdl+DlandaMC+YlkhHewKY85AWKB8sDc71NxnCv qwXJ94gphCZ9yjYJvGHvnqW5MzpsaqbOsBm44=
It's complaining about a python module called "layman.config", not
your config files, so I'd try reinstalling layman, and if that didn't
work, contact layman developers.
On Tue, Aug 5, 2008 at 4:20 AM, Mark Knecht <markknecht@xxxxxxxxx> wrote:
> I did some updates last week, did an emerge -DuN system, check that
> the system was working and the promptly split town for a couple of
> days off. When I returned I tried to update tonight but layman is
> failing:
>
> lightning ~ # layman -s pro-audio
> Traceback (most recent call last):
> File "/usr/bin/layman", line 23, in <module>
> from layman.config import Config
> ImportError: No module named layman.config
> lightning ~ #
>
> Does anyone recognize what might be causing this?
>
> I have not yet blown away the old config and tried reinstalling layman
> and the proaudio overlay. I can do that but I figured maybe it was
> good to ask about this first just to get straight what has happened.
>
> Thanks,
> Mark
>
>
>