Bug 1260792

Description of problem:
Currently, packages selected for inclusion into a content view during publish do not include dependent packages which is a big annoyance because this dependency checking must now be done manually which is a lot of work, especially if it is a multilevel dependency.

Version-Release number of selected component (if applicable):


How reproducible:

6.
Steps to Reproduce:
example:
1. create content view with rhel 7Server
2. create include filter on all base packages
3. create include filter on errata up to 1-apr-2015
4. create include filter on package redhat-access-insights
5. publish & promote contentview
6. subscribe content host to this content views repo's
7. try to install redhat-access-insights
8. look at dependency errors and try to resolve based on info
9. keep doning until all dependencies are resolved.

Actual results:
yum dependency errors

Expected results:
able to install packages with all dependencies resolved

Additional info:
If dependency cannot be resolved due to missing dependent packages in included repo's the publish task should fail with a clear explanation why it failed.