On Tue, Mar 24, 2009 at 12:44 PM, Michael DeHaan <[email protected]> wrote: > I've opened up a bugzilla on a problem I'm seeing with mod_python. > > So far the symptom is that the "no pxe" support only works 50% of the > time if you manually visit: > > http:///server.example.org/cblr/svc/op/nopxe/system/name > > The traceback is in the bugzilla. > > https://bugzilla.redhat.com/show_bug.cgi?id=491977 > > I'd be curious if anyone else sees this on anything other than F10.
Isn't this caused when you need to import a module that is a compressed egg file? The importer needs to decompress it or something like that. I've seen errors similar to this before when backporting fedora 9's python 2.5 to RHEL5 (scary patch at [1]). If memory serves, this is caused by manually building python modules using setup.py or ez_install. Perhaps bad packaging of a python module would also do it? If using ez_install, use the -Z flag to decompress the eggs during install. Can you try seeing if their are any egg files to verify this theory or not? Something like this *should* work /me thinks: find $(python -c "from distutils.sysconfig import get_python_lib; print get_python_lib()") -name '*.egg' We've used fedora 10 quite a bit and haven't seen this traceback before. [1] http://www.digitalprognosis.com/opensource/patches/python/python-2.5.1-backport-to-db4-4.3.patch -- Jeff Schroeder Don't drink and derive, alcohol and analysis don't mix. http://www.digitalprognosis.com _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
