In interest of full disclosure, I had to fix a few things for Red Hat Satellite Server / Spacewalk that warranted some new releases of Cobbler and Koan. The changes in this release aren't very profound for people who are just using Cobbler, but I didn't want some folks to wonder why this release wasn't getting wider visibility , so here it is:
- - 1.6.6 - (BUGF) fix typo in /usr/bin/cobbler-register - (NOTE: koan changelog in subdirectory is no longer maintained) - (BUGF) fix error message when wrong virt ram value is applied - (FEAT) koan now partially works in source code form on EL 2 - (BUGF) Satellite also has a python module named "server" so we have to remove ours for Python imports. This code was not used anyway. - (BUGF) Fedora 11 imports now work
One of these was a workaround for what we think is a mod_python import bug because of a reused module name. Another is code-only support for an OS that is not widely deployed.
Of this changelog, here are the only ones that will affect end users:
koan: fix typo in /usr/bin/cobbler-register cobbler: fix error message when wrong virt ram value is applied cobbler: Fedora 11 --os-version is now legal for imports
If either of those two items are interesting for you, you can pick up RPMs from
http://mdehaan.fedorapeople.org/files/cobbler/testing/
However we are probably *not* going to release this to Fedora/EPEL as it's so small, probably I'm going to wait until we have more items to do a 1.6.7 (if we accumulate enough new fixes to warrant this), or just wait until 2.0 ... it depends on what comes up.
Though if you've been wanting to use cobbler-register and haven't built a new RPM, that may get you started... although cobbler-register works a lot better in 2.0 so you may just want to wait. It also fixes that pesky message when you enter in the wrong virtual RAM.
Again, I consider both of these fixes not worth upgrading, but these packages do solve some Satellite problems/features that are rather important to it.
Fedora 11 *is* important, but then again, I didn't want to push a new release so close to the previous one. Also, I think the future focus should be on 2.0 rather than indefinitely continuing 1.6.X
Apologies if that is somewhat confusing :)
--Michael