Project

General

Profile

Bug #6607

Package Filter rules should not restrict on unique package name.

Added by Brad Buckingham about 6 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Category:
Web UI
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1106565
Description of problem:

Having repository with wit packages

package-0:1.0.0
package-0:2.0.0
package-0:3.0.0
package-0:4.0.0

There isn't an easy way to setup a filter such that the following packages are included:

package-0:2.0.0
package-0:4.0.0

Simply because:

validates :name, :presence => true, :uniqueness => { :scope => :content_view_filter_id }

You can't have two rules with the same package name. We should either lift this restriction or support a comma seperated list of values for exact versions.

Associated revisions

Revision 092b6b9a (diff)
Added by Brad Buckingham about 6 years ago

fixes #6607 / BZ 1106565 - Content View Package Filter Rules - allow duplicate name

Prior to this commit, a user could not create multiple package filter
rules for the same package (i.e. name) but different specific versions.

For example, if a repo had the following packages:
package-0:1.0.0
package-0:2.0.0
package-0:3.0.0
package-0:4.0.0

A user could not create rules to include/exclude the following packages:
package-0:2.0.0
package-0:4.0.0

Revision efdfc332
Added by Brad Buckingham about 6 years ago

Merge pull request #4426 from bbuckingham/issue-6607

fixes #6607 / BZ 1106565 - Content View Package Filter Rules - allow duplicate name

History

#1 Updated by Brad Buckingham about 6 years ago

  • Assignee set to Brad Buckingham
  • Target version set to 49
  • Triaged changed from No to Yes

#2 Updated by The Foreman Bot about 6 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/4426 added
  • Pull request deleted ()

#3 Updated by Brad Buckingham about 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#4 Updated by Eric Helms almost 6 years ago

  • Legacy Backlogs Release (now unused) set to 13

Also available in: Atom PDF