Project

General

Profile

Actions

Bug #6607

closed

Package Filter rules should not restrict on unique package name.

Added by Brad Buckingham almost 10 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Web UI
Target version:
Difficulty:
Triaged:
Yes
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.

Actions #1

Updated by Brad Buckingham almost 10 years ago

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

Updated by The Foreman Bot almost 10 years ago

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

Updated by Brad Buckingham almost 10 years ago

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

Updated by Eric Helms over 9 years ago

  • translation missing: en.field_release set to 13
Actions

Also available in: Atom PDF