Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:


Dependency calculation doesn't seem correct.  When adding a bind errata to a changeset and solving the dependencies for it (Changeset#calc_dependencies) , i get:

4 instances of "bash"
6 instnaces of "bind"
~20 instances of "bind-lib"
30 instances of "glibc"
and many more



There are several problems with this.  

1.  Why are the resulting dependencies only listed as "bash"  There should be some version number and arch listed
2.  I do not believe it is taking into account any packages already in the next environment.  In my instance, bash was already in the next environment.
3.  This was a bind errata and bind is a dependency? 
4.  Forgetting the above, I believe it is including multiple versions of the same package.  Is this what we want?  Or just include what the latest is that satisfies the dependency (assuming a version doesn't already exist in the next environment that satisfies it)?

I made some modifications in katello-0.1.169-1:
- filenames (nvra) are displayed instead of package names
- packages that have been promoted to the next environment are not included in the dependency list

There are still two questions left:
1) Should we include all available versions of dependent packages or just the latest?
2) We are currently calculating only first level of dependencies. Shouldn't we do it recurrently to satisfy the full dependency tree?

For the record:
1) We include only latest version of package if it has not been promoted previously
2) We calculate full dependency tree

The patch for this behaviour is ready.

Both changes are now available in katello-0.1.175-1.