Hello, Ben. On Thu, May 07, 2009 at 07:59:09PM +1000, Ben Finney wrote: > package gracie > tags 519623 + moreinfo unreproducible > thanks > > I don't observe this behaviour today, in a raw chroot built from > Debian ‘unstable’. Instead, I see:
I did not try installing it in a new chroot. I will try it and send you a report. But perhaps, it will be successfull and we should take a better look at the real problem here, which may not lie in the gracie package. > ===== > # /etc/init.d/gracie start > Starting Gracie OpenID > provider:/usr/lib/python2.5/site-packages/gracie/server.py:90: UserWarning: > openid.server.server.Server constructor requires op_endpoint parameter for > OpenID 2.0 servers > self.openid_server = OpenIDServer(store) > gracied. > ===== > > (The warning message is another bug to be fixed; but the server does start.) > > On 13-Mar-2009, Thadeu Lima de Souza Cascardo wrote: > > It fails to import gracie.server. I cannot import gracie, but I can > > import other packages in /usr/share/pyshared/. > > Note that packages are not imported from that directory; they are > imported from the byte-compiled location specific to the running > version of Python. The command below is exactly what I did. And I recall that what I meant was that other packages installed in pyshared could be imported because their byte-compiled version was in the proper location, which does not seem to happen with gracie. > In the same chroot, I'm able to import ‘gracie.server’ successfully: > > ===== > # python > Python 2.5.4 (r254:67916, Feb 18 2009, 04:30:07) > [GCC 4.3.3] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> import gracie.server > >>> gracie.server > <module 'gracie.server' from > '/usr/lib/python2.5/site-packages/gracie/server.pyc'> > >>> > ===== > > > Below is the error. > > > > Starting Gracie OpenID provider:Traceback (most recent call last): > > File "/usr/bin/gracied", line 18, in <module> > > from gracie.server import become_daemon > > ImportError: No module named gracie.server > > Are you still experiencing this? If so, what output do you see when > you run these commands: I've just purged gracie and installed it again, and I still have the same problem. I had used pycentral to install the package and it worked. Then, I had /usr/lib/python2.5/site-packages/gracie/server.pyc installed. After the purge, it's no longer there, but after a new install, it is missing. > ===== > $ echo $PYTHONPATH > Empty. casca...@vespa:~$ echo $PYTHONPATH casca...@vespa:~$ python Python 2.5.4 (r254:67916, Feb 17 2009, 20:16:45) [GCC 4.3.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import gracie.server Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named gracie.server >>> > $ locate gracie/server.py > /usr/lib/python2.4/site-packages/gracie/server.py > /usr/lib/python2.4/site-packages/gracie/server.pyc > /usr/lib/python2.5/site-packages/gracie/server.py > /usr/lib/python2.5/site-packages/gracie/server.pyc > /usr/share/pyshared/gracie/server.py > ===== > Since I've installed it again, I ran updatedb and what I get is: casca...@vespa:~$ sudo updatedb casca...@vespa:~$ locate gracie/server.py /usr/share/pyshared/gracie/server.py casca...@vespa:~$ That is, the byte-code version is not being installed during postinst, I assume. After running pycentral myself: casca...@vespa:~$ sudo pycentral pkginstall gracie casca...@vespa:~$ ls /usr/lib/python2.5/site-packages/gracie/server.pyc /usr/lib/python2.5/site-packages/gracie/server.pyc casca...@vespa:~$ > -- > \ “I planted some bird seed. A bird came up. Now I don't know | > `\ what to feed it.” —Steven Wright | > _o__) | > Ben Finney <b...@benfinney.id.au> Thanks for the attention, Cascardo.
signature.asc
Description: Digital signature
