On Wed, Aug 24, 2011 at 12:48 AM, James Cammarata <[email protected]> wrote: > On Tue, Aug 23, 2011 at 5:24 PM, Duffie Cooley <[email protected]> wrote: >> What I have done so far. >> >> I have a debian host running cobbler 2.1.0 from the debian repo. I went >> into /usr/lib/python2.7/dist-packages/cobbler and copied all the .py >> to .py.orig. Then I uncommented all of the debian specific stuff in >> actions-import and codes. Then I pycompile and rerun my import. Now when > > Something's wrong here, you shouldn't have to uncomment anything, as > we moved imports to a module structure and added full support for > debian/ubuntu distros (newer ones, at least) in 2.1.0. I'd recommend > grabbing the latest from git and trying that out, making sure to > uninstall what you've got on that machine so there are no conflicts. >
Looking at the current git, I see both the manage_import_*py and the action_import.py. Probably, Duffie did uncomment things on action_import, which is actually never used. Is probably a good idea to move the action_import (and probably others) to the obsolete directory, to avoid this kind of confussions. Javier Palacios _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
