Feature #26206
closedDependency Resolution within content views + associated UI constructs.
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1152515
Description of problem:
When creating a content view filter, a user can add/remove arbitrary packages/errata to a content view. However, dependency resolution is not completed on the resultant repos. As such, the end user can easily create a non-working CV.
Example:
That is, if the user creates a content view filter that includes errata 'foo',
and the packages in that errata require 'bar' and 'baz' as dependencies, 'bar' & 'baz' should end up in the resultant content view.
This RFE requests enabling dependency resolution by default on content views, while giving the user the option via the UI to disable.
Version-Release number of selected component (if applicable):
foreman-1.6.0.46-1.el6sat.noarch
katello-1.5.0-30.el6sat.noarch
pulp-server-2.4.1-0.7.beta.el6sat.noarch
How reproducible:
100%
Updated by The Foreman Bot almost 6 years ago
- Assignee set to John Mitsch
- Pull request https://github.com/Katello/katello/pull/7993 added
Updated by John Mitsch almost 6 years ago
- Subject changed from Dependency Resolution within content views + associated UI constructs. to Dependency Resolution within content views + associated UI constructs.
- Target version set to Katello 3.12.0
- Triaged changed from No to Yes
Updated by The Foreman Bot almost 6 years ago
- Status changed from New to Ready For Testing
Updated by John Mitsch almost 6 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|7474c9d72928d3d539c2e0f5cd85a06017c465c2.