OK, the mysql.init error is probably caused by the script already having been run, so you should be able to safely delete it from /etc/e-smith/sql/init or wherever it lives.
Not sure on the change_folders issue at the moment. It's also on my server and doesn't seem to be causing a problem, but I need to track down where it's coming from.
Now, a couple of general things that would have saved both of us some time, and you some frustration:
1. If you encounter errors in installation, say so, and give the EXACT text of the error message.
2. Don't use the --nodeps flag unless you (1) have been told to do so by the packager, or (2) know what you're doing. RPMs have dependancies for a reason, and usually using --nodeps will break things.