Subject: Re: xentools3 package currently broken?
To: Manuel Bouyer <firstname.lastname@example.org>
From: Daniel Horecki <email@example.com>
Date: 09/11/2007 22:03:22
2007/9/11, Manuel Bouyer <firstname.lastname@example.org>:
> On Tue, Sep 11, 2007 at 09:43:15PM +0200, Manuel Bouyer wrote:
> > On Tue, Sep 11, 2007 at 03:20:29PM -0400, Thor Lancelot Simon wrote:
> > > On Tue, Sep 11, 2007 at 08:45:11PM +0200, Manuel Bouyer wrote:
> > > >
> > > > Can you investigate what is trying to load signal.py on your system ?
> > >
> > > Well, it's clearly a dependency of some Python module. Can you see if
> > > you've got it on your system anywhere? Maybe it's my Python installation
> > > that's broken, and so it should be found in some other part of the Python
> > > search path...
> > Well, I have no signal.py/signal.pyc on my systems. find didn't return
> > anything in /usr/pkg, and locate didn't return anything relevant either.
> And a
> find /usr/pkg -type f |xargs fgrep -l signal.py
> didn't return anything either. I can't explain why xm is looking for a
> signal.py on your system.
> Manuel Bouyer <email@example.com>
> NetBSD: 26 ans d'experience feront toujours la difference
It doesn't need to be in .py file. It can be loadable module or simple
buildin in python. I think it's last case:
>>> import signal
If I'll try to import nonexistant module, it will tell me:
>>> import nonexistant
Traceback (most recent call last):
File "<stdin>", line 1, in ?
ImportError: No module named nonexistant
Daniel 'Shinden' Horecki