You have actually included modules in this, which is not how one builds a profile.
Your inclusion of views here has caused dependency generation to fail for views on drupal.org.
You haven't built an install profile here, you've copied a bunch of stuff together. That's not the way it's done. There are many good resources for this, but the way you're doing it is not right.
You can look at Commerce Kickstart and see how you're supposed to build a drush make file that automatically builds in the modules you want at packaging time.
How did I get here? By including views and such you've broken the project dependency system that lets the testbots download the right dependencies.
Could you please at least unpublish your releases? I don't think you can delete them. I'll be happy to help you work through this. You may need to have this project removed and start over again.
Please let me know how I can help.
Comments
Comment #1
greggles(less caustic title)
Comment #2
rfayThanks. Was just listening to a podcast from you about how to behave in the issue queue :-)
Comment #3
cr0ss commentedYou are right, I'll get rid of dup modules at next push.
Thanks for notice!
Comment #4
cr0ss commentedDone, modules are removed from distrib. Also I've checked all files with Coder module and created onepagecv.make files.
Comment #5
rfaycr0ss++ Thanks!
When we get something committed we normally move the status to "fixed", which automatically turns into closed(fixed) in two weeks if there are no more comments. That way it still shows up in people's lists for two weeks if they're interested in the result or perhaps might disagree, etc.
Comment #6
cr0ss commentedWelcome Randy. Got the point about statuses.