You are including the entire contents of the bin folder in your modpack archive. This needlessly bloats the archive and distributing the minecraft.jar is a violation of Mojang's EULA. The modpack.jar file should be the only file present.
I see that you are including LiteLoader. Have you integrated the liteloader files into the modpack.jar? The "correct" way to include LiteLoader in Forge/MC 1.6.4 is to make the changes you have made to the version.json file inside the modpack.jar file and allow it to retrieve the required library dynamically.
As is clearly stated in the (unnecessarily aggressive) first paragraph of the crash report, you have item ID conflicts. You have a MASSIVE number of item ID conflicts between many different mods. These would normally not prevent the client from starting even though they can cause serious gameplay problems down the road. However, GregoriousT has a "my way or the highway" philosophy and chooses to crash the client out rather than let the conflicts go undiscovered. Fix all these conflicts and the problem will go away.
You have mismatching mod versions in your mods folder. You have bspkrsCore and TreeCapitator for 1.7.2.
I am constantly reminding folks of this when they ask for help so I figured it might be good to remind new pack makers. The "modpack.jar" (especially when making 1.6.4 packs) is simply the Forge universal download renamed to "modpack.jar". There is no need to extract it and re-make it. Just rename the thing and put it in your "bin" folder.
